Microsoft Dynamics GP traces its roots back more than four decades, to its origins as Great Plains Accounting in the early 1980s. Most companies implemented today’s GP many years ago. Considering the timelines, it’s unlikely that you were working at your current company and part of the ERP implementation team when GP was installed, so the current wave of Microsoft messaging around Dynamics 365 Business Central (BC) is likely the first migration conversation many teams have had to navigate.
By now you know you aren’t required to migrate on Microsoft’s timeline. But you may still be weighing whether a move to BC makes sense at all, and if so, when. Let’s talk through what that decision actually involves, and why “staying and modernizing” is a legitimate answer of its own.
What Does “Migration” Actually Mean?
FACT: Moving from GP to BC isn’t an upgrade. It’s a full reimplementation of a different ERP.
Every industry has its euphemisms, but the software industry has a vast number of them. In this case, the word migration is a euphemism for “a full reimplementation of a new ERP,” because GP and BC are entirely different ERP solutions with entirely different architectures. And they were built to meet entirely different business needs.
That reimplementation touches nearly everything. You’re reassessing which GP modules, customizations, and add-ons you actually use, remapping your data, and rebuilding reports and workflows for BC’s different, web-based interface. On top of that, your team needs to retrain on a system that looks and behaves nothing like GP. None of it is a knock on BC – it’s simply worth knowing, before you start comparing timelines or budgets, that “migration” really means “new implementation.”
What It Typically Costs and Takes
A simple environment with clean data, few customizations, and only current General Ledger, Accounts Payable, and Accounts Receivable data might land in the $60k–$100k range with a 3–5 month timeline. But GP is the ERP of choice for handling complex finances, so very few GP users can simplify enough to hit that low end. Add extra modules, re-customized reports, existing customizations, and any third-party add-ons you need to replace, and most real-world projects land in the 6–9 month range with six-figure budgets – sometimes longer and higher for especially complex environments.
On top of the core project, budget for the ancillary costs that are easy to overlook:
- A licensing shift from GP’s perpetual model to BC’s ongoing subscription, which typically carries a higher total cost of ownership over time.
- Temporary productivity dips while your team adjusts.
- If any GP functionality or add-on you rely on has no BC equivalent, the cost of custom development to replace it from scratch.
Even when every stage goes smoothly, many businesses describe the experience as taking on an extra part-time job on top of their regular duties. Expect that to pull time and attention away from customer service, sales and marketing initiatives, and strategic planning while the project is underway.
So, Should You Migrate from Dynamics GP?
FACT: GP is not obsolete, and there’s no reason to rush.
As you no doubt noticed, this section title did not contain the word when. That’s because, honestly, reimplementing a whole new ERP at your business isn’t a matter of “when” you should do it, but rather “if” you should do it at all.
Imagine a contractor coming to your house – one of those door-to-door guys who pitch roofing services or solar panels. You feel generous, so you take a break and step outside to chat with him for a few minutes. He launches into his rehearsed pitch, and you respond.
“No, my roof is fine,” you say with a smile. “I haven’t had any problems. In fact, I just upgraded it pretty recently.”
“Well then, the clock is ticking,” he says, glaring at you. “Do you plan to tear down your house and build a new one next year, in 5 years, or later in the 2030s?” And he’s serious!
Implementing a whole new ERP system when your existing one is running smoothly is a lot like that. The choice of when to migrate should be based on your needs, and not on anything else. If GP works for you, keep it!
Remember:
- Dynamics GP will be the same as always. It will still receive updates & enhancements from Microsoft for years.
- GP won’t just stop working. After end-of-support, partners will be the people you turn to for support, updates, hosting, and even new features and innovation instead of Microsoft. Communities like the Knights of GP exist specifically to bring the partner and ISV ecosystem together, so GP customers will always have someone to rely on.
- Many businesses are considering sticking with GP. And why not? It’s familiar and reliable, supports complex finances, and can have a lower total cost of ownership than BC.
Let’s Get Back to That House Analogy…
If you’ve just upgraded the roof on your house and have no plans to move, you may want to consider a few small remodels to make your home even better. Nothing big, just something quick and easy that boosts your home’s value and your enjoyment. Redoing the blacktop on your driveway, for example, to make shoveling easier in the winter. That would save time and effort, right?
Similarly, if you plan to hang on to Dynamics GP, it’s worth looking at quick, high-value improvements to your day-to-day rather than treating “stay on GP” and “keep improving how you work” as mutually exclusive.
Saving time on a slow, manual process, such as commissions, reconciliations, reporting, or whatever your team’s particular headache happens to be, helps you get more value out of the ERP you already have, and there’s no need to wait for a brand-new system to enjoy those benefits. A good place to start is the Knights of GP Preferred ISVs and Preferred Partners; the community has already done some of the vetting for you.
John Stulak
John Stulak is a co-founder of EthoTech and has been part of the Microsoft Dynamics GP ecosystem since the early 1990s.
Since 2002, companies across every sector have relied on EthoTech for the right tool for tracking, calculating, and paying variable compensation. EthoTech is a Knights of GP Preferred ISV, and our product, Commission Plan, is built specifically for Microsoft Dynamics GP — we are committed to helping you gain value from GP well beyond its lifecycle. Commission planning for GP is all we do, and we do it better than anyone. Contact EthoTech to learn more.