Migrating to Business Central in 2026: method, steps and pitfalls to avoid

Dynamics NAV reaching end of life, mandatory e-invoicing, the rise of the cloud and AI: in 2026, many French SMBs and mid-sized companies are asking the same question. Should they migrate to Microsoft Dynamics 365 Business Central, and how can they do it without putting their accounting at risk? The interest is real: on Google Trends, searches related to Business Central have been clearly trending upward in France over the past twelve months.
Whether you are starting from Dynamics NAV (Navision), Sage, EBP or a set of Excel files, this guide covers the reasons to migrate now, the migration paths documented by Microsoft, the steps of a project, the costs to plan for and the most common pitfalls.
Why migrate now
1. The end of Dynamics NAV support
According to the official lifecycle published by Microsoft, extended support for Dynamics NAV 2017 ends in January 2027 and for Dynamics NAV 2018 in January 2028. Mainstream support for both versions has already ended. Beyond these dates, there are no more fixes or security updates: a risk that is hard to accept for a system that runs accounting, inventory and invoicing.
2. The French e-invoicing reform
Since September 1, 2026, all companies in France must be able to receive electronic invoices, and large and mid-sized companies must issue them in this format. SMBs and micro-businesses will have to issue them from September 1, 2027. Invoices go through state-approved platforms. An old, heavily customized or poorly maintained ERP makes this compliance harder.
The French localization of Business Central already documents e-invoicing in France with UBL 2.1 and Factur-X as well as e-reporting, alongside the expected accounting features: export of entries for tax audits, matching, declaration of exchanges of goods and declaration of services.
3. The cloud and the Microsoft ecosystem
Business Central online integrates natively with Outlook, Teams, Excel, Power BI and the Power Platform. For companies running a Dynamics 365 CRM, it connects sales and operations within one ecosystem, with no double entry.
The migration paths documented by Microsoft
Your starting point determines the method. Microsoft documents several scenarios.
| Current system | Documented path | Point to watch |
|---|---|---|
| Dynamics NAV 2015 to 2018 | Upgrade to Business Central on-premises, then the cloud migration tool to Business Central online | C/AL customizations must be converted into AL extensions |
| Dynamics NAV 2009 and 2013 | Intermediate upgrades before reaching Business Central on-premises, then cloud migration | A longer path: reimplementation is often worth comparing |
| Business Central on-premises | Direct migration to the cloud from version 25; prior upgrade for earlier versions | SQL Server 2016 or later database |
| Sage, EBP, another ERP or Excel | Data import through configuration packages and templates, or custom migration from a SQL source | A reimplementation project: the opportunity to review processes |
Two rules from Microsoft’s documentation are worth remembering. First, data in custom tables cannot be migrated until the C/AL customizations have been converted into AL extensions. Second, there is an alternative for older versions: the reimplementation tool from Business Central 14, which brings over master data, opening balances and setup, but not transaction history or customizations. Microsoft also recommends running at least one trial migration in a test environment (sandbox) before go-live.
The steps of a migration project
- 1. Current-state review. Inventory of processes, customizations, interfaces and data quality. This is the time to decide what should be carried over, simplified or dropped.
- 2. Scoping and fit-gap analysis. Compare your requirements with standard Business Central and its French localization before planning any development.
- 3. Data cleansing and preparation. Chart of accounts, customers and vendors, items, opening balances, unmatched entries: polluted history is expensive to migrate.
- 4. Configuration and extensions. Setting up the standard, converting or rewriting the essential customizations as AL extensions.
- 5. Trial migration and acceptance testing. At least one full run in a test environment, validated by key users.
- 6. Training and go-live. Role-based training, a go-live date suited to the accounting calendar, then closer support during the first weeks.
The cost items to plan for
Licenses. Microsoft publishes the following prices for France, per user per month, with an annual commitment:
| Business Central license | Public price excl. VAT | Who it is for |
|---|---|---|
| Essentials | €69.30 | Full management: finance, sales and operations |
| Premium | €95.30 | Essentials, plus manufacturing and service management |
| Team Members | €6.90 | Limited access: reading data and approving workflows |
The project. On top of licenses come scoping, data migration, configuration, conversion of customizations, training and post-go-live support. These amounts depend directly on the starting point: migrating from a heavily customized NAV does not have the same scope as a reimplementation from Excel. Be wary of budgets quoted without a prior current-state review.
Internal time. This is the item most often forgotten. Key users (accounting, sales administration, logistics) must be available for scoping, acceptance testing and training.
The most common pitfalls
- Reproducing the old system identically. Systematically converting every NAV or Sage customization amounts to migrating technical debt. Standard Business Central often covers needs that used to require development.
- Migrating all history without sorting. The larger and more inconsistent the data, the longer and riskier the migration. Decide upfront what must remain accessible and what can be archived.
- Underestimating e-invoicing. The choice of approved platform and the setup of flows must be part of the project, not handled after go-live.
- Skipping the trial migration. Going live without a full run in a test environment exposes you to discrepancies discovered in the middle of a closing.
- Forgetting the CRM. If your sales reps use another tool, the ERP migration is the right time to think about CRM and ERP integration.
Choosing the right Business Central partner
A few concrete criteria: proven experience migrating from your current system, command of the French localization and e-invoicing, the ability to cover the ERP, Dynamics 365 CRM and the Power Platform, and a method that starts with a current-state review rather than a quote. We detail these criteria in our article how to choose your Dynamics 365 partner, and our complete guide to Business Central for SMBs presents the solution in detail.
At Activops, every Business Central project can start with a Health Check: processes, data, tools, to know where you stand before you invest, with a prioritized 90-day plan.
Do your teams work on site? Our Dynamics 365 Field Service guide also covers integration with Business Central.
Frequently asked questions
When does Dynamics NAV support end?
According to the lifecycle published by Microsoft, extended support for Dynamics NAV 2017 ends in January 2027 and for Dynamics NAV 2018 in January 2028. Mainstream support for these versions has already ended.
Can you migrate directly from NAV to Business Central online?
No. Microsoft states that you must first move to Business Central on-premises, then use the cloud migration tool. C/AL customizations must be converted into AL extensions for their data to be migrated.
How do you migrate from Sage, EBP or Excel?
It is a reimplementation: data (chart of accounts, customers and vendors, items, balances) is imported through configuration packages and templates, after cleansing. It is also an opportunity to review processes.
How much do Business Central licenses cost?
For France, Microsoft publishes €69.30 excl. VAT per user per month for Essentials, €95.30 excl. VAT for Premium and €6.90 excl. VAT for Team Members, with an annual commitment. The project cost comes on top and depends on the starting point.
Does Business Central handle French e-invoicing?
The French localization documented by Microsoft includes e-invoicing with UBL 2.1 and Factur-X as well as e-reporting. Connection to an approved platform must be planned in the project.
Do you need to migrate all accounting history?
Not necessarily. Migrating opening balances and master data, and archiving history in a readable format, is often safer and faster. The decision is made during the current-state review.
Sources
- Microsoft Learn, Dynamics NAV 2017 – Lifecycle, accessed November 7, 2026 — learn.microsoft.com
- Microsoft Learn, Dynamics NAV 2018 – Lifecycle, accessed November 7, 2026 — learn.microsoft.com
- Microsoft Learn, Migrate Dynamics NAV to Business Central online, accessed November 7, 2026 — learn.microsoft.com
- Microsoft Learn, Migrate on-premises data to Business Central online, accessed November 7, 2026 — learn.microsoft.com
- Microsoft Learn, Local functionality, France (Business Central), accessed November 7, 2026 — learn.microsoft.com
- Microsoft, Dynamics 365 Business Central pricing (France), accessed November 7, 2026 — microsoft.com
- Previssima, Facturation électronique : ce qui change pour les entreprises dès le 1er septembre 2026 (in French), August 31, 2026 — previssima.fr
- Google, Google Trends, queries related to “business central”, France, past 12 months, accessed November 7, 2026 — trends.google.fr


