Implementation

Dynamics GP to Business Central Migration

Move off Dynamics GP before support ends, retire the servers it runs on, and arrive on Business Central in the cloud with the history you need and none of the workarounds you don't.

Talk to us about your project
Business CentralDynamics 365Power Platform

Kumo's Dynamics GP to Business Central migration moves your accounting off an on-premises GP server and into Business Central in the cloud. Microsoft ends Dynamics GP support on December 31, 2029, so the question for most GP customers is when to move, not whether. We plan the move so it happens on your schedule, brings the data and processes that still matter, and lets you switch off the servers GP has kept you paying for.

6

CRM and ERP moves to the cloud, including GP to Business Central

2M+

records migrated in a single cutover

30+

Dynamics 365 implementations delivered

Who it's for

A good fit if…

  • You run Dynamics GP on-premises and want off it before support ends.
  • Your GP server, SQL Server, or connectors are getting harder to keep running.
  • You keep servers, SQL Server licenses, backups, and remote access running mostly for GP.
  • GP is connected to a CRM or other system that also needs to move.
What you get

You walk away with

  • A migration plan that says what moves, what stays archived, and in what order.
  • Business Central set up for your companies, chart of accounts, and processes.
  • Your vendors, customers, items, and balances moved and reconciled.
  • Training for your finance team before the cutover.
  • A plan to retire the GP server, its SQL Server database, and the hardware and licenses behind them.
Value

Why it matters

Move on your schedule, not Microsoft's

Starting before the deadline means a planned cutover at a quiet point in your year, not a rush in 2029.

Move what is alive

Not every GP customization or year of history needs to come along. Leaving the dead weight behind is part of the value.

Switch off the server room

Business Central runs in Microsoft's cloud. Patching, backups, upgrades, and remote access stop being your IT team's job.

Approach

How it works

1

Review your GP setup

Companies, modules, customizations, add-ons, and the systems GP connects to.

2

Plan the move

What moves, what is archived, what Business Central does as standard, and the cutover date.

3

Migrate and reconcile

Master data and balances moved, checked against GP, and signed off by finance.

4

Cut over and retire GP

Training, go-live at a quiet point in your year, then GP archived and its servers shut down.

Inside the build

What it actually looks like

Screenshots from production work Kumo built and runs. Client branding and customer data are redacted.

Business Central in the cloud: sales, receivables, and payables on one home page, with Shopify orders flowing in. No server to keep running. Client details are blurred.
The deeper read

Why it matters

Dynamics GP still works, and it will keep receiving security updates into 2031. But tax updates and technical support end with 2029, Microsoft’s new development goes into Business Central, and every year adds more history and more workarounds to migrate.

The deadline is only half of it. GP keeps a server, a SQL Server database, backups, a VPN, and somebody’s weekends tied up. Moving to Business Central turns that into a subscription Microsoft runs: updates arrive on their own, finance works from anywhere, and the data sits on the same platform as Microsoft 365, Power BI, and Copilot instead of behind a firewall.

The organizations that move early pick their cutover date and retire their hardware on their own schedule. The ones that wait share partners and timelines with everyone else.

Not sure where to start? Begin with a Dynamics 365 roadmap assessment and get a scoped plan first.

FAQ

Questions we hear a lot

When does Dynamics GP support end?

Microsoft ends Dynamics GP support on December 31, 2029. That covers product enhancements, tax updates, and technical support. Security updates continue, if needed, until April 30, 2031.

Can we move GP and our CRM at the same time?

Yes, and if both are going we recommend it. Moving them together avoids building a temporary sync between a cloud system and an on-premises one, which is work you throw away later.

Do we have to bring all our GP history?

No. Most organizations bring master data, open transactions, and recent history, and keep older detail in an archive they can still report on. We decide that with your finance team.

What happens to our GP servers after the move?

Once finance has signed off and the history you need is archived, the GP server and its SQL Server database can be shut down. That ends the hardware refreshes, Windows and SQL Server licensing, backups, and patching that GP needed.

Ready to start?

Off on-premises Dynamics GP and its servers, onto Business Central in the cloud, before Microsoft ends GP support in 2029.

Talk to us about your project
Also under this capability

More from Dynamics 365 Implementation

Assessment · 2 to 6 weeksWays to startDynamics 365 Roadmap AssessmentA fit analysis for one or more Dynamics 365 modules, what your licenses and Copilot add, and a roadmap for the project.Scoped on a callSee the engagement →ImplementationDynamics 365 Sales & Customer EngagementDynamics 365 Sales (CRM) built around your sales process, with Copilot and agents that make every seller more effective.See the offering →ImplementationBusiness Central ImplementationFinance and operations on Business Central for teams that have outgrown QuickBooks, GP, NAV, or spreadsheets.See the offering →
← Back to Dynamics 365 Implementation