ERP Migration Planning Starts with a Game Plan

If you’ve ever lived through an ERP migration planning process, you know there’s a moment when the room gets quiet....

It usually happens halfway through the project, when someone realizes that what we’re calling planning has mostly consisted of a timeline… and a lot of crossed fingers.

I’ve had a front-row seat to both sides of this equation. I’ve led implementations as a consultant and owned the outcome as an operations leader. And I can tell you this: the projects that feel chaotic at the end almost always skipped discipline at the beginning.

A well-planned ERP migration doesn’t mean easy. It means clear phases, defined owners, realistic milestones, and users who are productive within weeks... not months.

Welcome to my first post in a new three-part series on ERP migration planning and execution for organizations moving to Dynamics 365 Business Central. In this article, I’ll outline the ERP migration roadmap, key phases, and readiness assessment steps.

Let’s dive in and answer some of the questions I hear most often from leadership teams preparing to make this move.

What does a “smooth” ERP migration actually look like in real life?

First things first: I want to define what “smooth” really means.

A smooth migration is not one where nothing goes wrong. That creature hasn’t been spotted in the wild.

A smooth migration is one where:

• The ERP migration roadmap is clearly defined and understood

• Each phase has accountable owners

• The ERP migration timeline is realistic, not aspirational

• Business disruption during cutover is minimal

• Users are productive within weeks, not months

For executives, that clarity reduces risk. For project managers, it reduces guesswork. And for end users, it builds confidence long before go-live.

In my experience, successful Dynamics GP to Business Central migration planning projects share one essential trait: leadership understands that this is not just a technical upgrade.

It’s a structured transformation effort.

According to Microsoft’s Cloud Adoption Framework, structured assessment and planning are foundational to any successful cloud migration, not optional add-ons.

That same principle applies directly to Business Central migration strategy: readiness must be deliberate.

When organizations treat ERP migration planning as a phase (as opposed to a meeting), everything downstream stabilizes.

What are the main phases of an ERP migration, and what happens in each one?

One of the most common ERP migration risks I see is when teams underestimate the number of distinct ERP migration phases involved.

When I coached youth soccer, I learned quickly that you can’t just hand kids a ball and hope they'll know what to do with it.

You need positions.

You need a plan.

You need someone calling plays.

It’s the same with ERP migrations. Without defined phases and ownership, everyone runs toward the ball at once — and no one’s actually guarding the goal that matters.

 If you’re researching ERP migration phases or trying to map out your ERP implementation roadmap, you’re really asking what happens between signing the contract and go-live.

Here’s the structure we typically follow for a Business Central migration from Dynamics GP:

1. Planning and ERP readiness assessment

This is where ERP implementation readiness is measured... not assumed. We evaluate:

• Process ownership and documentation

• Data quality and reporting dependencies

• Integration touchpoints

• Leadership alignment on scope

This phase forms the backbone of effective ERP migration planning.

2. Design, configuration, and data preparation

Here, we translate business requirements into Business Central configuration.

Decisions made here impact reporting, workflows, and user experience.

3. Testing, training, and go-live readiness

In this phase, confidence is built. Multiple testing cycles validate configuration, integrations, and data accuracy. Training aligns with real-world tasks.

4. Stabilization and optimization

One of the biggest mistakes I see is celebrating go-live like the project is over. In reality, that’s when the real refinement begins.

Too often, these ERP migration phases get compressed or blurred together, and the project starts to feel reactive instead of controlled.

How do you know if your organization is actually ready to migrate ERP systems?

This is where even confident leadership teams start shifting in their chairs.

Readiness is often assumed because the business case is clear. But business urgency is not the same as organizational readiness.

An effective ERP readiness assessment for a Business Central migration evaluates:

• Whether processes are clearly defined and standardized

• Whether reporting requirements are documented

• Whether master data is structured and governed

• Whether internal stakeholders agree on scope and expectations

A Forbes Technology Council article on organizational maturity called out that companies often overestimate their preparedness for transformation initiatives.

True readiness requires an honest evaluation of process maturity and leadership alignment.

That’s why we treat the readiness assessment as a named step in the ERP migration checklist, not an informal discussion.

Because once configuration begins, correcting gaps becomes exponentially more expensive.

What is an ERP readiness assessment, and why does it matter?

An ERP readiness assessment is a structured, pre-implementation evaluation conducted before Dynamics 365 Business Central configuration and data migration begin.

It identifies:

Gaps in processes

Data inconsistencies

Reporting blind spots

Role confusion

Unrealistic assumptions about scope or timeline

In short, it protects your ERP migration timeline.

Without it, teams often discover missing requirements during testing... or worse, after go-live.

With it, your ERP migration roadmap becomes grounded in reality.

For organizations planning a Dynamics GP to Business Central migration planning initiative, this step is particularly important.

Legacy workarounds, custom reports, and undocumented processes tend to surface only when someone starts asking detailed questions.

For example, a “temporary” Excel report built five years ago often turns out to drive executive decision-making — but no one documented how it was created.

Better to surface those early.

What goes wrong when companies underestimate ERP migration planning?

When ERP migration planning is compressed, skipped, or rushed, the consequences are predictable.

Common ERP migration risks include:

·         Missed dependencies between departments

·         Incomplete reporting configuration

·         Poor data alignment

·         Unrealistic cutover expectations

·         Low user confidence at go-live

I’ve sat in rooms where leadership assumed the technical build was the hard part.

But in reality, the hard part is alignment: people, processes, and expectations.

When planning is disciplined, the migration feels controlled.

When it isn’t, it feels stressful.

And stress at go-live erodes trust in the new system before it has a chance to prove its value.

Building a Strong Foundation for the Rest of the Journey

Effective ERP migration best practices treat planning, data, and people as equal pillars of success.

Here we focused on the big-picture ERP migration roadmap, readiness, and structured planning. Planning sets the foundation.

But even the best roadmap can collapse under poor data or weak adoption.

In my next two posts, I’ll go deeper into:

• Data preparation, cleansing, and testing, where many migrations either gain confidence or lose it.

• User adoption and go-live readiness — because technical success doesn’t matter if your team doesn’t embrace the system.

If you’re evaluating your own Business Central migration strategy, now is the time to slow down just enough to plan properly.

Good teams don’t show up on game day without a playbook. And good organizations shouldn’t show up to go-live without one either.

Because the goal isn’t just to go live. It’s to go-live and keep moving.

If you'd like to discuss your organization’s readiness or walk through a structured ERP migration checklist, join our Office Hours on Tuesdays at 11:30 ET, or reach out directly.

Together, we can build a migration plan that works for you.

About the Author

Chris Boling is a founding partner of Sandlapper Dynamics, where he helps businesses streamline operations, enhance productivity, and achieve strategic growth through Microsoft Dynamics 365. With over two decades of experience in the Dynamics community, Chris combines deep technical expertise with a customer-first approach to guide organizations through digital transformation.

His unique perspective, shaped by years as both a consultant and an end-user, enables Chris to deliver practical insights that bridge the gap between technology and business outcomes.

Chris brings authenticity, empathy, and a commitment to sustainable growth to every engagement.

You can reach Chris on LinkedIn.