What a Dynamics GP migration actually costs

Every GP customer asks the same first question, and every vendor answers it with “it depends” and then a sales call. Both halves of that are annoying, so here is the useful version: what the industry data actually shows, what it depends on in your specific environment, roughly what the tiers look like, and where budgets actually blow up. No fake precision. Anyone who gives you an exact number before examining your databases is quoting their hopes, not your project.

What the industry data actually shows

Before getting into GP specifics, it helps to know what a typical ERP migration costs across the industry, because that number anchors every conversation you will have with a partner or a board.

Those figures come from Panorama Consulting Group’s 2024 ERP Report, an annual survey of 131 organizations that actually ran ERP projects.1 They are the closest thing the industry has to a defensible benchmark, and they matter for GP migrations for two reasons. First, they establish the honest baseline that “it depends” gets accused of dodging. Second, they come with an important caveat: Panorama’s sample skews toward much larger organizations than the typical Dynamics GP shop, with a median revenue around $200 million and a median headcount over 750 employees.1 Most GP customers run $10 million to $50 million in revenue with 50 to 200 employees, which is roughly a quarter to a tenth the size of Panorama’s median respondent. Scale the absolute dollar figure down proportionally to your own size and the underlying risk factors (not the headline number) are what actually transfer to your project.

On schedule, the same survey found 58.0% of projects finished on time, with 31.3% running late.1 Put budget and schedule together and roughly one in three ERP projects misses one or the other. That is not a reason to panic; it is a reason to plan against the specific causes, which the data also names.

The eight real cost components

1. Destination licensing. The recurring cost you will pay forever: per-user monthly subscription for Business Central, NetSuite, Odoo, or QuickBooks Online. Easy to quote, and therefore the number salespeople lead with. It is rarely the number that hurts in year one. See the pricing comparison further down this page for actual current rates.

2. Implementation and configuration. Partner time to set up the new system: chart of accounts design, posting setups, workflows, security roles. Scales with entity count and process complexity more than with headcount.

3. Data migration. Extracting master records and balances from the GP SQL databases, cleaning them, loading them, and reconciling. In practice this means pulling from tables like SY01500 (company master), RM00101 and PM00200 (customer and vendor master), and GL00100 (chart of accounts), then validating totals against the trial balance. Master records and opening balances are routine. What multiplies this line is the next item.

4. Historical transactions. The single biggest self-inflicted cost driver. Migrating years of posted history out of GL20000 and GL30000 (open and historical general ledger transactions), RM20101 and RM30101 (open and historical receivables), and PM20000 and PM30200 (open and historical payables) into a new system costs multiples of migrating opening balances plus open transactions. Most companies need lookup access to history, not history living inside the new ERP. A read-only GP archive answers audits and disputes at a fraction of the price, and it sidesteps exactly the kind of data-quality risk that Panorama’s respondents named as a leading cause of both budget and schedule overruns (more on that below).

5. Reports. Every SmartList favorite, modified Report Writer report, and Management Reporter (or FRx, and yes, FRx is still out there) financial statement your team relies on either has a native equivalent, needs rebuilding, or should die. The count of reports that need rebuilding is a direct cost line, and nobody knows the count until someone inventories it.

6. Customizations and integrations. Dexterity modifications, VBA on windows, ISV add-ons, Integration Manager jobs, and eConnect integrations to your website, warehouse, CRM, or bank. Each one is a decision (replace natively, rebuild, or retire) and every rebuild is developer time. Shops with untouched vanilla GP skip this line almost entirely; shops with a 20-year VAR relationship find this is half the project.

7. Payroll. If you run US or Canadian payroll in GP, you have both a harder deadline (tax table updates end December 31, 20292) and a costlier cutover: year-to-date balances, tax setup, benefits, and at least one full parallel pay run, often two or three. Moving payroll to a bureau instead of the new ERP is frequently cheaper and always simpler.

8. Training and internal time. The line item every budget forgets. Your controller and AP clerk will spend real hours on data validation, parallel runs, and learning new screens. It is not a check you write, but it is a cost you pay, usually during a month-end close.

Where budgets actually blow up

The overruns are predictable, which is exactly why they are preventable. Panorama’s 2024 survey asked organizations that went over budget why, and the answers form a clear pattern.

Every one of those five causes maps directly onto a GP migration decision you make in week one, not month six:

• “Unexpected need for additional technology” (51.2%) is what happens when nobody inventoried the ISV add-ons, the custom Dexterity forms, or the third-party tax engine bolted onto GP until testing surfaces them. A technical inventory before signing anything is the single cheapest insurance available.
• “Underestimated project staffing” (39.5%) shows up as the controller who was supposed to spend five hours a week on the project actually spending twenty, and nobody backfilling the close.
• “Organizational issues” (39.5%) is scope creep dressed as improvement, competing priorities from other departments, and decisions that sit unmade for weeks.
• “Data issues” (34.9%) is the GP-specific one. Dirty master data, unreconciled subledgers, and a decision to migrate more history than necessary all land here. The same survey found data issues cited by 46.3% of projects that ran over schedule as well, making it the most consistently named risk across both budget and timeline.1
• “Underestimated consulting fees” (32.6%) is what happens when a fixed-fee proposal did not actually fix the scope, so every discovery becomes a change order.

None of these are exotic risks. They are the same five things a well-run GP migration explicitly scopes for before a contract is signed.

What pushes cost up or down

Honest tiers instead of a fake number

Dollar figures vary by destination, geography, and partner rates, so treat these as shapes, not quotes.

Small. Single company, light customization, no in-house payroll, history archived rather than migrated. Typical destination: QuickBooks Online or a minimal Business Central setup. This is a low five-figure project measured in weeks. The main risks are data cleanup surprises and underestimating training.

Typical. One to three companies, a handful of customizations and integrations, a real report inventory, maybe payroll. Destination: Business Central, NetSuite, or Odoo. Mid to high five figures over 3 to 6 months is the honest center of gravity, with payroll or history migration capable of pushing it past that.

Complex. Many entities, deep Dexterity customization, several integrations, in-house payroll across US and Canada, regulatory reporting. This is a six-figure, 6 to 12 month program regardless of destination, and pretending otherwise in the budget only moves the pain to the steering committee later. This is also the tier that starts to resemble Panorama’s survey population, where the $450,000 median and 15.5-month timeline become a directionally useful reference rather than an outlier.1

Within each tier, implementation typically runs one to three times the first year of subscription licensing for the simple cases, and the multiple grows with customization. If a proposal shows licensing dwarfing services on a complex environment, something has been left out of scope, and you will meet it later as a change order.

What destination licensing actually costs

Licensing is the part every salesperson quotes cleanly, so here is the current list and typical pricing across the destinations GP customers actually choose. Treat vendor list prices as a ceiling; negotiated street pricing, especially at volume or through a reseller, commonly comes in below list.

NetSuite’s implementation range deserves a second look: $25,000 at the low end assumes a simple, single-subsidiary deployment, while $500,000 or more reflects multi-entity, multi-currency organizations with heavy customization.4 Most GP shops migrating to NetSuite land well inside that range rather than at either extreme, but the width of the range itself is the point: NetSuite pricing, like GP migration pricing generally, is negotiated per environment, not published as a fixed rate card.

How to spend less

1. Archive history; migrate opening balances and open transactions.
2. Clean master data inside GP before anyone quotes you, using the same customer, vendor, and item master tables (RM00101, PM00200, IV00101) the migration will eventually extract from.
3. Inventory reports, customizations, and integrations, then retire the unused before scoping the rest. This single step is the direct countermeasure to the 51.2% “additional technology” and 34.9% “data issues” overrun causes above.
4. Move payroll to a bureau unless there is a strong reason to keep it in the ERP.
5. Cut over at fiscal year end.
6. Start while 2029 is still comfortably far away. Partner calendars will fill as the deadline nears, and rush pricing is real in every migration wave.
7. Get bids that separate licensing, implementation, data migration, and training into distinct line items, so you can see exactly where a number is soft before you sign.

Turning this into your number

Everything on this page is a range because a range is honest and a single number is not, unless someone has actually looked at your GP company databases, your customization list, and your payroll setup. The industry benchmarks above tell you what to expect in aggregate and where the risk concentrates; they do not tell you your number.

A scoped estimate built on an actual inventory of your GP environment costs little and converts every range on this page into your number. That inventory is the first thing we build in an assessment, and it is worth having even if you never hire us.