I can’t tell you how many times I’ve had this conversation with a CFO: They tell me GP still works, their team is used to it, and a Dynamics GP to Dynamics 365 Business Central migration sounds like more hassle than it’s worth.
I get it. Change is disruptive. But then I ask: What happens when “GP still works” isn’t good enough anymore?
That’s exactly what happened to Mark. His business was growing, but GP wasn’t keeping up. Manual workarounds became the norm. Reports took hours instead of minutes. IT kept patching things together, but it was getting harder to ignore the cracks. And then, one day, when Mark needed GP most, it failed him.
A critical financial report wouldn’t generate before an investor meeting, leaving him scrambling with outdated numbers. At the same time, his team struggled to process payroll due to a GP system freeze, and an audit request turned into a compliance nightmare when missing data forced days of manual corrections.
It was a perfect storm of critical failures, last-minute scrambling, and sleepless nights that made one thing painfully clear: Sticking with the familiar was the real risk. GP wasn’t cutting it anymore.
Mark wasn’t alone in this realization. Companies of all sizes are moving to the cloud to avoid these exact pitfalls – not just to solve immediate challenges, but to future-proof their operations against the next inevitable disruption.
Mark didn’t rush into migration overnight, though. He took the time to plan it properly, mapping out a strategy, choosing the right partner, and making sure his team was prepared. And because of that, the transition was smoother than he ever expected.
So, if you’re still wondering when – or how – to start planning your Dynamics GP migration, let’s break it down step by step.
The Breaking Point: Why a Dynamics GP to Dynamics 365 Migration Became Inevitable
Mark wasn’t actively looking to migrate Dynamics GP to Dynamics 365. Sure, GP had quirks, but nothing he thought was a deal-breaker… until everything started unraveling at once:
- Critical financial reports, payroll, and compliance issues all hit at the same time, proving that workarounds weren’t sustainable.
- A cost analysis showed that staying on GP was actually more expensive in the long run.
- IT was spending more time maintaining GP than supporting business growth.
But the real tipping point was the failed investor meeting that put future expansion at risk.
Mark wasn’t the only one facing these challenges. Businesses across industries are realizing that legacy systems aren’t built for the demands of today’s digital world. Microsoft’s insights on embracing cloud migration with Dynamics 365 highlight how companies are moving to the cloud – not just to fix immediate issues, but to ensure long-term scalability, efficiency, and resilience.
Mark didn’t just want a quick fix – he needed a structured plan to ensure a smooth, low-risk migration.
The Planning Process: Preparing for Migration
A successful migration doesn’t start with the flip of a switch – it starts with a plan. Mark knew that if he wanted a smooth Dynamics GP to Business Central migration, he needed to tackle it strategically. Here are the five steps he put in motion to get his company there:
1. Getting Leadership Buy-In
Mark saw the writing on the wall, but the leadership team? Not so much. With an understanding that change isn’t just a technical decision but a business one as well, before moving forward, he:
- Framed the conversation around long-term value: cost savings, efficiency, and risk reduction.
- Got executive alignment early, so decision-makers were on board.
- Addressed concerns head-on, including cost, training time, and employee pushback.
2. Evaluating the Current System and Cleaning Up Data
Migrating messy, outdated data into a new system is like bringing expired food into a brand-new fridge… if it was bad before, it’s not going to get better in a new space.
Before the transition, Mark’s team:
- Audited their GP setup to identify what data, processes, and reports were still relevant.
- Removed duplicates, outdated records, and unnecessary customizations to streamline the migration.
- Standardized data formats to ensure smooth mapping into Business Central.
These steps prevented them from importing old problems into their new system; a mistake too many companies make.
3. Selecting a Migration Partner: Expert Guidance for a Seamless Transition
This wasn’t a DIY project, and Mark knew it. He chose a migration partner that helped them:
- Identify the best migration approach (full move vs. phased transition).
- Avoid common pitfalls, like mis-mapped data fields or broken integrations.
- Train employees ahead of time, so they weren’t caught off guard.
4. Setting Realistic Timelines & Expectations
ERP migrations don’t happen overnight (unless downtime, confusion, and panic are your thing). Mark’s team:
- Mapped out a timeline that aligned with business needs and internal bandwidth.
- Trained employees before full deployment, ensuring they were comfortable from day one.
- Had a contingency plan – because even the best migrations can hit a few bumps.
5. Rolling Out in Phases: Testing, Training, and Implementation
Rather than a sudden system switch, Mark and his team:
- Ran a pilot program with a small group before expanding company-wide.
- Provided hands-on training sessions so employees could adapt at their own pace.
- Launched in waves, starting with finance before bringing in other departments.
The result was a smooth, low-risk transition instead of a last-minute scramble.
Overcoming Resistance: The Emotional Side of Migration
Technical challenges aside, one of the biggest hurdles was employee pushback. Change isn’t just a systems upgrade – it’s a mindset shift.
- Fear of the unknown – Employees were nervous about learning a new system.
- Concerns about disruption – Would Business Central slow them down?
- Skepticism – Could it really be better than GP?
Mark handled it like a pro by:
- Highlighting familiar features – Business Central retains many of GP’s best functions, so employees weren’t starting from scratch.
- Hands-on training & early access – Letting employees explore Business Central before the full rollout made a huge difference.
- Clear communication – Instead of just announcing the change, Mark explained why they were migrating and how it would make their lives easier.
By the time they officially switched over, the fear of change had shifted to excitement about better workflows and automation.
What Changed After the Move?
Mark’s biggest realization? They should have done this sooner.
Instead of fighting with outdated technology, his team was finally able to focus on business growth without constant system workarounds. The impact was immediate:
- No more IT headaches – Microsoft handles updates and maintenance.
- Better reporting & automation – Real-time data at their fingertips means no more waiting hours for reports.
- Seamless integration – Outlook, Excel, and Teams all working with their ERP.
Mark’s experience underscores a broader truth: clinging to outdated ERP systems can incur significant hidden costs and operational inefficiencies. As highlighted in our article, Why ERP Migration is Crucial: The True Cost of Outdated Systems, delaying migration doesn’t just slow down operations – it can hinder growth and competitiveness.
With Business Central in place, the company could finally focus on the future instead of patching up the past.
This story isn’t unique; I’ve seen countless businesses hesitate, only to realize the risks of staying with GP.
The truth is that moving to Business Central doesn’t have to be disruptive. With the right strategy, the right partner, and a phased approach, migration can be smoother than you think.
Thinking about migrating from Dynamics GP? Talk to our experts at Dorado Solutions. We’ll help you build a roadmap for a seamless transition.
Join our webinar to learn how companies like Mark’s made the switch successfully!
bout the Author
Wally Dodds, Principal and Owner of Dorado Solutions, Inc., brings over 25 years of experience in accounting and ERP consulting. Starting as a Senior Accountant for a Fortune 500 distribution company, Wally transitioned into consulting, playing a pivotal role in growing a Dynamics GP practice into one of the largest global partners.
With expertise spanning industries like manufacturing, distribution, healthcare, and nonprofits, Wally has held diverse roles, including Project Manager, Technical Consultant, and Dynamics GP Product Lead. Known for delivering innovative, compliant solutions, he combines deep technical knowledge with a talent for addressing client challenges, ensuring impactful results.
You can find Wally on LinkedIn.
