.svg)
NetSuite Divestiture and Entity Separation: Keeping One Company's History When the Group Changes
A sale, an acquisition, a closed division or a restructuring draws a line through a NetSuite account that was never built to be divided. One side needs the leaving entity's history; the other needs to keep the rest without handing over the whole account. This page sets out what has to be agreed before anything is extracted, how a scoped archive is verified, who can see it afterwards, and what we do not offer. Other situations in which records leave an account are on the situations page.
When the group changes, the history has to follow the entity
A NetSuite account holds every subsidiary's records under one subscription. A corporate transaction changes who is entitled to which part of that history: the buyer of a business unit needs its ledgers and documents, an acquirer still has to produce the evidence behind the acquired company's opening balances, and a closed division faces audit and tax questions long after its last transaction. Three ways exist to keep the history; only one can follow the entity.
Keep the account open for the history
The records stay where they are for as long as someone renews the subscription, and access stays tied to NetSuite user seats. The history cannot be handed to a buyer or a former subsidiary without the account going with it: a licence cannot be divided along entity lines. That cost is set out on the caretaker licence cost page.
Take a one-off export
Quick, and usually a folder of CSV files with the relationships between records lost. Standard manual methods fail to capture complex data relationships and custom objects, and a folder cannot produce a trial balance for the subsidiary the buyer is taking on.
Extract a scoped archive
The entity's records, relationships and attachments are extracted with the boundary agreed at the outset, verified against the source, and hosted where the party that owns them can search and report without a NetSuite licence. The data stays theirs and exportable. This is what we do, with AcroXtract for the extraction and DBVault for the access.
What has to be agreed before anything is extracted
A separation archive is scoped before it is extracted, not filtered afterwards. The transaction defines the boundary; the work is to turn it into a dataset both sides can rely on, in this order.
1 · The boundary
Finance, legal and IT agree which entity or subsidiaries are in scope, which accounting periods and books, and which File Cabinet folders. That agreement is the specification for everything that follows.
2 · Dependency review
Records the entities shared are identified before extraction starts: customers and vendors that dealt with more than one company, items sold by both, books and files belonging to the whole group. Completeness depends on how these are allocated; the review decides what a coherent archive has to include.
3 · Account mapping and indexing
Every record type in scope is inventoried, including custom records and custom fields, and baseline counts are taken from the account itself.
4 · Scoped extraction
Transactions, entities, items, accounting records and attachments within the boundary are extracted into a relational database by AcroXtract, relationships intact. If people are still working in the account, a delta extraction brings across what changed before the cut-off.
5 · Verification and acceptance
The extracted records are compared against the source at the database level, then the party that will rely on the archive tests it against real questions before sign-off.
6 · Delivery
Access on DBVault for the authorised people, or the data in CSV or MySQL form for the team that will use it elsewhere.
What the separated archive has to hold
The GL impact of every transaction in scope, by subsidiary and period, so a trial balance can be run for the entity on its own.
Transactions with their lines, payments with their applications, journal entries with every line.
The customers, vendors, items and accounts those transactions resolve to, including the shared ones.
Each accounting book where Multi-Book is in use.
File Cabinet attachments linked to the records they support.
Custom records and custom fields, named as they were in the account.
Where the boundary is not clean
The difficulty in a separation is rarely the extraction; it is the records that belong to both sides at once. A date rule is easier to apply to transactions than to the master data behind them, and a coherent archive may need related records from outside the requested date or entity. We assess the boundary before promising completeness and say where a simple rule will not hold. We do not decide the allocation: purchase-accounting, legal-hold and retention rules are the parties' and their advisers' decisions.
How both sides know the dataset is right
In a divestiture the seller signs off a dataset it will no longer control, and the buyer relies on one it did not create. Neither should have to take the other's word for it, so verification runs in layers and acceptance is done by the party that will live with the result.
Automated comparison against the source
Extracted records are compared against the source account at the database level, not by a spot count, as a fixed step of every AcroXtract engagement.
Reconciliation to the group's own figures
Because the archive holds the GL impact of every transaction, a trial balance and general ledger can be run for the separated subsidiary and period and set against the group's own figures, book by book where Multi-Book is in use.
Relationships and attachments
Transactions still resolve to their customers, vendors, items and lines, and File Cabinet documents open from the records they support. This is the check a folder of exports fails.
Acceptance by the party that will rely on it
A formal validation period in which the receiving finance team works the archive against the questions it will be asked, with ticket-based issue reporting until sign-off. The checks a team can run itself are in How to verify a NetSuite export is complete.
Who sees what afterwards
After a separation, the people who need the archive are rarely the people who built it: the buyer's controller, a local finance team, an auditor for one entity. On DBVault each is given a named restriction profile, and the platform logs who looked and who exported.
Scoped to the subsidiary
A profile restricts which archives a person can open, which record types, which File Cabinet folders and which subsidiaries, each as an allow list or a deny list. A buyer's team can be limited to the subsidiaries it acquired; archives outside the profile are not shown.
Files only through records
Direct browsing of the File Cabinet can be switched off, so documents are reachable only as attachments on records the person may already see. Someone given the leaving entity's invoices cannot wander the group's document store.
Logged, not asserted
Login events and download history are kept inside the platform, so the question that follows a separation, who saw the other side's records and who exported them, has an answer. Restrictions apply to viewer roles; administrators cannot be restricted.
What this does not do
It does not split an existing archive into independent archives as a service. Where archived data later has to move, we assist with that migration and supply the data in CSV or MySQL form.
It does not load data back into NetSuite or into a successor ERP; that load is done by the team implementing the target system.
It does not decide purchase-accounting, legal-hold or retention rules, and does not review, interpret or classify the records.
It is cloud-hosted only; there is no on-premises option.
Workflows locked in the NetSuite user interface are not part of a data archive.
Situations in this family
Each of these is scoped, verified and hosted the same way and under the same boundary. What differs is who is entitled to the history and what they will ask of it.
A divestiture archive for the buyer
A business unit is transferred and both sides need an agreed dataset: the entity's GL history, transactions and selected attachments, without transferring the seller's whole account. Completeness depends on how shared customers, vendors, items, books and files are allocated.
An acquired company's history
The acquirer consolidates systems on its own platform but must keep the evidence behind the acquired company's pre-acquisition balances and transactions. The original records become a distinct archive; future operations run elsewhere.
A closed business unit
A division no longer needs an operational ERP but stays subject to audit, tax, contractual or corporate record-keeping. Its records stay accessible for the period the company and its advisers determine, without maintaining the environment that produced them.
Subsidiary-restricted access
A multi-entity group needs local teams, auditors or counterparties to see only their part of the archive. Restriction profiles scope each person to the subsidiaries, record types and folders their role covers.
Selected companies out of an existing archive
An archive customer later needs particular companies' data separated out for a new owner or system. Not a service we sell: the data stays exportable, we assist with the migration, and whether the boundary can be drawn cleanly depends on the shared records and the receiving system's needs.
A new NetSuite account for the new structure
A change of ownership or legal structure sometimes leads to a fresh NetSuite account. The old environment is kept as an independent archive rather than mixed into the new one; that situation is covered under NetSuite decommissioning.
When this is decided, and what shapes the cost
The useful moment is when the transaction defines the entity boundary and before the account that holds the history is closed or handed over. If the seller's NetSuite term ends with the deal, or the acquired company's account is shut down as systems consolidate, the archive should be in use before that date. If you are already inside that window, say so; the extraction is then scheduled around the date.
The sizing form on the AcroXtract page collects database size, File Cabinet size and user count, and a quote for the extraction and for DBVault hosting follows from those and from the agreed boundary. Hosting is an annual subscription with no licence to renew for the source system and no per-report charge. Where people keep working in the account until the cut-off, a delta extraction picks up what changed. This page quotes no figures; the comparison with keeping an account open to read it is on the caretaker licence cost page.
Engagements where the history had to follow the business
All case studiesA merger that left one company with two ERPs, an organisation winding down its operations, and a manufacturer whose data was carried onward when it changed platform. The write-ups describe what was extracted, how it was verified and what happened afterwards.
-
Case Study“From start to finish, the project was completed to our satisfaction in under a month.”
Brandon Carter, Managing Director of Financial Systems, Partner.CoClosing a second ERP after a merger: Partner.Co's NetSuite history exported in under a month
Read more -
Case Study“Not many providers can do what Blueacrobat Corporation does with their affordability and effectiveness.”
Yvan Masson, President of US Operations, BIAR SamplingBIAR Sampling: NetSuite data backed up, carried to a new platform and kept accessible
Read more -
Case Study
“We were delighted with their transparency, honesty, and fantastic communication. Very punctual and high quality outcomes.”
Chief Information Officer, education companyMeeting record-keeping obligations while winding down: a NetSuite archive for an education provider
Read more
Questions asked before a divestiture or separation
Can you extract just one subsidiary or business unit from our NetSuite account?
.webp)
Yes, as a scoped extraction agreed at the outset, subject to a review of the records the entity shared with the rest of the group. Customers, vendors, items, books and files often belong to more than one entity, and a coherent archive for the leaving business may need some of them. We assess the boundary before promising completeness.
We already have a DBVault archive. Can you split it into one archive per entity?
Splitting an existing archive into independent archives is not a service we offer. The archive is not a dead end: the data stays exportable as snapshots and CSV, and where entities are later separated we assist with the migration and supply the data in CSV or MySQL form. Whether a clean boundary can be drawn depends on the shared records and the receiving system; it is scoped case by case.
The buyer wants the history loaded into their own NetSuite account. Do you do that?
No. We do not load archived data back into NetSuite or into a successor ERP. We supply the data in CSV or MySQL form and work alongside the team doing the load; the load itself, with its mapping, dependencies and target configuration, is a separate project for the buyer's implementer.
Can the archive stop at the date the sale closed?
Sometimes. Transactions can be scoped by accounting date more readily than the master data behind them, and a coherent archive may need related records from outside the requested range, so date-bounded archival is assessed by record type during scoping rather than promised as a filter. Access controls afterwards are set by archive, record type, File Cabinet folder and subsidiary, not by date.
How do we give the buyer's team access without showing them the rest of the group?
Through a named restriction profile on DBVault that limits which archives they can open, which record types, which File Cabinet folders and which subsidiaries, each as an allow list or a deny list. Direct File Cabinet browsing can be switched off so files open only from records they may already see, and their logins and downloads are logged. Administrators cannot be restricted.
Who decides what the buyer is entitled to, and how long we have to keep the rest?
The parties and their advisers. We do not decide purchase-accounting, legal-hold or retention rules, and we do not review, interpret or classify the contents of the records. We extract what is in scope, verify it against the source, and give authorised users the means to search, view and export it, not legal or audit opinions.
Can the separated finance team still run a trial balance for their entity?
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 subsidiary, department, class or location, and audit reports such as the transaction journal, for the periods, subsidiaries and accounting books the archive holds.
Plan the archive for a separation or acquisition
Tell us which entity is leaving or arriving, what the transaction says about its history, and when the account that holds it closes. We will walk through how the boundary becomes a dataset, how both sides verify it, and how access is scoped afterwards.
.svg)
.svg)
.png)
.png)
