Why a NetSuite checklist needs a legacy data step
NetSuiteMost NetSuite implementation checklists cover scoping, design, migration, integrations, testing, training and cutover. Few say what happens to the history that is not migrated. Many implementations bring across master data, open transactions and opening balances, sometimes with summarized trial balances for comparison years, and leave the transaction detail in QuickBooks, Sage or an older ERP. When that subscription lapses or the server is retired, years of detail, attachments, memos and audit trails can disappear with it.
QuickBooksFor a company with 50+ full-time employees at peak (contractors excluded), that legacy history has two kinds of value. It supports audits, tax positions and disputes. It may also merit a permissioned licensing review before anything is archived or purged. Deciding where it lives is a CFO decision, best made before the implementation contract is signed.
The NetSuite implementation checklist
Scoping, before you sign with an implementation partner
- Name an executive sponsor and a day-to-day project owner inside the company.
- Document requirements by process: record to report, procure to pay, order to cash, payroll interface and revenue recognition.
- List legal entities, currencies and intercompany flows, and confirm the edition and modules that fit them.
- Inventory every system that will connect to NetSuite: CRM, payroll, expense, bill pay, e-commerce, warehouse, ticketing and planning tools.
- Agree in writing what the implementation partner owns for data migration and what the company owns.
- Hold a budget contingency for data cleansing and extra conversion cycles.
Design
- Redesign the chart of accounts and decide segments such as department, class and location.
- Define roles, approval workflows and segregation of duties.
- Specify the reports the board, lenders and management need from the first close.
- Draft the month-end close calendar for the new system.
Data migration
- Decide migration depth: master records, open receivables and payables, opening balances and how many years of summarized history.
- Clean and deduplicate customers, vendors and items before the first mock conversion.
- Run at least two mock conversions and reconcile each to the legacy trial balance.
- Get the controller's written sign-off on the final reconciliations.
The legacy data plan (the step most checklists skip)
- List every system being retired or downgraded, with the years of history it holds and approximate record counts, captured as metadata only.
- Decide where un-migrated history will live: a read-only subscription, a full export into company-controlled storage, or an archive service.
- Confirm the export includes transaction detail, attachments, memos and audit trails, not just balances.
- Name an owner for the archive and write down its retention schedule.
- Check retention obligations for tax, contracts and personal information before anything is deleted.
- Note which other systems tie to the ledger, such as CRM, support and project tools, and whether any of them are changing at the same time.
- Ask the owner whether the archive should get a permissioned licensing review before it is purged or the old vendor contract ends.
Testing and training
- Write user acceptance test scripts for each process and have process owners run them.
- Run a parallel close for at least one period if the timeline allows.
- Train by role, with short guides for approvers who will rarely log in.
Cutover and go-live
- Set and announce freeze dates for the legacy system.
- Load final balances and open items, then reconcile again.
- Agree go or no-go criteria in advance and hold a formal decision meeting.
- Plan hypercare support through the first close.
First 90 days after go-live
- Hold a post-implementation review after the first quarter-end close.
- Verify the legacy archive opens and is complete before cancelling the old subscription.
- Update the company's systems inventory to show which records now live where.
Where the legacy data decisions fall on the implementation timeline
NetSuite timelines vary with the number of entities, modules, integrations and the state of the data, so take durations from your implementation partner's statement of work rather than a generic plan. What does not vary is the order in which the legacy decisions have to be made.
| Phase | Legacy data decision due | What goes wrong if it slips |
|---|---|---|
| Before contract signature | Who owns migration and archive work, and how it is priced | Archive work becomes an unbudgeted change order |
| Design | How many years of summarized history come across | Comparison reports get rebuilt by hand every month |
| Mock conversions | Whether the legacy export includes detail, attachments and audit trails | Gaps surface after the old vendor relationship has ended |
| Cutover | Legacy freeze date and final export | Late transactions land in neither system |
| First quarter after go-live | Archive verified, old subscription cancelled or renewed on purpose | History is lost at the next renewal decision |
How to read the legacy data results
| Result | What it means | Next action |
|---|---|---|
| Full history exported to company storage, owner named | History is preserved and under the company's control | Record the years and systems covered in the systems inventory |
| Old system kept read-only, subscription renewing | History is reachable only while someone pays | Set a date to export before the next renewal decision |
| Only balances exported, old contract ending soon | Detail, attachments and audit trails are at risk | Negotiate a complete export before termination |
| Nobody owns the archive | It will be forgotten or deleted | Assign an owner and a retention schedule |
| Archive holds customer or employee personal information | Privacy and retention duties apply | Review with counsel before keeping, sharing or deleting |
Personal information in legacy archives is easy to overlook. If the company is subject to the California Consumer Privacy Act (CCPA), its notice at collection must state how long it keeps each category of personal information, and retention must be reasonably necessary and proportionate, under Civil Code section 1798.100. Other state laws and contracts can add obligations. This is general information, not legal, tax or financial advice.
Where a licensing conversation fits in a NetSuite project
A company replacing QuickBooks or an older ERP often has the profile AI labs and data buyers look for: years of finance and operations history, surrounded by CRM, support, project and communication systems. The companion page on when to switch from QuickBooks to NetSuite looks at the signals that trigger the move, and many of them also feed a licensing fit screen.
The CFO's job is to make sure the history survives the project and to ask the owner whether a review is worth exploring. You never export, upload or describe the records yourself. If the owner is interested, the company lists its systems and years of history in its own data inventory, and SourceX then tests fit against its baseline: a US company with 50+ full-time employees at peak (contractors excluded), a documented operating history of several years, clear rights to license what it holds, and an owner or executive able to sponsor the deal. Staffing clients need extra care because candidate records are personal data; see fractional CFOs for staffing firms. Implementation partners see the same moment from the other side, and their first-month referral plan shows how they raise it.
Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. Rewards become payable only after the buyer pays and SourceX receives its fee; a lead, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed. The reward is a share of SourceX's fee, so it never reduces what the company receives. The referral program overview for fractional CFOs covers the rest.
Red flags that should pause the legacy plan
- The legacy system mainly holds data the company processed for its own clients, not its own records.
- The vendor contract ends before a complete export can be produced.
- Older years were already deleted or the server was decommissioned without a backup.
- An acquired entity's books sit in the archive, and the purchase agreement left those records with the seller.
- The archive is mostly consumer personal information or protected health information.
- Nobody at the company can run an export or answer questions about what it contains.
Next step
Add the legacy data section to your next implementation kickoff agenda. If a client's history runs deep, get a preliminary read from the company fit checker, compare it with who qualifies, and register as a partner now, so you can act as soon as the owner agrees.