.svg)
AcroFile copies the NetSuite File Cabinet out of the account with its folder structure, file names and each file's link to its record intact, delivered to storage the organisation controls, once for a retiring account or daily for a live one.
Trusted by
.png)
.png)
.png)
.png)
A folder of downloaded files is not an archive of the File Cabinet. The folder tree, the file names and the attachment links are what let a finance user find a document from the invoice it belongs to years later, and they are the parts a manual download loses first.
Preserves original data and file-folder structure.
Enterprise-level data security: encrypted in transit and at rest, ISO/IEC 27001:2022 certified and SOC 2 Type II audited.
The File Cabinet folders in scope, delivered to storage the organisation controls.
A walkthrough on a demonstration archive: the folder structure, the file names and each file's link to its record, as delivered. No account sizing needed first.
.webp)
Every file in the File Cabinet folders in scope, in its original format.
The folder structure and the file names, as they were in NetSuite.
The link between each file and the record it was attached to.
One run for an account that is being retired, or a daily run for an account that stays live.
Delivery to the organisation's own AWS S3 bucket or SFTP server, encrypted in transit and at rest.
Old Attachments Sent and Attachments Received folders moved off the live account, where File Cabinet storage is a cost.
A general-ledger archive on its own does not answer a records request: the signed contract, the remittance and the supporting PDF sit in the NetSuite File Cabinet, attached to the transaction they belong to. AcroFile is Blueacrobat's enterprise-level service for exactly that. It runs once, as File Cabinet archiving for an account that is being retired, or on a daily schedule as a backup for one that stays live.
 1 (1).png)
 1.png)
AcroFile copies the File Cabinet out of NetSuite with the folder structure, the file names and the link between each file and its record intact, so a document can still be found from the transaction it belongs to. It runs once for an account that is being retired, or on a daily schedule for an account that stays live.
Every file in the File Cabinet, whatever its size or type.
The folder structure and file names, exactly as they were in NetSuite.
The link between each file and the record it was attached to.
Runs once for an account being retired, or daily for one that stays live.
Covers migrations, financial archival, off-site storage and decommissioning.
Four situations bring the work to AcroFile. In each, the test is the same: the document must still be findable from its record afterwards.
A migration moves open balances and master data; it rarely moves the File Cabinet. AcroFile takes the folders out with their structure and their attachment links, so the documents can be held alongside the archived records or handed to the team implementing the new system. The load into that system is their work; AcroFile delivers the files in a form they can use.
Where the File Cabinet has grown and its storage is a cost, the old Attachments Sent and Attachments Received folders can be moved off the live account into storage the organisation controls, with the same folder structure, so nothing has to be searched for twice.
Retention obligations apply to the supporting document as much as to the transaction. AcroFile keeps each file with the record it was attached to, so an invoice and its PDF stay together for as long as the retention period runs, and an auditor's request can be answered from the archive rather than from a licence kept open to read it.
Decommissioning has a date attached, and the File Cabinet is gone with the account when it passes. AcroFile extracts the folders in scope before that date, verified against the source, and the documents remain reachable from their records on DBVault or in storage the organisation holds. The sequence for the whole account is on the decommissioning page.
The File Cabinet folder tree is mapped and every file in the folders in scope is indexed, so what is delivered can be checked against what was there.
The files in scope are copied out in their original format and delivered to the organisation's AWS S3 bucket or SFTP server, encrypted in transit and at rest.
The folder structure, the file names and the link between each file and its record are kept, and the delivered set is compared with the index before hand-over.
The organisation's finance or records users open documents from the records they belong to, in the delivered folders or on DBVault, and log anything that does not match as a ticket. Sign-off follows their acceptance; the compared index is the evidence behind it.
Each of these organisations had its File Cabinet extracted with its records, for retention, audit, a migration or read-only access afterwards. The write-ups describe what was extracted, how it was confirmed and how it was delivered, in the reviewer’s own words.
“The cost was very reasonable. It far outweighs not having access to our historical data.”
“They covered their bases well and knew exactly what we needed ahead of us asking.”
“I was most impressed with their ability to predict and estimate execution times, where they always met or exceeded.”
Blueacrobat has extracted and archived ERP data, most of it Oracle NetSuite, for HPE, Kimberly-Clark, Dropbox, Snapchat, NetApp and many others.
Long-lived instances, heavily customised accounts, multi-book and multi-subsidiary structures, and document stores that had to keep their folder structure. The case studies describe engagements of that kind in the reviewer's own words.
Every extraction is compared with the source, then accepted by the organisation's own users before sign-off.
A plausible row count is not treated as proof. The comparison covers record counts by type, financial totals, referential integrity and field-level checks. If people kept working in ERP during the project, the delta is captured and verified again.
Map the account, extract, verify, user acceptance, then a delta where required: the same sequence on every engagement, so a fixed shutdown date can be planned against it.
What the service does not do is stated before the work starts: it does not load data into a successor ERP, and the archive is read-only access to history, not a replacement for the application.
Blueacrobat is ISO/IEC 27001:2022 certified and SOC 2 Type II audited; the Trust Centre describes the controls and how to obtain the certificate and the report.
Every engagement has a written scope and a named contact, and extraction runs with the organisation's own credentials, used read-only.
For an organisation that needs enterprise-level File Cabinet extraction and archival, AcroFile is the service built for it. Contact Blueacrobat to learn more about the service and how it keeps each document linked to its record.
.svg)
.svg)
.webp)
Nothing can be extracted from an account that has already closed, so the files have to leave the File Cabinet while access is still open. AcroFile copies the folders in scope, with the folder tree, the file names and the link between each file and its record, and delivers them to storage the organisation controls before the end date. Planned into the same window as the record extraction, the two are verified together.
Yes. Each file is copied in its original format into the same folder path it had in NetSuite, under the same name, and the index records which record it was attached to. That is what lets someone find a remittance from the invoice it belongs to years later, instead of searching a flat download by guesswork.
The extraction starts by mapping the folder tree and indexing every file in the folders in scope. After the export, the delivered set is compared with that index, folder by folder and file by file, before hand-over. The organisation's own users then open documents from their records and log anything that does not match; sign-off follows their acceptance, not the file count.
To the organisation's own AWS S3 bucket or SFTP server, encrypted in transit and at rest, in the folder tree the files had in NetSuite. From there they are the organisation's to hold on whatever storage its retention policy requires, with no subscription. When AcroXtract extracts the records at the same time, the File Cabinet can be delivered in the same zip as the database, so the documents and the transactions they support travel together.
Hosting on DBVault is a separate, optional service for teams that need an archive they can search rather than a file share. DBVault is cloud-hosted on AWS, and there is no on-premises installation: if the files must sit on infrastructure the organisation runs, the S3 or SFTP delivery is that copy, and it is the organisation's.
Yes. Scope is set by folder before the work starts, so a retiring account can take the whole File Cabinet while a live account moves only the old Attachments Sent and Attachments Received folders off the account. The folders in scope are what the index covers, what the comparison checks and what the quote is sized on.
No. AcroFile copies the File Cabinet; AcroXtract extracts the records, their relationships and the general ledger, and DBVault gives read-only access to the resulting archive. The link between each file and its record is kept on the File Cabinet side, so when the two run together the archived invoice still resolves to its PDF. If the account is being retired, both are usually needed.
Yes. Archiving runs once, for an account that is being retired: the files come out with their folder structure and their links to records, are checked against the index taken at the start, and are kept for as long as they have to be. A backup runs on a daily schedule for an account that stays live, so files added or changed are copied as the business works. What NetSuite data archiving has to keep covers the records around them.
Yes. For an account that stays in production, AcroFile can run daily and copy the File Cabinet to the organisation's storage. Where the records need protecting as well, AcroBackup for NetSuite captures the records and the files that changed since the previous run into DBVault, on a schedule agreed for the account. It is the better fit when recovery of records, not only of documents, is the aim.
In the organisation's own storage, whoever its access controls allow. Where finance, audit or a former subsidiary’s team has to find documents without a file share, the same folders are hosted on DBVault as part of the archive: the File Cabinet is its own section there, browsable by folder, and each file also opens from the record it was attached to.
Access on DBVault is read-only and assigned through named roles and restriction profiles. A viewer can be limited to named File Cabinet folders, and direct browsing of the File Cabinet can be switched off so files are reachable only from records the user is permitted to see. Login events and download history are logged, so it can be shown who took what out.
A File Cabinet is sized by its folders and what they hold, not by the account’s record count, so it is scoped and quoted on its own inputs: the size of the File Cabinet, which folders are in scope and, where the files will be hosted on DBVault, the number of users who need access. Those come from a short sizing exercise, and the quote follows from it rather than from a list price. If the record extraction runs at the same time, the two are scoped and quoted together.
Start from the date access to the account ends. The export, the comparison with the index and the users’ acceptance all have to fit inside that window, and a large File Cabinet lengthens the export and the comparison, so the project window depends on the scope and on how soon access ends. If the record extraction runs at the same time, the two are planned together and verified together.
To start, Blueacrobat needs a login used read-only under credentials the organisation controls, the list of folders in scope, the date access ends, and the bucket or server the files are going to. The sequence for the whole account is on the decommissioning page.
No. AcroFile copies files stored in the NetSuite File Cabinet. A record that points at a document held in another system carries a link rather than a file, so that document is not in the File Cabinet and is not copied; it stays where it is. Records that carry such links should be mentioned during scoping, so the archive’s coverage is stated before the work starts.
.png)
.png)
