Moving to Business Central from Dynamics GP: What Marketing Doesn’t Tell You

For your current system, Dynamics GP to D365 Business Central, here are some things to watch out for when moving from Dynamics GP to Business Central.

1. Business Central is not Dynamics GP in the Cloud—Here’s what that really means

What marketing says:
“It’s a modern cloud upgrade—familiar, but better.”

What I’ve actually seen:

• Clients expect the same mental models: batches, account segments, modals, GP navigation.
• The shock isn’t technical—it’s conceptual.

Most frustration I see in early Business Central projects isn’t because Business Central can’t do something—it’s because users try to use it the way GP trained them to think.

Some examples are dimensional accounting vs. segments, posting groups vs. classes, and more structure.

2. Data migration issues when moving from Dynamics GP to Business Central

What marketing says:
“We can migrate your data quickly so you can get live fast.”

What I’ve actually seen:

• GP environments where GL ≠ subledgers
• Years of workarounds, inactive vendors, broken history
• Migration tools don’t fix accounting problems—they expose them

If GP has been holding together through muscle memory and workarounds, Business Central will surface every one of those issues—immediately

Data migration becomes a moment of truth, exposing the inconsistent data. The difference is moving data and trusting data. D365 Business Central is less forgiving of inconsistent setup. (e.g., using the same GL account for different posting areas)

3. Why speed isn’t the most important KPI in a Business Central migration

What marketing says:
“Go live in weeks, not months.”

What I’ve actually seen:

• Fast projects succeed only with discipline and scope control
• Slow projects fail when no decisions get made
• The real variable isn’t time—it’s readiness

Every ‘fast’ Business Central project I’ve seen succeed had one thing in common: the client knew exactly what they were not carrying forward from GP. There are real risks in copying GP instead of redesigning. in rushed projects, they often end up costing more in the post-go-live support.

Fast projects succeed only with discipline and scope control. For a deeper look at how structured approaches make this possible, see my guide to Dynamics GP to Business Central migration strategy.

4. User adoption challenges in Business Central after moving from Dynamics GP

What marketing says:
“Users will love the modern interface.”

What I’ve actually seen:

• Users struggle most with invisible changes:
  • No batches
  • Different posting flow
• Month‑end closes, and exceptions are where confidence drops

UAT is crucial to any implementation. Training once isn’t enough. The critical first 90 days after go-live will determine the implementation’s outcome.

Most post‑go‑live stress isn’t about missing features—it’s about users not yet trusting the results they’re seeing.

5. Business Central rewards discipline—GP allowed flexibility

What marketing says:
“Business Central streamlines and automates everything.”

What I’ve actually seen:

• BC enforces structure (which is good—but uncomfortable)
• Defaults, dimensions, and setups matter more
• Clean design produces cleaner reporting—but only if set up correctly

Business Central doesn’t tolerate ‘we’ve always done it this way’—and that’s either its greatest strength or its biggest shock

BC is a quieter system when done correctly. Sloppy setups show up faster than in GP. BC also exposes governance gaps rather than hiding them.

Ready to move off Dynamics GP? Talk to ArcherPoint by Cherry Bekaert and get a clear path to Business Central.

Trending Posts