How to migrate from Dynamics GP to Acumatica
To migrate a client from Dynamics GP to Acumatica with superglue's AI agent, connect the client's GP database, and give superglue access to the client's Acumatica account. superglue assesses the data in minutes, plans every phase, recommends an answer to each decision, and runs a trial load that reconciles to the cent before cutover. You review, decide and sign off with the client.
Microsoft ends support for Dynamics GP on December 31, 2029, so most GP clients plan their move now.
What are the steps to migrate from Dynamics GP to Acumatica?
Migrating from Dynamics GP to Acumatica takes six steps: connect both systems, assess the data, plan every phase, decide the mapping, run a trial load and cut over. Each load repeats exactly what you tested, and every write waits for your approval.
- 01
Connect Dynamics GP and Acumatica
Connect the GP company database on SQL Server read-only. superglue writes nothing, and the client keeps working in GP until cutover. The client then gives superglue access to Acumatica.
- 02
Assess the Dynamics GP data
In minutes, superglue counts every record, finds the open items and lists the data issues with examples. You know the size of the migration before you quote it.
- 03
Plan every phase
superglue drafts the plan from discovery to cutover, with tasks, owners and the Dynamics GP specifics already in it.
- 04
Decide the mapping
superglue brings each decision below with a recommendation from the client's own data. You confirm or change each answer, and the client signs the mapping.
- 05
Run the trial load
superglue loads an Acumatica test tenant and compares it with Dynamics GP: the trial balance per period, the open receivables and payables per customer and vendor, and the inventory value. superglue explains every difference before cutover.
- 06
Cut over
At cutover, superglue loads the final data with the same steps as the trial load, and you sign the reconciliation with the client.
How do you get the data out of Dynamics GP?
- The client's IT creates a read-only SQL Server login for the GP databases, and the superglue gateway reaches the server on the client's network. GP user logins do not work for this.
- Ask whether history was ever removed with GP's Remove History utilities. Removed history is gone from the database.
- The client keeps working in GP until cutover.
The client installs the superglue gateway once: Connecting to on-prem systems
What needs to be configured in Acumatica?
The client adds an API user and a connected application for superglue. superglue configures Acumatica and loads the data through that access, in an Acumatica test tenant first, in this order:
- 01
The features the client licenses, such as subaccounts, multicurrency and projects.
- 02
The subaccount structure, companies and branches, and the chart of accounts.
- 03
The financial year and its periods, opened for every migration date.
- 04
Cash accounts, credit terms, taxes and numbering, then the preferences and classes of each module.
- 05
Customers, vendors and items, then the opening balances and the open items.
Access setup for the client: Acumatica configuration guide
What moves from Dynamics GP to Acumatica?
| In Dynamics GP | In Acumatica |
|---|---|
| Main account segment | GL accounts |
| Other account segments | Subaccount segments and branches |
| Customers and customer classes | Customers and customer classes |
| Projects | Projects and project tasks |
| Vendors and vendor classes | Vendors and vendor classes |
| Items and item classes | Stock and non-stock items |
| Checkbooks | Cash accounts |
Open items
Open receivables and payables documents, unapplied cash and credits, open sales and purchase orders, and inventory per site with its cost layers.
Open items load as AR and AP documents with their original numbers, dates and due dates, in an open financial period, so the aging in Acumatica matches on day one.
History
GP keeps unposted transactions in work tables and posted ones in history tables, and receivables, payables and the general ledger also keep open tables. superglue reads all of them, so nothing that moved to history is missed.
History loads as journal transactions per financial period, account and subaccount.
Which decisions do you make when you migrate from Dynamics GP to Acumatica?
- 01
How do GP account segments become subaccounts?
Acumatica has one account and a segmented subaccount, which fits the GP account format well.
superglue maps the main segment to the account and the other segments to subaccount segments, so GP reports keep their structure.
- 02
What happens to GP classes?
GP customer, vendor and item classes map directly to Acumatica classes.
superglue moves each class in use with its accounts and terms, and leaves out empty classes.
- 03
Which companies and branches does the client need?
In Acumatica, a company can have several branches. Branches drive balances, reports and access rights.
superglue recommends one company for each legal company in Dynamics GP, and branches only where the client reports per site.
- 04
Which classes carry the defaults?
Customer and vendor classes set the accounts, terms and other defaults for every record in them, and item classes set the units, the valuation method and the posting class.
superglue proposes classes from the groups the client already uses, so each record gets its defaults from its class.
- 05
How much history moves?
Most clients need the open items plus one to two years of monthly balances in Acumatica, and older years as yearly balances. The client keeps the older detail in an archive.
superglue recommends two years of monthly balances per account, and full transaction detail only where the client needs to look into single transactions.
What are the common challenges when you migrate from Dynamics GP to Acumatica?
Old reports often show only part of a module
GP keeps unposted, open and fully applied transactions apart, and many client reports read only some of them, so a subledger total rarely matches the general ledger at first. Agree one starting number with the controller. superglue reads all of them and reconciles each module to that number.
Unposted batches hide real invoices and payments
Batches that were entered but never posted are missing from the trial balance, yet they often hold real invoices and payments. Ask the client to post or delete them before each extract. superglue lists them, so nothing goes missing at cutover.
Customer, vendor and item classes set defaults that records override
Customer, vendor and item classes hold default posting accounts, and many records override them. superglue finds the overrides and proposes the defaults for the new system.
Multi-company clients need an intercompany plan
Clients with several companies keep one database for each, with intercompany balances between them. Agree early which companies merge, which become entities, and how the intercompany balances settle. superglue reads every company and matches the intercompany balances.
Brief the controller on equity accounts
Acumatica has no equity account type, so equity accounts are set up as liability accounts and shown as equity on the balance sheet. Controllers who read the account list often ask about it, so explain it before they see it.
Finish the preferences before the first trial load
Acumatica does not load the records of a module until that module's preferences are complete. Put the preferences in the configuration plan ahead of the first trial load.
superglue also runs the rest of the Acumatica project. See the Acumatica implementation
Frequently asked questions
Which data moves from Dynamics GP to Acumatica?
The chart of accounts, customers, vendors and items, the open items, and as much history as the client needs. The mapping table on this page shows where each record lands in Acumatica.
Does superglue write to Acumatica without my approval?
No. superglue only reads Dynamics GP. Before any write to Acumatica, it shows the target, the connection and a transformed sample, and waits for your approval.
How do I know the migration is complete?
superglue reconciles the trial load and the final load against Dynamics GP: the trial balance per period, the open receivables and payables per customer and vendor, and the inventory value. You get a reconciliation report to sign with the client.
What happens when I start this migration?
You sign up and connect the client's systems. If you want to see a full migration run first, superglue can set up Pinecrest Supply, a sample client.
Start your Dynamics GP to Acumatica migration
Sign up and connect the client's systems, or let superglue set up Pinecrest Supply, a sample client, to see a full migration run first.