NetSuite to QuickBooks Desktop conversion: the cutover playbook

NetSuite to QuickBooks Desktop moves stall on truncated exports, project mapping, and open inventory and tax questions; this playbook orders the cutover.

Most NetSuite to QuickBooks Desktop conversions do not fail on the arithmetic. They fail on a truncated export, a project list with no agreed landing spot, and tax or inventory decisions taken after the cutover. Our engineers run these moves in a fixed order. This page is that order.

Scope the move before you export anything

Three decisions shape the whole project, and none of them involve data yet.

First, decide how much history converts. Full history is possible; a balances-forward start date is smaller. You post opening balances and open documents as of that date and leave older detail archived in NetSuite.

Next, count the lists: chart of accounts, customers, vendors, and items. These counts drive the effort on any conversion, ours included, so gather them before asking for a quote.

The destination is the third call. A new company file is the clean default. Folding the data into an existing file is workable, but it stacks a second project on top; our page on merging two QuickBooks company files explains why.

Settle the deal-breaker questions early

Two source conditions stop the migration outright. A dataset with more than one currency, or with multiple subsidiaries, does not convert as it stands. Consolidate to one base currency and one subsidiary first. A second currency that was never used still counts, so clear it before exporting.

Sales tax comes next. Confirm whether you use it, then decide how each NetSuite tax code maps to a QuickBooks tax code.

Inventory drives difficulty more than anything else. Flag whether you use plain inventory, item assembly, or kits and packages. Kits have no direct QuickBooks equivalent; they become group items or get flattened, which is a mapping decision rather than a technical one. Some firms drop inventory tracking entirely; our write-up on converting QuickBooks inventory items to non-inventory covers what that costs in history and valuation.

Edition matters here too. Assembly and Advanced Inventory features live in QuickBooks Enterprise, so confirm the destination edition before the mapping is fixed.

Export the transaction detail in full

In NetSuite, open Transactions, then Management, then Search Transactions. Click Submit to run the search, then Export CSV. Before uploading anything, compare the row count in the file against the result count NetSuite displayed. They must match exactly.

If the search exceeds 100,000 lines, split it into date ranges and export each range separately. Open every file and confirm the last row is a real transaction, not a clean-looking boundary. Truncation is silent; the count comparison is the only reliable check.

Export the lists the same way: accounts, customers, vendors, and items, with names and internal IDs. Date the export set and keep it. If anything re-runs later, the re-run should start from identical bytes.

Map NetSuite projects to QuickBooks jobs

Desktop has no separate project list. A job is a child of a customer, so each NetSuite project lands as a job under its parent. The conversion is mechanical once the structure is documented, and documenting it falls to you.

Before exporting, capture screenshots of how projects are organized: which customers carry projects, which stand alone, how sub-projects nest. Those screenshots set the parent and child on every row. Fix a naming convention at the same time, because Desktop displays projects as Customer:Job and long names get cut off in reports.

Freeze the source, then convert and validate

Pick a cutover date and stop posting in NetSuite from that day, or lock the period. The export set must describe a closed world.

Hand over the dated exports, the counts, the screenshots, and the mapping decisions. If we run the move, that means our NetSuite to QuickBooks conversion service; you receive a QuickBooks company file back.

Validate before anyone books live work. The trial balance at the cutover date must tie to NetSuite. A/R and A/P aging totals must match, along with inventory valuation if you carried it. Every project in the screenshots must appear as a job. Reconcile one bank account end to end.

Rollback is cheap by design here. NetSuite is untouched by exporting, so the source of record survives every failed attempt. The destination is a new file, so a failed validation means discarding it and re-converting from corrected exports, never patching in place. Keep the NetSuite login alive until sign-off.

The checks that confirm a clean conversion

A clean conversion is boring, and boring is the goal. The balance sheet and profit and loss for the converted period tie to NetSuite. Both agings match down to the customer and vendor. Item counts and the inventory asset balance match. The file passes Verify with no errors, and the first bank reconciliation clears.

Only then do you decommission NetSuite. Archive the final export set beside the closing reports, because the old system remains your rollback until the new file has survived a full monthly close.