NetSuite decommissioning

NetSuite Decommissioning: What Has to Happen to Your Data Before the Account Closes

A NetSuite account can be switched off in an afternoon. The obligation to produce its records lasts for years. This page sets out what has to come out of the account, in what order, how you know the extraction is complete, and how finance and auditors keep working with the history once the subscription has ended. It draws on decommissioning engagements we have delivered since 2023.

The decision that outlasts the ERP

Most decommissioning projects are run by the team implementing the new system, and the old system's history is the last item on the plan. It is also the item auditors, tax authorities and your own finance team will ask about for years afterwards. Retention obligations are measured in years; the migration is measured in weeks. Whatever you decide about the history has to hold for the longer of the two. There are three ways companies keep NetSuite history.

A quiet server hall with one rack still lit, the rest switched off

Keep the account open only to read it

Nothing has to be extracted, but the licence keeps renewing for data nobody enters any more, access stays tied to NetSuite user seats, and the history cannot be handed to a buyer, a subsidiary or a successor system without the account coming with it.

Take a one-off export

Cheap and quick, and the usual result is a folder of CSV files with the relationships between records lost. Standard manual methods fail to capture complex data relationships and custom objects, which is exactly what an auditor asks for first.

Extract into a hosted, read-only archive

The records, their relationships and the attachments are extracted once, verified against the source, and kept in a system your finance team can search and report from without a NetSuite licence. The data stays yours and stays exportable. This is what we do, with AcroXtract for the extraction and DBVault for the access.

What has to come out, and in what order

An extraction that will stand up to an audit is a project with a fixed sequence, not a set of saved-search downloads. Ours runs in six steps, and the two that take longest are the two most often skipped.

1 · Account mapping

Every record type in the account is inventoried, including custom records and custom fields. You cannot verify what you did not know to extract.

2 · Indexing

Baseline counts and structures are captured from the account itself, not from the export.

3 · Database creation

A relational database is built to hold the records with their relationships intact.

4 · Record extraction

Transactions, entities, items, accounting records, System Notes and File Cabinet attachments are extracted into it by AcroXtract.

5 · Verification

Automated database-level comparison of the extracted records against the source account, then financial reconciliation.

6 · User acceptance

Your team works the archive against real questions, with issues logged and resolved before sign-off.

Two long corridors of records, one lit, one dark

What the archive has to preserve

General ledger detail and the GL impact of each transaction, by subsidiary and by period.

Multi-Book accounting, reconciled book by book.

System Notes and audit trails, so a change made years ago can still be explained.

Custom records and custom fields alongside the standard record types.

Entity relationships: transactions resolve to their customers, vendors, items and subsidiaries.

File Cabinet attachments, linked to the records they belong to.

If people are still working in NetSuite

Most companies keep transacting in NetSuite until the go-live of the new system. A full extraction taken weeks earlier is then incomplete by definition. A delta extraction identifies what changed after the full pass, using record hashing, and brings it across before the true cut-off, followed by a mandatory re-verification of the combined set. It is the step most often left out of a decommissioning plan, and the one that decides whether the archive matches the account on its last day.

How you know the extraction is complete

A matching row count proves that rows arrived. It does not prove that the values are right, that the relationships survived, or that inactive records and custom fields were included. Verification therefore runs in layers.

A trial balance on a desk at dusk, the office behind it already empty

Automated comparison

Extracted records are compared against the source account at the database level, not by a spot count, as the fifth step of every AcroXtract engagement.

Financial reconciliation

Trial balance and general ledger by subsidiary and period, and each accounting book where Multi-Book is in use.

Relationships and attachments

Transactions still resolve to their entities and line items, and File Cabinet documents to their records.

User acceptance

A formal validation period in which your finance team tests the archive against the questions it will actually be asked, with ticket-based issue reporting until sign-off. The checks a team can run on its own export are in How to verify a NetSuite export is complete.

Access after the subscription ends

The archive is hosted read-only on DBVault. Records cannot be modified after finalisation, and an auditor, a controller and a former subsidiary's finance lead can each be given exactly the scope they need. The data stays exportable as snapshots and CSV, so the archive is never a dead end when the business changes again.

Search and navigate

Structured filtering across transactions, the general ledger and the File Cabinet, with links preserved from records to their original documents.

Financial reports

Trial balance and income statement run from the archived data, for the periods the account covered.

Scoped access

Single sign-on with multi-factor authentication and role-based permissions; read-only for everyone.

What this does not do

It does not load data back into NetSuite or into a successor ERP. Where you are migrating, we work alongside the team doing the load and supply the data in CSV or MySQL form.

It is cloud-hosted only; there is no on-premise option.

Workflows locked in the NetSuite user interface are not part of a data archive.

When to start

Plan for a project window measured in months rather than weeks, and expect most of it to be validation, not extraction. Start from the date the account will close, or the renewal you intend not to pay, and work backwards. Where the deadline is already close, we have delivered complete extractions in days; the engagements below include several.

Decommissioning engagements since 2023

All case studies

Each of these companies left NetSuite or retired an account and needed its history to remain reachable. The write-ups describe what was extracted, how it was verified and how long it took, from February 2023 to February 2026.

Questions asked before a decommissioning

Can we keep using NetSuite until the new system goes live?

Yes, and most companies do. The full extraction is taken early, and a delta extraction brings across everything that changed up to the true cut-off, followed by a re-verification of the combined set. The archive then matches the account on its last day rather than on the day the project started.

What if we only keep a read-only NetSuite account for the history?

It works until someone needs the history outside NetSuite: a buyer of a business unit, a subsidiary that is now a separate company, an auditor who wants a dataset rather than a login, or a finance team that has moved to another system. A hosted archive keeps the data yours and exportable; an account keeps it inside NetSuite for as long as you keep paying.

Do you load the data into our new ERP?

No. We extract, verify and archive; the load into a destination system is done by the team implementing it. We supply the data in CSV or MySQL form and work alongside that team where a migration is running.

How do we know nothing was missed?

Verification compares the extracted records against the source account at the database level, reconciles the financials by subsidiary, period and accounting book, and checks that relationships and attachments survived. Your team then has a formal validation period to test the archive against real questions before sign-off, with every issue logged and resolved.

Who can use the archive afterwards, and how?

Anyone you authorise, through single sign-on with multi-factor authentication and role-based permissions. Finance can filter and navigate transactions, the general ledger and the File Cabinet and run financial reports such as the trial balance and income statement; auditors can be given read-only scope for the period they are examining.

Is the archive a dead end for the data?

No. Records stay exportable as snapshots and CSV, and we assist customers whose archived data later has to move again, for example when a corporate structure changes. What we do not offer is a productised load back into NetSuite.

How long does a decommissioning project take?

Plan in months, not weeks, and expect validation to take longer than extraction. The elapsed time depends on account size, customisation and how much of your team's time is available for user acceptance. Where a deadline is fixed and close, complete extractions have been delivered in days; the engagements above include several.

What do you need from us to start?

Access to the account, a contact who knows its customisations, and the date it will close. The sizing form on the AcroXtract page collects database size, File Cabinet size and user count, which is what a quote is based on.

Plan your NetSuite decommissioning

Tell us when the account closes and who will need the history afterwards. We will walk through what has to come out, how it is verified, and what it takes to have the archive in use before the licence ends.

Thank you for your inquiry.

One of our representatives will be happy to get back to you within one business day.
Oops! Something went wrong while submitting the form.