Dynamics GP to QuickBooks Desktop: A Migration Playbook

A Dynamics GP to QuickBooks Desktop move succeeds or fails on preparation; this playbook covers account mapping, exports, history cutoffs, and go-live.

Dynamics GP and QuickBooks Desktop look similar on an organization chart and behave nothing alike in the data. GP keeps a segment-based chart of accounts, multiple open years, and its own inventory engine. QuickBooks works from a flat account list and plain calendar dates. A conversion between them is a data project, and it goes well when you treat it as one. This is the sequence our engineers follow.

Map the chart of accounts before anything moves

Start in GP, not QuickBooks. Export the account master with balances, mark every account active or inactive, and note the segment structure. A GP chart built on entity, department, and natural account cannot move as it stands, because QuickBooks has no segments. Each segment either maps to a class or a location (locations require Enterprise), or it folds into the account description.

Build a mapping spreadsheet with one row per GP account and one target QuickBooks account. Collapse accounts that exist only for reporting rollups. Leave GP's unit accounts behind; QuickBooks has no equivalent. Retained earnings needs no mapping either, because QuickBooks calculates it from prior years' net income.

When the mapping exposes deeper structural problems, fix them on paper first. Our bookkeeping notes on chart of accounts design cover the choices worth settling before a single record moves.

How many years of history should you bring over?

Three depths are possible. Full history imports every past transaction as journal entries; nothing is lost except drill-down, and the file grows heavy. Open-item conversion brings balances, open invoices and bills, and the current year's activity. Summary conversion brings monthly trial balances for a defined window.

Most conversions we run take open items plus summary balances for the current and prior year. That preserves year-over-year comparisons without importing a decade of noise. A 13-period GP calendar translates fine, because QuickBooks tracks dates rather than period numbers. Mind the list limits: Pro and Premier cap name lists at 14,500, and every imported customer and vendor counts against it. Leave inactive GP records out and keep them in a GP report instead.

Export the master records

Pull customers, vendors, items, and employees out of GP through SmartList or a direct SQL export to CSV. Export employees only if payroll will stay in QuickBooks; if payroll is moving to an outside service, a simple reference list is enough. Clean the data before it reaches QuickBooks: merge duplicates, fill blank fields, and standardize spellings. QuickBooks matches list entries by name, so two spellings of one vendor become two vendors permanently.

Classify every GP item as a QuickBooks inventory part, non-inventory part, or service, and assign its income, cost of goods sold, and inventory asset accounts in the mapping. Serial and lot tracking rarely maps cleanly, so decide the workaround before the import rather than after.

Export the open transactions

The open set is specific. It covers unpaid customer invoices, unpaid vendor bills, uncleared bank and card transactions, unapplied credits, open sales orders and purchase orders, and inventory on hand. Export each set with document number, original date, counterparty, amount, and remaining balance.

Inventory deserves its own decision. Quantities and values either arrive with the open transactions or through one inventory adjustment dated at the cutoff. Pick one method, because mixing both double-counts stock.

Build the file and test it against GP

Pick the edition first, because large item and name counts call for Enterprise. Create the company, import the mapped accounts, then the names, then the items. Enter or import opening balances and open transactions dated at the cutoff, and back up the file after every stage. Each backup is a rollback point. If the build stalls, this is the work our engineers handle through our Dynamics GP to QuickBooks conversion service.

Then test. Run a trial balance in QuickBooks as of the cutoff and compare it line by line to GP's trial balance at the same date. The receivables and payables aging reports must tie to GP's aging, and inventory valuation must tie to GP's stock status. Run Verify before you show the file to anyone.

Go live and reconcile the trial balance

Set a closing date and closing password in the new file so nothing posts before the cutoff. Freeze entry in GP and keep it readable rather than deleting it; staff will need to look things up for months.

Reconcile every bank and credit card account using the first statement that covers the cutoff. The opening balance entry appears as the first deposit or adjustment, and everything after it comes from live activity. At the first month-end, compare the trial balance and the aging reports against GP's final numbers, especially if you ran the two systems in parallel.

Keep a rollback point at every phase

GP stays untouched throughout; never delete it at go-live. Keep dated backups of the QuickBooks file after each import stage. Keep the mapping spreadsheet under version control; it is the audit trail for every balance in the new file. If a test fails, restore the last good backup and fix the source export. Patching a half-loaded file hides problems, while rebuilding from a clean stage exposes them.

What does a clean outcome look like?

The cutoff trial balance matches GP to the cent. Aging reports tie, and the first bank reconciliation completes without forced adjustments. Staff enter invoices, bills, and deposits without workarounds, and month one closes on time. GP sits read-only in the background, and the mapping spreadsheet explains every balance in the new file. That is a finished conversion.