Moving from Dynamics GP to Business Central: a migration that keeps your history

Why GP companies are moving now

Microsoft has published an end date for Dynamics GP support. It has also stopped selling GP to new customers. GP still runs, and nobody is forced off tomorrow. However, new development has moved to Business Central. The pool of people who know GP well gets smaller each season.

There are positive reasons as well. Business Central runs in a browser with no server to maintain. It gets updates in two release waves a year. It also links to Microsoft 365 and Power BI. For many GP users, the biggest daily change is working from anywhere without a remote desktop session.

What the Dynamics GP to Business Central migration tool moves

The cloud migration tool in Business Central has a dedicated path for Dynamics GP. It brings across the chart of accounts, customers, vendors, items and bank accounts. It also brings open receivables and payables, along with inventory on hand. A setup page lets you choose which modules and companies come along.

We handle GP account segments with care. The main segment becomes the G/L account number. The other segments become dimensions. That is how Business Central expects you to model departments and divisions. You can bring older transactions over as a read-only historical snapshot. So staff can look up past invoices without keeping the GP server alive.

What a Dynamics GP to Business Central migration rebuilds by hand

Code does not travel. Dexterity customizations, modified forms and most GP add-ons have no automatic route. So we assess each one. Does a standard Business Central feature cover it? Can an AppSource app replace it? Or must it be rewritten as an AL extension? Many turn out to be unnecessary.

Reporting changes too. We rebuild Management Reporter layouts as Financial Reports. Filtered list views, analysis mode and Excel replace SmartList habits. Payroll deserves early attention, because Business Central has no built-in US payroll. GP Payroll users move to a payroll provider or a payroll app. Journal entries then flow into the ledger.

How we run a Dynamics GP to Business Central migration

We begin with an assessment of your GP environment. We look at your GP version, companies, modules and data size. Custom code and links to other tools get a check too. The result is a plain list. It shows what moves, what changes and what retires. So everyone has the same picture before work begins.

Then we rehearse. We load a sandbox with the migration tool and reconcile balances against GP. Your team works through real tasks, such as entering an invoice, running a payment batch and closing a period. We fix issues and repeat the rehearsal until the numbers tie and people are comfortable. Cutover day follows the same script at a period end.

Dynamics GP to Business Central migration pitfalls and what you receive

The costliest mistake is recreating GP inside Business Central. The two products think differently about dimensions, posting and batches. Forcing old habits on the new system works badly. So we explain the Business Central way first. We customize only where a real need remains.

Dirty data is the other. Clean out dead vendors, repeat customers and unused accounts in GP first. It is easier there. At the end, you receive a reconciled live company and the reconciliation workpapers. You also get role-based training recordings and a list of every extension and app installed. We support you during US business hours through your first month-end close.

Dynamics GP to Business Central migration questions

Do we have to leave Dynamics GP?

Not immediately. GP continues to work. Microsoft has published the dates until which it will give support and security updates. Planning ahead lets you choose a calm period for the move. You then avoid reacting to a deadline or to a server that fails.

Is it a migration or a new implementation?

Some of each. The tool moves data, which saves real effort. However, Business Central is a different product. So we design setup choices, processes and reports afresh. Treating a Dynamics GP to Business Central migration as a data copy is a common reason projects disappoint.

How much GP history can we bring?

Open transactions and balances come across as live data. The tool can also load old transactions as read-only history. Users can search and read them inside Business Central. We agree the cut-off with you. That choice trades convenience against a longer migration run.

What happens to our GP add-ons?

We assess each one on its own. Some vendors sell a Business Central version. Standard features meet some needs, and a different app meets others. We list every add-on during assessment with a recommended replacement. So there are no surprises late in the project.

Will our chart of accounts change?

Usually it becomes shorter. Segments that stood for departments or locations turn into dimensions. That leaves a chart of natural accounts. The migration tool applies this mapping. We check the result with your controller. So financial statements still read the way the business expects.

Related migration services

Leaving GP involves data work, cloud setup and often a payroll decision. These pages cover the neighboring topics, including a side-by-side look at the two products. Read them before you plan a Dynamics GP to Business Central migration. Then send us your GP version and module list, and we will outline the assessment. For the product detail, see Migrate Dynamics GP data to Business Central online on Microsoft Learn.