.svg)
Which of These Is Your NetSuite Situation?
Almost nobody contacts us asking for a database extraction. They contact us because something changed: the subscription is ending, the company is moving to another ERP, an auditor wants a closed year, a business unit has been sold, or IT wants a copy of the live account that nobody in production can touch. Four years of those conversations sort into nine situations. Each has its own page, and every one of them ends in the same two places: AcroXtract to get the records out with their relationships intact, and DBVault to keep them searchable and reportable afterwards.
Leaving NetSuite, or retiring an account
The account is being switched off, or kept open only to be read. The obligation to produce its records outlasts it by years, and the records have to be somewhere that is not a licence.
Decommissioning and ERP transition
The subscription ends on a date, or the new ERP goes live, and the history has to come out first: what is extracted, in what order, how it is verified, and what happens if people are still working in NetSuite until the cut-off. NetSuite decommissioning.
Historical access and financial reporting
The account is gone and finance still has to find an invoice, answer a customer, or run a trial balance for a period the new system never held. What a legacy archive has to hold, who can see what, and how statements come out of it. Access to NetSuite data after you cancel.
Keeping a read-only account for the history
The default is to keep paying: a reduced, read-only NetSuite account that renews every year for data nobody enters. What that buys and keeps costing, and how the cost of a hosted archive is shaped instead. NetSuite caretaker licence cost.
Audit, tax, compliance and records retention
Auditors come back for closed periods, tax authorities ask about old filings, and retention rules are measured in years. Transaction evidence with its posting detail and attachments, restricted access for the people who ask, and retention on your terms rather than a licence's. NetSuite audit and records retention.
Divestiture, acquisition and entity separation
A business unit is sold, a company is acquired, a group restructures, and one entity's history has to follow it without the rest of the ERP going too. Scoping an extraction to an entity from the outset, shared records, and access limited by subsidiary. NetSuite divestiture and entity separation.
File Cabinet and attachment preservation
The supporting documents are as much the record as the transactions: invoices, contracts, statements, and the link that says which bill each file supports. Preserving the folder structure, the files and their relationships before the account closes. Until its own page is built, the File Cabinet service is AcroFile.
Staying on NetSuite, or deciding the architecture
The account stays live, and the question is protection, portability or procurement rather than departure.
Independent backup and recovery readiness
A verified copy of the live account, held outside production, with daily, weekly and monthly recovery points, so that a deletion, a corruption or an incident has a known prior state to go back to. What a backup can restore and what it cannot. Until its own page is built, the service is AcroBackup for NetSuite.
Portable data, analytics and customer-hosted copies
The archive is not locked behind our interface: a MySQL database snapshot, the File Cabinet as files, CSV for selected datasets, and SQL connectivity for Power BI or a warehouse. What is portable, what is a separate project. Until its own page is built, the deliverables are described on AcroXtract and the hosting questions on DBVault.
Security, residency and controlled access
What procurement and security review before an archive is approved: hosting region, certifications and reports, multi-factor authentication and single sign-on, customer-controlled administration, retention for as long as your policy requires. Until its own page is built, the controls are set out in the Trust Centre.
Why every situation ends in the same two places
Each situation starts from a different event and asks a different question, and each of them needs the same two things done well. The records have to come out of NetSuite complete, with their relationships, their posting detail and their attachments intact, and verified against the source before access ends: that is AcroXtract. Then they have to be somewhere finance, auditors and successors can search and report from without a NetSuite licence, with access scoped per person and the data still exportable: that is DBVault. A company staying on NetSuite needs the same extraction run on a schedule rather than once, which is what the continuous backup service does. Where a situation is genuinely different, the page for it says how; where it is not, it says that too, and sends you to the page that already answers it.
Questions asked before choosing a page
We are in more than one of these situations. Which page should we read?
.webp)
Start with the event that has a date attached. A licence expiry or an ERP go-live sets the order of everything else, so read NetSuite decommissioning first; the audit, access and divestiture pages describe what the archive has to be able to do afterwards, and they apply whichever route you took to it.
Is this the same service under nine names?
No, and the pages are written so that the difference is visible. The extraction and the archive are the same two products in every case; what changes is the boundary of the work (one entity or the whole account, a frozen account or one still in use, a single extraction or a schedule), the proof the buyer needs, and what we say plainly that we do not do. Where two situations would get the same answer, one page carries it and the other links there.
Do we need DBVault if we only want the data out?
No. AcroXtract delivers the archive as a MySQL database snapshot and the File Cabinet as files, and the data can be supplied in CSV or MySQL form to a team loading another system. DBVault is where the archive lives when people need to search, report and scope access without a NetSuite licence; the portable-data situation page sets out what leaves with you either way.
We are staying on NetSuite. Is any of this for us?
The backup and recovery readiness situation is: a verified copy of the live account outside production, with retention points, for the day something is deleted or corrupted. It uses the same extraction on a schedule and the same archive platform for access. The other eight situations start from the account closing or changing hands.
What if our situation is not on this page?
Tell us what changed and what the records will be asked for. Four years of conversations produced these nine; a tenth would be worth hearing about, and the answer is usually one of the existing pages with a different starting point.
Tell us what changed
The subscription date, the new system, the audit, the sale or the restructuring. We will say which of the nine situations it is, what has to come out of NetSuite, and what it takes to have the archive in use before it matters.
.svg)
.svg)
.png)
.png)
