QuickBooks to NetSuite at a growing distributor: what history to bring

What history should a distributor bring into NetSuite?#

A distributor moving from QuickBooks to NetSuite usually brings three things: open transactions, balances as of the cutover date, and enough summarized history to run comparisons. Everything older tends to stay in the QuickBooks file and in exported reports, where it remains available without being mapped into NetSuite records.

The decision turns on who will use old data and how often. A controller preparing year-over-year statements needs monthly account balances. A sales manager reviewing what a customer bought before the switch needs item-level history. A buyer setting reorder points needs demand by item and location. Each need points to a different import level, and the cheapest answer that serves real users is usually right.

Agree on the answer before the implementation partner builds import templates. Changing history scope after mapping has started is where migration budgets and go-live dates tend to slip.

Balances only, summarized history or full detail?#

The three history options differ in what lands in NetSuite, what the team can report on afterward, and how much mapping and reconciliation work each creates. The table compares them for a typical wholesale distributor.

Many distributors settle on a hybrid: summarized general ledger history in NetSuite, plus a separate item sales history for active customers loaded as custom records or kept in a reporting tool. That keeps the ledger clean while giving sales the purchase history they ask for most.

What must move no matter which option you pick?#

The cutover data set is the same under all three options, because NetSuite cannot run the business without it. Getting these records right matters more than any history decision, and most go-live problems trace back to one of them.

• 1Customer master: bill-to and ship-to addresses, terms, credit limits, tax status and exemption certificates, sales rep and price level.
• 2Vendor master: remit-to addresses, payment terms, tax reporting status and vendor part numbers.
• 3Item master: item numbers, descriptions, units of measure and conversions, costing method, reorder settings and default bins or locations.
• 4Price levels and customer-specific contract prices that reps quote from every day.
• 5Open AR invoices and unapplied payments and credits, with original dates so aging stays correct.
• 6Open AP bills and vendor credits.
• 7Open sales orders, including backorders and drop-ship lines, and open purchase orders with expected receipt dates.
• 8On-hand quantity and value by item and location from the cutover count.
• 9An opening trial balance that ties every subledger to the general ledger.

Where distributors get tripped up#

Distributors get tripped up by inventory more than by accounting. QuickBooks keeps a simpler inventory model than NetSuite, so costing, units of measure and locations need decisions that a services firm moving the same ledger would never face.

Costing comes first. The costing method chosen in NetSuite may differ from how QuickBooks valued items, so inventory value at cutover has to be agreed and tied to the general ledger item by item. Units of measure come second: if fittings sold by the each in one QuickBooks item and by the case in another, the NetSuite item design must settle base and sale units before any history can map to it.

Names are the third trap. QuickBooks lists often carry duplicate items, retired items renamed with a z prefix, and customers that are really ship-to locations of one account. Cleaning these before import is far cheaper than after, and it decides whether historical detail can map at all.

How do you keep the QuickBooks file usable after cutover?#

The QuickBooks file stays usable when finance preserves it deliberately rather than leaving it on someone's laptop. Old history only helps if the team can open it, find a document and explain it to an auditor, a tax examiner or a customer disputing an old invoice.

The retention clock is set by tax rules, not by the go-live date. The IRS says records supporting income, deductions or credits should be kept until the period of limitations for that return runs out, generally 3 years and longer in some cases, and Rev. Proc. 98-25 treats machine-sensible records in an accounting system as records that must be kept while they may become material to tax administration. A QuickBooks company file is exactly that kind of record, so the decision to retire it belongs with your tax advisor.

Mapping sheets are the piece teams lose most often. Without them, nobody can say which NetSuite customer an old QuickBooks invoice belongs to, and the history becomes much harder to analyze or to describe in any later review.

• 1Make a final backup of the company file after the last close in QuickBooks, and record the product, edition and version that opened it.
• 2Decide how access will continue: a retained desktop license, a read-only arrangement or a complete set of exports. Check Intuit's current terms for what remains available after a subscription ends.
• 3Export detail reports to CSV and PDF: general ledger detail, transaction lists by customer and by vendor, sales by item detail, inventory valuation and monthly trial balances.
• 4Save attachments, memos and invoice notes that standard reports leave out.
• 5Keep the account, customer, vendor and item mapping sheets that show how each QuickBooks record became a NetSuite record.
• 6Keep the backup and exports on company-controlled storage, name a custodian in finance, and set the retention period with your tax advisor.

Illustrative: a fittings distributor picks summarized history#

Illustrative: a fictional industrial fastener and fittings distributor with two warehouses moves from QuickBooks Desktop Enterprise to NetSuite after adding a second location and an online ordering portal. The CFO's first request comes from sales, who want full invoice history in NetSuite.

The team asks who actually needs old detail. The controller needs monthly comparatives, which summarized ledger history covers. Sales needs item purchase history, but only for active accounts. The CFO approves monthly summary journal entries plus an item sales history table for active customers, loaded as custom records.

Everything else stays in the preserved QuickBooks file and exported detail reports, with mapping sheets. After go-live, auditors tie comparatives to the QuickBooks trial balances, reps see customer purchase history, and old credit memo questions are answered from the exports without reopening the migration.

Why old transaction detail still matters after go-live#

Old transaction detail matters after go-live because it records how the business actually ran: which customers bought what, when prices changed, and how returns and credits were handled. That history feeds forecasting and pricing reviews, and for some distributors it becomes relevant to licensing records to AI developers who need real order and exception workflows.

A general ledger alone carries little signal for that purpose. Value comes from linked records: orders tied to quotes, credit memos tied to the reason for the return, and notes that explain decisions. The SourceX Enterprise Data Value Framework weighs drivers such as scale, recency, data cleanliness and rights, while preparation cost and privacy burden reduce net value, so a documented archive with mapping sheets is far easier to assess than an unopened backup.

When a distributor asks SourceX to look at its history, the first step is a metadata-only fit check covering systems, years and record families. Nothing is exported at that stage, and the company approves each later step of the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery.