Converting from Microsoft Dynamics GP (Great Plains) to QuickBooks
Moving off Dynamics GP to QuickBooks requires an export-and-map migration with no direct import tool. Here is what the conversion involves and where it stumbles.
Businesses transitioning away from Microsoft Dynamics GP — long known as Great Plains — to QuickBooks Desktop routinely discover that no direct conversion path exists. Intuit does not offer a tool that reads a Dynamics GP company database and rebuilds it inside QuickBooks. The migration is, at its core, an export-and-map project, and the bulk of the effort lies in deciding which mid-market ERP structures to carry forward and which to simplify for a small-business accounting platform.
What exports from Dynamics GP
The conversion focuses on accounting essentials. From GP, you export the chart of accounts, customer and vendor records, item lists, and the balances and open transactions as of a chosen cutover date. These elements are then mapped into the corresponding QuickBooks lists — Chart of Accounts, Customers, Vendors, and Items — with prior-period figures brought over as opening balances.
QuickBooks Desktop supports importing lists via structured spreadsheet files (CSV or Excel format), so the practical workflow involves exporting each GP list, reformatting the columns to match QuickBooks’ import templates, and importing them one list at a time. Opening balances for accounts, customers, and vendors are entered either during the import or through journal entries dated as of the cutover.
Where the account structure breaks
The single most common failure point is the chart of accounts. Dynamics GP uses a segmented account structure — for example, separating account, department, location, or division into distinct segments within a single account number. QuickBooks does not support multi-segment accounts in the same way. Those segments must be flattened into a single account number or redistributed across QuickBooks’ Class tracking and Customer:Job structure.
This remapping is where conversions most often go wrong. A GP chart with hundreds of segmented combinations can balloon into an unwieldy QuickBooks chart of accounts if every segment combination becomes its own account. The better approach is consolidating where the detail is no longer needed and using Classes to preserve departmental or divisional reporting without multiplying accounts unnecessarily.
What does not carry over
Several GP capabilities have no one-to-one QuickBooks equivalent. Multi-company and inter-company entries, analytical accounting dimensions, and complex ERP modules generally must be either consolidated into QuickBooks’ account, class, and job structure or handled outside the books entirely. Businesses that rely heavily on GP’s analytical accounting for dimensional reporting will need to redesign that reporting around QuickBooks’ native Class and Location tracking, which is less granular than what GP provides.
The clean-cutover approach
The accepted recommendation is a clean cutover rather than a full historical transaction migration. Under this approach, detailed activity begins in QuickBooks on a chosen go-live date. All prior history — account balances, open invoices, unpaid bills — is summarized as opening balances as of that date. Attempting to reproduce every historical GP transaction inside QuickBooks is generally impractical and adds risk without operational benefit.
Open transactions deserve particular attention. Outstanding customer invoices and unpaid vendor bills should be brought into QuickBooks as individual open items — not just rolled into a balance — so they can be applied against payments processed after the cutover.
Why this is typically handled as a service
Because of the account-structure mapping complexity and the ERP-to-QuickBooks simplification involved, a Dynamics GP conversion is typically handled as a professional migration service rather than a do-it-yourself import. The work involves scoping the migration, mapping segmented accounts and open items into QuickBooks’ structure, and verifying that the resulting file reconciles to the GP trial balance before go-live. Reconciliation against the final GP balances is the critical validation step — if the QuickBooks opening balances do not tie to GP as of the cutover date, the conversion is incomplete.
For businesses weighing whether to condense years of accumulated data as part of the move, condensing the company file before or during migration can reduce the volume of records being mapped and simplify the cutover.
Planning the cutover date
Most successful conversions target a fiscal year-end, quarter-end, or month-end as the cutover. This aligns opening balances with a natural reporting boundary and minimizes the number of mid-period transactions that need to be split between the old and new systems. Whatever date is chosen, the GP books should be fully reconciled — bank accounts, receivables, payables, and inventory — up to that date before the balances are exported, so that QuickBooks starts from a verified position.