
Dynamics GP now has a retirement date. Microsoft says it will stop product enhancements, tax updates and technical support for GP on 31 December 2029, with security patches only until 30 April 2031. Dynamics NAV 2018 runs out even sooner, on 11 January 2028. So the real question is not whether you need a Business Central migration. Instead, it is what waiting is quietly costing you in the meantime.
In other words, think of it as moving house. You can stay until the landlord takes back the keys. Or you can pack calmly, throw out the junk and pick the moving day yourself. So this guide walks you through that move: the price of staying put, the right route for your version, the steps, the licence costs, a realistic timeline and the packing rules Microsoft itself recommends.
Key takeaways
- GP support ends on 31 December 2029 and NAV 2018 support on 11 January 2028. Also, GP 2015 or later moves straight to Business Central online, while NAV must first pass through Business Central on-premises.
- Microsoft lists Business Central Essentials at $80 and Premium at $110 per user/month, paid yearly. Since the migration tool is built in, the real cost sits in clean-up, customizations and testing.
- Mohila’s upgrade projects usually take a few weeks to a few months, depending on complexity. Above all, one sandbox dry run before cutover keeps the plan on track.
The price of staying put on GP and NAV
Of course, staying on an old system rarely appears as a line on the P&L. Instead, the cost leaks out slowly, in places nobody budgets for.
Why staying feels safe
- First, there is no project to run this year.
- Also, users already know every screen.
- Besides, the old server still works, for now.
What it quietly costs you
- Fewer fixes as support winds down. In fact, Microsoft itself warns that GP support may no longer match past standards.
- Meanwhile, servers, SQL licences and backups stay your problem.
- Moreover, new rules, such as e-invoicing, must be bolted onto an ageing system.
- Finally, the later you start, the less room you have for a calm rehearsal.
A migration you schedule is a project. A migration forced on you by an end-of-support date is an emergency.
Business Central migration in plain English
Picture a removal company. Microsoft’s built-in cloud migration tool is the truck: it carries your setup, master data, open transactions and, for GP, your history from the on-premises SQL database into Business Central online. However, the truck does not decide what to throw away, or how to arrange the new rooms. That is the job of your team and your partner.
Fortunately, your old system keeps running while the boxes move. Microsoft states that the on-premises solution stays the live environment until you complete the migration. Meanwhile, users in the new online company get read-only access, so nothing they type gets overwritten.
| Your starting point | Route to Business Central online | Watch out for |
|---|---|---|
| Dynamics GP 2015 or later | Direct, with the built-in cloud migration tool | Choose companies and filters, such as active customers only |
| Dynamics GP before 2015 | First bring GP to 2015 or later, the tool’s minimum | An extra upgrade step |
| NAV 2015 to 2018 | BC 14 on-premises, then BC version 25 or later, then online | C/AL code must become AL extensions |
| NAV 2013 or 2013 R2 | NAV 2018, then BC 14, then version 25 or later, then online | A longer chain to test |
| On BC 14 and want a fresh start | BC 14 reimplementation tool | Moves essentials only: master data, opening balances, setup |
Glossary: five words you will hear at kick-off
- Integration runtime: a small Microsoft component installed on your network that sends data securely to the cloud.
- Replication: copying data across. Because of that, you can run it again and again until it is right.
- Data upgrade: the final conversion step. After it, you cannot replicate again from the older version.
- AL extension: the modern way to customise Business Central. NAV’s older C/AL code must be rewritten into it.
- Sandbox: a safe copy of Business Central for testing, so mistakes never touch live data.
How the Business Central migration moves your data, step by step
- Assess. First, run Microsoft’s migration assessment tool for GP. It flags likely issues and suggests options.
- Prepare and clean. Next, decide which companies to move, archive obsolete history and confirm your database compatibility level is 130 or higher.
- Set up. Then an administrator runs the Cloud Migration Setup guide in Business Central online, connects the SQL database through the integration runtime and selects companies.
- Replicate. After that, Run Migration Now copies the data across. If something looks wrong, you fix it and run it again.
- Upgrade. Once every company is replicated, you run the data upgrade. This step is one-way.
- Validate and test. For GP, validation compares source data with the migrated data. Meanwhile, key users test their daily work in a sandbox.
- Go live. Finally, you complete the migration, give users their real permissions and reconnect integrations.

The UAE and GCC angle
Business Central online is available in the UAE, Saudi Arabia, Qatar, Kuwait and Oman. In each of these markets, partners localize it on top of Microsoft’s international (W1) version. Moreover, Microsoft’s availability list shows that environments for these countries are deployed to its UAE Azure geography.
That matters for two reasons. First, local tax and reporting logic that was custom-built in NAV or GP must be checked against the online localization apps. Second, new compliance work, such as UAE e-invoicing or ZATCA in Saudi Arabia, is better built once on Business Central than patched onto a system nearing its end. For example, Mohila’s own UAE E-Invoicing extension for Business Central works with an accredited service provider. Read our UAE e-invoicing requirements guide to see how it fits your plan.
What a Business Central migration costs
| Licence or item | Typically for | Microsoft list price | Notes |
|---|---|---|---|
| Business Central Essentials | Finance, sales, purchasing and inventory users | US$80.00 per user/month, paid yearly | Copilot included |
| Business Central Premium | Users who need manufacturing or service management | US$110.00 per user/month, paid yearly | Everything in Essentials, plus more |
| Business Central Team Members | Approvers and light users | US$8.00 per user/month, paid yearly | Read, approve and limited edits |
| Cloud migration tool | The move itself | No separate price listed | Built into Business Central online |
| Extra database capacity | Very large histories | Not listed; bought via your partner | 80 GB base, plus 2 GB per Essentials and 3 GB per Premium user |
Licences are only part of the bill. In practice, these factors drive the total cost of the move:
- Users per role: above all, how many people need Essentials, Premium or just Team Members.
- Data clean-up: for example, archiving old years, closing stale records and fixing duplicates.
- Customizations: in particular, rebuilding NAV code as AL extensions, or replacing it with standard features.
- Add-ons and integrations: similarly, finding Business Central equivalents and reconnecting them.
- Training and support: finally, role-based sessions and help in the first weeks after go-live.
How long a Business Central migration really takes
In general, Mohila’s upgrade projects usually take a few weeks to a few months, depending on how complex your system is. Therefore, we fix the exact timeline only after the free consultation, once we have seen your version, data and customizations.
| Phase | What happens in a GP or NAV move | Who is involved |
|---|---|---|
| Scoping | Assessment, route choice, companies in scope | Finance lead, IT, Mohila |
| Design | Map old setup to Business Central; decide what to keep, archive or rebuild | Process owners, Mohila |
| Configuration | Tenant, licences, localization apps, extensions | Mohila, IT admin |
| Data migration | Cloud migration setup, replication, data upgrade | Mohila, IT |
| Testing | Validation, sandbox dry run, user tests | Key users, Mohila |
| Training | Role-based sessions on the new screens | All users |
| Go-live | Final replication, completion, early support | Everyone |
What speeds it up
- GP 2015 or later, so the route is direct.
- Clean data, because old history is already archived.
- Few customizations, so there is less to rebuild.
- Above all, one decision-maker who can say yes quickly.
What slows it down
- First, a long NAV chain through BC 14.
- Also, heavy C/AL code that must become extensions.
- Many companies in one batch, which Microsoft says takes longer.
- Finally, a Business Central update landing in the middle of the move.
An illustrative GP move in three scenes
Illustrative example only. The roles are typical, not a real client.
Scene 1: the packing decision. For example, a distribution company runs GP 2018. The finance manager wants every year of history; however, the IT officer worries about storage. Together with the partner consultant, they agree to move active customers and items only, and to keep a full GP copy for reference.

Scene 2: the rehearsal. Next, the team runs a full dry run in a sandbox. The validation report shows a mismatch in one customer posting setup. As a result, they fix the mapping and replicate again, before any live date is set.
Scene 3: moving day. Finally, users stop entering in GP, the last replication runs and the data upgrade completes. After the numbers match, the finance manager signs off, and the team logs into Business Central on Monday morning.
Seven packing rules for a Business Central migration
- Start with the assessment. First of all, run the migration assessment before you sign a plan.
- Decide the companies upfront. Microsoft notes that the more companies you replicate at once, the longer it takes.
- Clean before you pack. In other words, archive obsolete history and shrink oversized log tables.
- Never aim at a live environment. Migration overwrites data, so do not set it up on a production environment already in use.
- Freeze the scenery. Do not update either version, or add and remove extensions, while replication is on. Instead, reschedule the online update.
- Rehearse at least once. Microsoft recommends a full dry run in a sandbox before cutover.
- Validate before you switch. Also, give at least one user SUPER permissions in each company before you connect.
Your buyer’s question bank
Before you sign with any partner, ask these six questions and listen closely to the answers.
Six questions to ask any migration partner
- First, which route fits our exact version, and why?
- What will we archive, and how will we still reach old history?
- Which customizations become extensions, and which become standard features?
- Also, how many dry runs are in the plan?
- Who validates the numbers, and against what?
- Finally, what support do we get in the first weeks after go-live?
How Mohila can help
Mohila runs GP and NAV upgrades to Business Central with a free evaluation of your upgrade path, clear scope-based pricing and up to a three-month warranty on project delivery. Whether you are on Dynamics GP or Dynamics NAV, you can also see similar moves in our anonymous case studies, including GP and NAV 2013 and 2016 migrations to Business Central online.
Talk to an Expert
Book a free 1-hour consultation, and we will map your GP or NAV version to the shortest safe route, before an end-of-support date picks moving day for you.
Frequently asked questions
In short, Microsoft lists Business Central Essentials at US$80 and Premium at US$110 per user/month, paid yearly, and the cloud migration tool has no separate price. However, the full cost depends on data clean-up, customizations, integrations and training. Mohila gives a scope-based quote after the free consultation.
Mohila’s upgrade projects usually take a few weeks to a few months, depending on complexity. For example, a direct GP 2015+ route with clean data is faster, while a NAV route through BC 14 with heavy customizations takes longer.
No. Instead, Microsoft requires NAV to be upgraded to Business Central on-premises first, and C/AL customizations must become AL extensions. Alternatively, from BC 14 you can use the reimplementation tool to move only essential data.
Yes, the GP migration tool can bring historical data, and you choose what to include per company. You can also keep a copy of the GP database in Azure Data Lake for future reference.
Yes. The on-premises system stays live until you complete the migration. Meanwhile, users in the new online environment get read-only access, so replicated data is not overwritten.
Sources
- Microsoft Learn: Dynamics GP migration to Business Central online, end-to-end overview
- Microsoft Learn: Prepare and plan for cloud migration from Dynamics GP
- Microsoft Learn: Migrate Dynamics NAV to Business Central online
- Microsoft Learn: Lifecycle policies for Dynamics GP
- Microsoft Learn: Products ending support in 2028 (Dynamics NAV 2018)
- Microsoft Learn: Managing capacity in Business Central
- Microsoft Learn: Business Central country and regional availability
- Microsoft: Dynamics 365 Business Central pricing




