Dynamics NAV GP Migration Business Central Cost 2026

The cost of a Dynamics NAV or GP to Business Central migration is driven by five factors: user licensing, implementation labor, data migration, customization rework, and integrations. Of these, data migration and customization rework are the largest and least predictable, often accounting for 40 to 55 percent of the total budget while licensing is usually the smallest recurring line.

Understanding the weight of each component prevents the most common budgeting error, which is quoting only licensing and treating everything else as an afterthought. Here is how the money typically distributes:

• Licensing: recurring subscription cost per user, the smallest one-time impact but a permanent operating expense.
• Implementation and configuration: partner labor to set up chart of accounts, dimensions, posting groups, and workflows.
• Data migration: extraction, cleansing, mapping, and loading of master and historical data.
• Customization and extension development: rebuilding legacy NAV or GP modifications as Business Central extensions.
• Integrations and training: connecting third-party systems and onboarding users.

Nearly 70 percent of ERP implementations exceed their original budget (source: Panorama Consulting Group, 2026), and the overrun almost always traces back to underestimated data and customization work. PortMux research shows that organizations who inventory their customizations and define a data scope before quoting reduce overruns dramatically.

The teams that come in on budget are the ones who treat data cleansing as a project phase, not a footnote. Dirty legacy data is where migration budgets quietly double.

Ryan Loiacono, Founder, Untapped Connections

Business Central licensing is a per-user monthly subscription with two main tiers. As of 2026, Business Central Essentials costs about 70 dollars per user per month and Business Central Premium costs about 100 dollars per user per month, with a lower-cost Team Members license around 8 dollars per user per month for light users who only read data and approve tasks.

Essentials covers financial management, sales, purchasing, inventory, and project management, which is enough for most companies migrating from GP or NAV. Premium adds service management and manufacturing, so choose it only if you actually run those operations. Mixing Essentials and Premium in the same tenant is not allowed, so all full users must sit on one tier.

Licensing math example

A 25-user company on Essentials pays roughly 25 users times 70 dollars, or about 1,750 dollars per month (21,000 dollars per year). Add a handful of Team Members licenses for approvers and the annual licensing figure stays modest compared to the one-time implementation spend.

Cloud ERP now represents the majority of new ERP deployments worldwide (source: Gartner research, 2026), and the subscription model is a key reason. Unlike legacy NAV and GP, where you paid large upfront license fees plus annual enhancement plans, Business Central Online rolls updates and infrastructure into the subscription. This eliminates the version upgrade projects that used to hit NAV and GP shops every few years.

Data migration is the process of extracting master and transactional data from NAV or GP, cleansing and mapping it, then loading it into Business Central's data model. It is the single most variable cost in the project because it scales directly with data volume, data quality, and how many years of history you insist on carrying over.

Most organizations do not need to migrate everything. The standard practice is to migrate all open transactions and master data, plus a defined lookback window of historical data (commonly 2 to 3 years) with older records archived to a data warehouse or left readable in the legacy system.

What increases data migration cost

• Long historical lookback windows (5+ years of transactions).
• Poor source data quality requiring manual cleansing.
• Multiple companies or legal entities in one migration.
• Heavy use of custom fields and tables in the legacy system.

PortMux found that organizations who trim their historical lookback window cut migration timelines by 30 to 50 percent, which directly lowers the labor bill. Data-related tasks consume roughly 30 to 40 percent of total ERP project effort (source: Gartner research, 2026), so scoping this correctly is the highest-leverage decision you make. A proper data quality audit before migration is not optional overhead; it is the cheapest insurance you can buy against a mid-project overrun.

Customization rework is the cost of rebuilding legacy NAV or GP modifications as Business Central extensions, and it is often the most underestimated line item. Business Central does not support the old code-modification model, so every legacy customization must be either replaced by native functionality, sourced from an AppSource app, or rewritten as a modern extension.

This is actually an opportunity. Many NAV and GP customizations built years ago now exist natively in Business Central or are available as low-cost apps. The mistake is instructing a partner to recreate every legacy modification blindly, which multiplies development hours for features you may no longer need.

How to control customization cost

1. Inventory every legacy customization and score how often it is actually used.
2. Map each one to a native Business Central feature, an AppSource app, or a required extension.
3. Retire everything unused before requesting a quote.
4. Budget extension development only for the genuinely custom items that remain.

Retiring unused legacy customizations before quoting lowers total migration cost by 20 to 40 percent, according to PortMux analysis of midmarket migrations. Integrations follow the same logic. Connections to payroll, CRM, e-commerce, and reporting tools each add cost, so confirm which integrations are still business-critical before scoping them into the project.

The single best money-saving move in a Business Central migration is a ruthless customization audit. Most shops carry a decade of modifications they no longer use, and paying to rebuild them is pure waste.

Ryan Loiacono, Founder, Untapped Connections

There are three main paths to Business Central: a clean re-implementation, an assisted data migration using Microsoft's cloud migration tools, and a partner-led full migration. The right choice depends on how much of your legacy configuration and history you need to preserve versus how much you want a fresh start.

A clean re-implementation is a fresh Business Central setup where you bring master data and open balances but leave historical transactions behind. It is the fastest and lowest-cost path when your legacy configuration is dated. Microsoft's assisted cloud migration tool automates replication of NAV, GP, and on-premises Business Central data into a SaaS tenant and works well when your data model is relatively clean.

Roughly 55 to 75 percent of ERP migrations run over their planned timeline (source: Panorama Consulting Group, 2026), and phased hybrid rollouts are the main defense for large, complex environments because they contain risk to one entity at a time. PortMux typically recommends the assisted cloud tool for clean midmarket shops and a partner-led approach only when customization volume genuinely demands it.

The hidden costs in a Business Central migration are the ones outside the initial quote: data cleansing labor, user training, parallel-run periods, post-go-live support, and change management. Together these can add 15 to 30 percent to a project that was scoped on licensing and implementation alone, which is why so many ERP budgets overrun.

The classic trap is signing the lowest partner bid, then discovering that data cleansing, training, and hypercare support were carved out as change orders. Always confirm what a fixed-fee quote actually includes.

Costs teams routinely forget

• Data cleansing: manual correction of duplicate vendors, stale items, and broken references.
• Training: end-user onboarding, which drives adoption and reduces support tickets.
• Parallel run: operating old and new systems together during month-end close for one or two cycles.
• Hypercare: intensive post-go-live support for the first 30 to 60 days.
• Integration maintenance: ongoing upkeep of connections after go-live.

The average midmarket ERP project exceeds its budget by 15 to 25 percent (source: Panorama Consulting Group, 2026). PortMux advises finance teams to add a 15 to 20 percent contingency line specifically for data and training, because those are the two areas where quotes are consistently optimistic and reality is consistently more expensive.

To estimate your Dynamics NAV GP migration Business Central cost, sum four numbers: annual licensing (users times tier price), one-time implementation labor, data migration effort, and customization or integration development, then add a 15 to 20 percent contingency. This gives a defensible planning figure before any vendor conversation.

Step-by-step cost estimation

1. Count full users and light users, then apply Essentials, Premium, and Team Member rates for annual licensing.
2. Inventory legacy customizations and mark each as replace, retire, or rebuild.
3. Define a historical data lookback window and estimate record volume.
4. List integrations still considered business-critical.
5. Request fixed-fee quotes from two or three Business Central partners against this identical scope.
6. Add a 15 to 20 percent contingency for data cleansing and training.

The most powerful cost reducers are all decisions you control. Trimming the data lookback window, retiring unused customizations, and choosing the assisted cloud migration path over a full custom rebuild routinely cut total cost by 20 to 40 percent. PortMux consistently sees that the organizations who do this scoping work before engaging a partner get cleaner quotes, fewer change orders, and faster go-lives than those who hand a partner an undefined project.

The Dynamics NAV GP migration Business Central cost is driven far more by data and customization decisions than by licensing, and those decisions are entirely within your control. Plan on 30,000 to 250,000 dollars total, with data migration and customization rework accounting for the largest share, and expect a 3 to 9 month timeline for most midmarket moves.

Scope your data, audit your customizations, choose SaaS over on-premises unless compliance forces otherwise, and add a real contingency for training and cleansing. Do that groundwork before you call a partner, and you will control the two costs that blow up ERP budgets. PortMux recommends treating the pre-quote scoping phase as the highest-return work in the entire project, because every hour spent there saves several during implementation.

• Home
• Pricing
• Contact
• HubSpot Breeze Agent Pricing for PE Portfolio Migration
• Usage-Based Billing Migration: Escape Adyen Lock-In
• Intercom Salesforce Acquisition Data Migration Guide
• Carve-Out IT Separation Day 1 Data Readiness Guide