.svg)
Access to NetSuite Data After You Cancel: Your Options for Legacy Records
When a NetSuite subscription ends, the records do not come with you. They stay inside an account that is reachable only while someone pays for it. This page compares the three ways companies keep access to that history, describes what a legacy archive has to hold to be useful, and shows how access is scoped and proven once the ERP is gone.
What ends with the subscription, and what does not
NetSuite access ends on the last day of the term. The obligations attached to the records do not: retention rules are measured in years, auditors come back for closed periods, tax authorities ask about old filings, former customers and suppliers dispute old invoices, and a buyer of a business unit wants that unit's history. Every one of those requests needs someone who can open the records and produce them in a form the asker can use.
A read-only NetSuite account
Keeps the records where they are and visible to the people with seats. The renewal continues for data nobody enters, access stays tied to NetSuite users, and the history cannot be handed to a buyer, a former subsidiary or a successor system without the account going with it. A licence cannot be divided along entity lines when the corporate structure changes.
A one-off export
Quick and inexpensive, and usually a folder of CSV files. The relationships between records are lost in the flattening, custom objects are commonly missed, and nobody can run a trial balance from a folder. It answers the question of ownership and fails the question of usefulness.
A hosted, read-only archive
The records, their relationships and the attachments extracted once and verified against the source, then hosted where finance, auditors and successors can search, filter and report without a NetSuite licence. The data stays yours and exportable. This is what we deliver, with AcroXtract for the extraction and DBVault for the access.
What a legacy archive has to hold to be useful
An archive that can answer an auditor is not a table of invoices. It is the whole account, organised the way the account was, with the links between records intact. In practice that means the following groups, each with its line items and sublists.
Transactions, with their lines
Sales (estimates, sales orders, invoices, cash sales, refunds, returns), purchasing (purchase orders, item receipts, vendor bills and credits), payments and their applications, deposits and checks, inventory movements, and journal entries with every line.
The general-ledger effect of each one
GL Impact is held per transaction. It is what makes a trial balance, a balance sheet or an income statement possible from an archive, and it is the technical answer to how financial statements exist without NetSuite.
Entities and company structure
Customers, leads, prospects, vendors, contacts, employees and partners; subsidiaries, departments, classes, locations, terms and tax types, so every transaction still resolves to who and where.
Accounting and items
The chart of accounts, the full item set including assemblies and kits, inventory balances, sales tax items.
Files, activities and support
The File Cabinet with its folder structure and each file attached to the record it belongs to; events, calls, tasks, messages and notes; support cases and solutions.
Custom records, by name
Custom records come across as first-class record types, including SuiteApp-generated sets such as Fixed Asset Management. This is where manual exports most often fail.
Finding a record in it
Universal search across the archive, filtered by transactions, entities, items, accounting, custom records or other.
Searchable by transaction and document number, entity and external ID, name, company, e-mail, phone and memo; internal IDs matched exactly.
Records reproduced as documents with PDF print templates, for example an invoice for a dispute.
Snapshots and CSV exports as first-class sections, so the data can leave when it needs to.
The extraction that fills the archive is AcroXtract; the archive itself, with its search, reports and access controls, is DBVault.
Who can see what, and can you prove it
"Role-based access" is a claim every vendor makes. What matters to a compliance reviewer is the mechanism. In DBVault, access for viewers is set through named restriction profiles that constrain four independent things, and the platform logs who looked and who took what out.
Four axes of restriction
Which archives a person can open, which record types, which File Cabinet folders and which subsidiaries. Archives outside the profile are not merely locked; they are not shown.
Allow list or deny list, per axis
Each axis works as "everything except what is listed" or "only what is listed". Saying that a user can see two record types in one subsidiary and nothing else is a different claim from "granular permissions".
Logged, not asserted
Login events and download history are kept inside the platform, so the second compliance question, who saw it and who exported it, has an answer.
The auditor profile, in practice
An external auditor is given a profile scoped to the archive, the subsidiary and the record types their engagement covers, with direct File Cabinet browsing switched off so files are reachable only as attachments on records they may already see. The profile is named for its purpose, reused for the next auditor, and assigned at invitation. Two things are worth stating plainly: restrictions apply to viewer roles, and administrators cannot be restricted. A reviewer will assume that anyway; saying it removes a discovery from the vendor assessment.
Reporting after NetSuite
Because the archive holds the GL impact of every transaction, financial reports run from the archived data rather than from a spreadsheet someone rebuilt. The set covers the statements an auditor asks for and the management views a finance team uses.
Financial statements: cumulative and consolidated trial balance, period activity, balance sheet, income statement, general ledger, account activity, chart of accounts, transaction detail.
Management reports: P&L by department, class, location and subsidiary; revenue by customer; expenses by vendor.
Multi-currency: trial balance by currency and FX analysis.
Audit and compliance: transaction journal, period comparison, account type summary, reversals.
Support is raised inside the platform, against a specific archive, with attachments, and tracked as a ticket. For an organisation whose ERP is gone and whose records now live with a supplier, that answers the procurement question of who to call in three years and whether it goes anywhere.
Consolidated balance sheet, two year-ends side by side. Sample document with fictitious figures.
Statement of changes in equity across two years. Sample document with fictitious figures.
When the data has to move again
An archive is not the last stop for the records. Companies restructure, sell business units and change platforms again, and the history has to follow. Because the data is held as records rather than as a licence, it can.
Snapshots and exports you control
User-accessible snapshots and CSV export are part of the platform. The data is not locked behind a proprietary format or a request to us.
Migrations involving the archive
Where archived data later has to move, for example after a divestiture or a group restructuring, we assist with that migration. A licence cannot be divided along entity lines; a dataset can.
What we do not do
We do not load archived data back into NetSuite or into a successor ERP; where a migration is running, we work alongside the team doing the load and supply the data in CSV or MySQL form. Hosting is cloud only, and workflows locked in the NetSuite interface are not part of a data archive.
What hosting depends on
The AcroXtract sizing form collects database size, File Cabinet size and user count, and a quote for the extraction and for DBVault hosting follows from those three. There is no licence to renew for the source system and no per-report charge. Compare that shape with an account kept open only to read it: one is sized once for the data you have, the other renews for as long as you might need it.
Companies whose NetSuite history is still in use
All case studiesEach of these organisations left NetSuite or retired an account and kept working with the records afterwards: for audits, for record retention, for users who still needed to look things up. The write-ups describe what was kept and how it is used.
Questions asked about access after NetSuite
What actually happens to our data when we cancel NetSuite?
The records stay inside NetSuite, and NetSuite is reachable only through an active account. Nothing is handed to you at the end of the term. If the history has to be produced later, for an audit, a tax query or a former customer's question, someone has to be able to open it, which means either an account you still pay for or a copy you took out before the end.
Is a read-only NetSuite account enough?
It keeps the records visible to the people with seats, for as long as the account renews. It does not give you a dataset you own, it cannot be handed to a buyer or a former subsidiary, and it cannot be split along entity lines when the corporate structure changes. A hosted archive is the option that gives you the data itself, exportable, with access you scope.
Who can see what in the archive?
Access is granted per person through named restriction profiles. A profile limits which archives a user can open, which record types, which File Cabinet folders and which subsidiaries, each as an allow list or a deny list. Direct browsing of the File Cabinet can be switched off so files are reachable only as attachments on records the person may already see. Administrators cannot be restricted; that is stated plainly rather than hidden.
Can we prove who looked at what?
Yes. Login events and download history are logged inside the platform, so you can answer who opened the archive and who took what out, which is the question a compliance reviewer asks after who can see what.
Can our finance team still run financial statements?
Yes. Because the archive holds the GL impact of every transaction, financial reports run from the archived data: trial balance, balance sheet, income statement, general ledger, P&L by department, class, location or subsidiary, and audit reports such as the transaction journal.
What if the data has to move again later?
Records stay exportable as user-accessible snapshots and CSV, and we assist customers whose archived data later has to move, for example after a divestiture or a change of corporate structure. What we do not offer is a productised load back into NetSuite.
How do we give an auditor access without giving them everything?
Create a profile scoped to the archive, subsidiary, record types and period their engagement covers, with direct File Cabinet browsing switched off, and assign it at invitation. The product's own guidance uses exactly this example. Nothing else in the tenant is visible to them, and their logins and downloads are logged.
What does hosting cost depend on?
The sizing form collects database size, File Cabinet size and user count; a quote follows from those three. There is no per-query or per-report charge, and there is no licence to renew for the source system.
Plan access to your NetSuite history
Tell us who will need the records after the account closes and what they will ask of them. We will walk through what the archive would hold, how each person's access is scoped, and what it takes to have it in use before the subscription ends.
.svg)
.svg)
.png)
.png)
.svg)
.svg)
.svg)
