“Successful access to the entire NetSuite database for all years including attachments.”
What Is NetSuite Data Archiving? What It Has to Keep, and How to Prove It
NetSuite data archiving is the work of extracting a NetSuite account's records, with their relationships, their general ledger detail and their attached files, into a separate read-only archive where they can still be searched, reported on and produced after the account is retired. It is a different job from exporting a few saved searches and from backing up an account that stays live. This page sets out what an archive has to keep, how archiving NetSuite data works, how you know the result is complete, and what finance and audit can do with it once NetSuite is gone.
Archiving, backup and export are three different jobs
The words are used interchangeably, and the difference only shows years later, when somebody needs an answer from a system that no longer exists. Each one keeps something different.
An export keeps rows
Saved searches and CSV files give you the records you selected, one file per search. Relationships between records are flattened, sublists come out flattened or missing, custom records are easy to overlook, attached files are not part of the export, and nothing proves the set is complete. See NetSuite data to CSV for when an export is the right tool.
A backup protects a live account
A backup keeps a scheduled copy of an account that is still in use, so records can be recovered after a mistake or a loss. It follows the account while it runs. That is AcroBackup for NetSuite, a different need from archiving.
An archive keeps the history usable
Archiving takes the whole agreed record out of an account that is being retired, keeps it related and verified, and holds it read-only where people can search it, run statements from it and produce documents for as long as the retention obligation lasts. That is AcroXtract, with the archive hosted on DBVault.
How NetSuite data archiving works, in order
An archive that will answer an auditor is a project with a fixed sequence, run while the account is still open. Each step exists because of a gap the step before it would otherwise leave.
1 · Map the account
Every record type in the account is identified, custom records and custom fields included, so the scope is known before anything is extracted. You cannot verify what you did not know to extract.
2 · Index the structure
Which records reference which, which lines belong to which transactions, which files attach where. This is what lets the relationships be kept instead of flattened.
3 · Build the archive database
A relational database is created to match that structure, with each record type and the links between them.
4 · Extract, read-only
Records, lines, entities, master data, custom records and the File Cabinet are extracted into it, through a NetSuite login you provide and can revoke, used read-only. The business keeps working while it runs.
5 · Verify against the source
A database-level comparison against the account, then financial reconciliation by subsidiary, period and accounting book. A plausible record count is not treated as proof.
6 · Validate with the people who will use it
Your team tests the archive against the questions it will be asked once NetSuite is gone, and raises anything that looks wrong as a ticket inside the archive. Sign-off follows when the tickets are cleared.
What a NetSuite archive has to keep
Transactions with every line, not only the headers
The GL impact of each transaction, by subsidiary, period and book
Customers, vendors, items and the chart of accounts they resolve to
Custom records and custom fields as record types of their own
The File Cabinet, each file linked to the record it supports
System Notes and audit history within the agreed scope
If people keep working in NetSuite
An extraction reads the account as it stands on the day it runs. Where transactions continue after the first pass, a final data-entry cut-off is agreed and a delta extraction brings across what changed, and the combined set is verified again. The extract-while-live page covers the cut-off and the delta in full.
Archiving the File Cabinet with its records
The File Cabinet holds the documents a record points to: the signed contract behind a sales order, the invoice as it was sent, the receipt behind an expense. Archiving the records without it leaves the evidence behind; archiving it without the records leaves files nobody can place.
What NetSuite's own download gives you
Oracle documents that a File Cabinet folder downloads as a ZIP file that keeps the folder structure, and recommends working with files of 100 MB or smaller (Downloading Files from the File Cabinet). That is a copy of the folders.
What a folder copy does not carry
Oracle's description covers the folders and the files in them; which transaction, customer or vendor each file was attached to is not part of it. An archive has to extract that link with the records, so a file opens from the invoice it supports years later instead of from a folder someone has to remember.
How it is archived with the records
AcroFile extracts the File Cabinet with its folder structure and each file's link to its record, on its own or as part of a full archive. Why it matters after NetSuite is set out in NetSuite File Cabinet archiving: keeping attachments with their records.
Three ways to keep NetSuite history, compared fairly
Each of these suits some organisations. The difference is what it costs to keep, and what a finance user can do with it in year five.
Keep a reduced NetSuite licence
Every question stays answerable inside NetSuite, by people who know it. The subscription keeps running for the whole retention period, and the history stays tied to one account. What keeping the account costs sets out the comparison.
Export to files
Free and familiar, and enough for a narrow need. Relationships are flattened, custom records are the part most often missed, and a folder of exports carries no evidence that everything came out.
Extract into a hosted archive
The agreed record is extracted with its relationships, verified against the source and held read-only on DBVault, and it is delivered to you as a MySQL database snapshot and a zip of the database and the File Cabinet, so hosting is optional and the data can move again.
What finance and audit can do with the archive afterwards
An archive that only a database specialist can query has moved the problem, not solved it. On DBVault, a finance user works without a NetSuite login.
Find a record and everything around it
Search the whole archive with filters by date, transaction type, subsidiary and custom field; a record opens with its sublists, its entity links and its attachments in place.
Run the statements for a closed year
Trial balance, balance sheet, income statement and general ledger run inside the platform against the archived GL impact, Multi-Book included, and each figure leads back to its transactions.
Give an auditor exactly their scope
Read-only viewers restricted by archive, record type, File Cabinet folder and subsidiary through named profiles; direct File Cabinet browsing can be switched off; logins and downloads are logged.
What archiving does not do
It does not replace the next ERP: the archive is read-only history.
It does not load data into another system; records leave as CSV or MySQL for the team doing a load.
Workflows and other logic locked in the NetSuite user interface are not part of a data archive.
It is cloud-hosted only; there is no on-premises installation of the platform.
When to start archiving NetSuite data
While the account is fully open and the people who know it are still there. Verification, your validation period and any delta all need the source, and the easiest place to investigate a missing record type is still NetSuite itself.
Start from the date on which NetSuite access ends and work backwards; how long each step takes depends on the size of the account, its customisation, the File Cabinet volume and how quickly your team can validate. The licence expiry page works backwards from a term end, and the NetSuite decommissioning page covers the whole retirement.
NetSuite archives in use on DBVault
All case studiesEach of these organisations had its NetSuite history extracted and kept on DBVault. The write-ups describe what was extracted, how it was delivered and what the team uses now.
- Case StudyVP of IT Strategy and Data, software companyRead more
- Case Study
“Blueacrobat is efficient, professional and cost effective.”
Director of Business Intelligence, telecommunications companyA telecommunications company's legacy NetSuite archived on DBVault for audit
Read more - Case Study
“Their product, DBVault, was built and readily available to use after data extraction.”
Senior Systems Analyst, AwayAway: NetSuite records and File Cabinet extracted and hosted on DBVault
Read more
Questions about NetSuite data archiving
What is NetSuite data archiving?
Extracting a NetSuite account's records, with their relationships, general ledger detail and attached files, into a separate read-only archive that people can search and report from after the account is retired. It is done while the account is still open, and it is verified against the account before the account closes.
Is archiving NetSuite data the same as backing it up?
No. A backup keeps a scheduled copy of an account that stays live, so records can be recovered after a mistake. Archiving takes the history out of an account that is being retired and keeps it usable for as long as the retention obligation runs. Some organisations need both, at different times.
Are saved-search exports enough to archive NetSuite?
For a narrow need, sometimes. For an account being retired, usually not: exports flatten the relationships between records, custom records are the part most often missed, attached files are not included, and nothing proves the set is complete.
What should a NetSuite archive include?
Transactions with their lines, the GL impact of each one by subsidiary, period and book, entities and master data, custom records and custom fields, the File Cabinet linked to its records, and System Notes within the agreed scope. The scope is agreed when the account is mapped.
Can the File Cabinet be archived with the records?
Yes. It is extracted with its folder structure and each file's link to the record it belongs to, so a document opens from the transaction it supports. It can be archived on its own or as part of a full archive.
Do we need a NetSuite licence to see archived data?
No. The archive is hosted on DBVault, where authorised users search records, open attachments and run financial statements without a NetSuite login. The data is also delivered to you as a database snapshot, so hosting is optional.
How is an archive of NetSuite data proved complete?
By a database-level comparison against the account, financial reconciliation by subsidiary, period and accounting book, and a validation period in which your team tests the archive and raises issues as tickets until sign-off. Where people kept working, the delta is verified again.
What decides the cost of archiving NetSuite data?
The size of the NetSuite database, the size of the File Cabinet and the number of people who need access afterwards. The extraction is a project, and hosting on DBVault is an annual subscription; a quote follows from a short sizing exercise.
Archive NetSuite before the account closes
Tell us when NetSuite access ends, whether people will keep working in it until then, how large the File Cabinet is and who will need the history afterwards. We will set out what the archive would hold, how it would be verified, and what your team would be working in once NetSuite is gone.