Business Central Migration Services

Your Legacy ERP Has an Expiry Date. Don’t Just Upgrade, Evolve.

We move companies from Dynamics NAV, GP, SL, QuickBooks, and NetSuite to Microsoft Business Central, on time, on budget, with every balance reconciled on day one.

Share Your Migration Needs
Microsoft Solutions Partner
In practice since 2001
Trusted by Fortune 500 & SMBs
  1. Home
  2. Business Central Migration

What Is Business Central Migration?

Business Central migration moves your company's ERP data, workflows, and customisations from a legacy system like Dynamics NAV, GP, QuickBooks, or NetSuite to Microsoft Dynamics 365 Business Central. It typically takes 2–6 months and costs from $5,000 depending on company size and complexity.

2–6 mo.

Typical timeline

$5K+

Starting investment

Migrates from

Dynamics NAV Dynamics GP QuickBooks NetSuite SAP Other legacy systems

Why Congruent Software for Business Central Migration Services?

We are a certified Microsoft Solutions Partner with more than two decades of Business Central migration experience across nonprofits, manufacturing, construction, and security services. We will tell you what your migration involves, what it costs, what can go wrong and how we prevent it.

Delivering Microsoft Dynamics migrations since 2001

Flexible engagement models with fixed price option

Multiple migration cycles before go-live

Certified Microsoft Solutions Partner

30+ team of Dynamics 365 certified consultants

Expertise across nonprofits, manufacturing, construction & distribution

What Our Business Central Migration Services Actually Covers

Our Services Covers More Ground Than Most Teams Anticipate.

A Business Central migration is not just a data transfer. It is a structured programme spanning seven work areas. Understanding what each involves will help you scope your project and evaluate any proposal you receive.

What Typically Migrates

General Ledger Balances AR Open Transactions AP Open Transactions Customer Master Data Vendor Master Data Item Master & Inventory Open Purchase Orders Open Sales Orders 2–3 Years Transaction History

User accounts are recreated in Microsoft 365 separately. Permissions and roles are configured as part of the BC security setup.

System Audit & Scoping

Every module, customisation, integration, and data anomaly assessed before we commit to a price. No surprises later.

Data Extraction & Cleaning

Financial records, inventory, customers, vendors and transactions are extracted, deduplicated, and reconciled against your trial balance. Data cleaning is where projects lose time. We budget for it upfront.

Environment Design & Configuration

Chart of accounts, dimensions, posting groups, tax codes, security model are designed from scratch around how your business operates today.

Custom Development & Extensions

Legacy customisations assessed one by one. Rebuilt, replaced with native BC features, or retired. Every decision made transparently, with your sign-off.

Integration Migration

CRM, payroll, warehouse, ecommerce, banking and similar connections remapped to Business Central's REST API architecture. A defined workstream, not an afterthought.

Testing & User Acceptance

We write the test scripts. Your team runs them against real business scenarios. Nothing moves to production without their sign-off.

Cutover Strategy & Support

Final data migration, legacy system shutdown, go-live. Our team stays on standby for the first two weeks. Critical issues are resolved within initial hours.

"All users love the Production very much! If you remember my team was not so excited as field office accountants, Country Directors, Regional Directors and cardholders are. Now, my team including me like the new system as well!
My team and I really appreciate your work and support! Please send our thanks and appreciation to your team! Millions thanks for everything you do for us!"

Senior Director of Grants and Finance

Leading Nonprofit Organization

Read The Full Case Study

Which ERP Systems Can Move to Business Central?

Every Legacy System Has a Path Out. Here's Yours.

Microsoft Business Central accepts direct migration from Dynamics NAV (all versions), Dynamics GP (2015 and later), Dynamics SL, and QuickBooks, using purpose-built Microsoft migration tools. Migrations from NetSuite, Acumatica, Sage, and Oracle require manual data extraction and ETL processes. Business Central on-premises environments can migrate to Business Central online using Azure Data Factory.

Our previous experience in migration from NAV, GP, SL and on-premises BC reduce timelines considerably compared with building from scratch.

Source System Microsoft Tool Available Key Watch Points
Dynamics NAV (all versions) Yes — on-prem upgrade path C/AL code must be converted to AL. Multi-version gap can be large.
Dynamics GP (2015+) Yes — Cloud Migration Tool GP end of life confirmed. Dexterity and VBA customisations need full rebuilds.
Dynamics SL Partial — configuration packages SL project accounting and job costing need careful remapping.
QuickBooks Desktop / Online Yes — QB migration app Chart of accounts and class structure often need redesign for BC.
NetSuite No — manual / middleware No native tool. Requires ETL build. High data volume and configuration complexity.
BC On-Premises (any version) Yes — Azure Data Factory Cleanest migration path. Main task is extension compatibility and licensing change.
Sage 100 / 300 / Intacct Partial — config packages Chart of accounts restructuring often required.
Acumatica No — manual / ETL Object-relational data model differs significantly from BC.

Why BC Migrations Are Accelerating Right Now?

Every Month You Wait, Your Legacy System Gets More Expensive.

Three things are driving the current wave of Business Central migration activity. All three are time sensitive.

Legacy System Support Is Ending

Dynamics NAV Mainstream ended October 2023
Dynamics GP — new licences Ended April 2025
Dynamics GP — security updates Stop April 2031
Dynamics SL Mainstream ended 2023

Staying on these systems means no new features, rising security risk, and fewer people who know the code.

On-Premises Infrastructure Costs Are Compounding

$80K–$200K

per year, on-premises legacy Dynamics

  • Hardware refresh and maintenance
  • SQL Server licensing
  • IT staff and administration
  • Backup systems and storage
  • Disaster recovery infrastructure

Business Central eliminates all of it. Microsoft owns the infrastructure.

AI Capabilities Are Locked Behind Cloud ERP

Microsoft Copilot for Business Central is available on the cloud version.

  • Bank reconciliation
  • Cash flow forecasting
  • Inventory replenishment
  • Late payment prediction

Companies that migrate now start building the data foundation that makes AI useful.

Share Your Migration Needs

What the Business Central Migration Timeline Looks Like.

Every Migration Phase Has a Defined Output & Nothing Moves Forward Without It.

Timeline depends on four variables: data volume and quality, number of legal entities, customisation depth, and integration complexity.

Phase 1 2–3 weeks

Discovery & Scoping

System audit, data profiling, integration mapping, stakeholder alignment.

Deliverables

Scope document
Risk register
Project charter
Phase 2 2–4 weeks

Environment Design

Chart of accounts, dimension structure, security model, integration architecture.

Deliverables

Signed-off technical design
Phase 3 4–6 weeks

Data Extraction & Cleaning

Legacy data export, deduplication, master data standardisation, trial balance reconciliation.

Deliverables

Clean, validated data set
Phase 4 4–8 weeks

Build & Configure

BC environment setup, AL extension development, integration builds, report migration.

Deliverables

Configured BC environment ready for testing
Phase 5 1–2 weeks

Data Migration Test Run

Load data into test environment, reconcile GL, AR, AP, validate completeness.

Deliverables

Migration validation report
Phase 6 3–4 weeks

User Acceptance Testing

Business users test real scenarios, issues logged and resolved, training delivery begins.

Deliverables

UAT sign-off from your team
Phase 7 1 week

Final Migration & Cutover

Final data load, legacy system shutdown, production go-live.

Deliverables

Live Business Central system
Phase 8 2 weeks

Hypercare

On-call support, critical issue resolution ≤4 hours, post-go-live stabilisation.

Deliverables

Stable, operating system
Phase 9 4–8 weeks

Optimisation

Performance tuning, Copilot activation, report refinement, training completion.

Deliverables

Fully optimised production environment

How Long Does Business Central Migration Take?

Small companies, clean data,
no customisations

8–12 weeks

Mid-market,
standard complexity

4–5 months

Multi-entity,
heavy customisations

6–9 months

No commitment required — we scope first, then quote.

Get a custom timeline for your environment

What Business Central Migration Costs?

Real Numbers By Company Size Without Any Guesswork.

Migration cost is driven by four factors: the complexity of your current system, how clean your data is, how many customisations need rebuilding, and your choice of engagement model.

Migration services cost by company profile

SMB

10–50 users · Single entity

Starting from

$5,000

Single legal entity
Up to 2 integrations
Standard BC configuration

Mid-Market

Most Common

50–300 users · Multi-entity

Starting from

$25,000

Up to 3 legal entities
3–5 integrations
Custom AL extensions included

Enterprise

300+ users · Multi-currency

Starting from

$100,000

Multi-entity & multi-currency
Enterprise integrations
On-site support option

Annual Business Central licensing depends on user count and is separate from migration services.

What shapes your final number

What Drives Cost Up

Data quality issues

Budget 30–40% of migration effort for data work if your master data is unmanaged.

Heavy legacy customisation

Every custom feature in NAV or GP needs individual assessment which may days or sometime weeks.

Complex integrations

CRM, payroll, warehouse, and ecommerce each are separate workstreams remapped to BC's REST API.

Multi-currency and multi-company

Each legal entity adds approximately 20–30% to migration effort. Multi-currency adds configuration and testing complexity.

What Keeps Cost Down

Clean, standardised data

Well-maintained customer, vendor, and item records save weeks of effort.

Accepting native BC features

Modern BC covers what many legacy customisations were built to do. Accept the native version and save development cost.

Flexible delivery models

An onshore–offshore blend reduces implementation cost by 20–30% at no reduction in quality.

Our Five stage methodology to reduce risk during business central migration

Migrations Fail in Predictable Ways, We Address Each One Of Them.

Most Business Central migration failures trace back to the same five issues: GL reconciliation errors on go-live, custom code that breaks in the cloud, integrations that stop passing data, users who revert to spreadsheets, and go-lives timed against a financial close. Every one is the result of a step that was rushed or skipped. Our five-stage methodology was designed specifically around these failure points. Each stage exists because we have seen its absence cause a project to fail.

Stage 1

Diagnose Before You Design

We spend two to three weeks reviewing every custom object, integration endpoint, and data anomaly in your legacy system before writing a single line of configuration. Most projects fail here silently teams start building before they understand what they are building on. Projects that skip this stage carry unresolved risk into every phase that follows.

Prevents

Custom reports, workflows, and integrations that break at go-live.

You Get

Risk register, scope document, data quality assessment, integration inventory.

Stage 2

Agree the Architecture on Paper

Chart of accounts, dimension framework, security model all agreed with your finance and IT leads before configuration starts. Changing architecture at the design stage costs nothing. Changing it mid-build costs weeks.

Prevents

Costly mid-project redesigns that extend timelines and inflate budgets.

You Get

Technical design document, data mapping spreadsheet, architecture sign-off.

Stage 3

Migrate Data Three Times Before Go-Live

We run three migration cycles: a rough load to identify structural issues, a validated load with full reconciliation, and a dress rehearsal that mirrors go-live exactly. We do not proceed to UAT until every GL balance, AR aging figure, and AP total reconciles to your source system.

Prevents

GL balances that don't reconcile on day one — the most common and most costly migration failure.

You Get

Three reconciliation reports, signed data sign-off.

Stage 4

Test Against Your Actual Business

UAT scripts are built around your real transactions: month-end close, purchase orders, customer invoicing, inventory movements. Your users run the tests. We fix every issue. Change management preparation runs in parallel for eight weeks. Nothing goes to production without your team's sign-off.

Prevents

User avoidance — where the technical migration succeeds but the organisation never adopts the system.

You Get

Custom UAT scripts, issue log, business sign-off.

Stage 5

Go Live With a Rollback Plan in Hand

Go-lives are always scheduled for the start of a new financial period. On cutover day we have a precise runbook, a tested rollback plan, and a support team on standby. Two weeks of hypercare support is included as standard. Critical issues are resolved within four hours.

Prevents

Extended downtime from a go-live timed against a financial close, or an unplanned incident with no recovery path.

You Get

Cutover runbook, rollback plan, two-week hypercare included.

Which Business Central Migration Approach Is Right for You?

Two Approaches. One Right Answer.

Your answer depends on how many entities you have, how clean your data is, and how much risk your organisation can absorb in a single cutover event.

Criteria Phased Migration Big Bang Migration
What it means Migrate one entity or module at a time Migrate everything in a single cutover event
Risk level Lower — problems in Phase 1 are fixed before Phase 2 Higher — all risk concentrated in one event
Overall timeline Longer (entities migrate sequentially) Shorter (one consolidated timeline)
Cost Higher short-term (parallel systems running) Lower (no parallel operation period)
Disruption level Lower — staged organisational change Higher — full organisation switches at once
Best for Multi-entity companies, first-time BC users, heavy customisations Single-company, clean data, experienced internal team, tight board deadline

Our Recommendation

For most mid-market companies: phased migration. The first entity is your pilot. Your team learns the system, process gaps surface early, and each subsequent entity takes less time than the last. For small, single-company environments moving from QuickBooks or clean on-premises BC, big bang is the right call with shorter timeline, faster ROI.

Business Central Migration for Nonprofits

Mission-Led Organisations Need More Than a Standard ERP Setup.

If your organisation manages grants, restricted funds, or government programme funding, general BC migration guides don't cover what you need. You need to plan your migration to account for these explicitly.

Microsoft nonprofit pricing: Qualifying nonprofits receive significant discounts on Business Central licensing through Microsoft's nonprofit programme.

Fund accounting configuration

BC handles fund accounting through its dimension framework. Mapping restricted and unrestricted funds correctly upfront is essential. If done incorrectly, it produces reporting that satisfies neither programme managers nor auditors.

Grant and restriction management

Grant lifecycle tracking right from award through drawdown to close-out needs deliberate design in BC or through a third-party AppSource extension. We'll advise on the right fit for your grant volume and complexity.

Donor system integration

Salesforce NPSP, Blackbaud Raiser's Edge, and DonorPerfect all have BC integration options. We design the connection for pledge tracking, donation recording, and campaign reporting as a defined workstream.

Enterprise BC Migration: Multi-Entity, Governance, and Compliance

At Enterprise Scale, Migration Becomes a Programme Before It Becomes a Project.

For organisations with 300+ users, multiple legal entities, or strict compliance requirements, standard migration planning is not enough.

Multi-entity data migration

Each legal entity is a separate migration project within a programme. We pilot with your simplest entity first, validate end-to-end, then apply that process to your most complex entities.

Intercompany transactions

Business Central's intercompany module handles eliminations and cross-entity postings. Mapping decisions for intercompany history must be made before the data migration design is locked.

Role-based access and compliance

Permission sets, approval workflows, segregation of duties, and audit trail configuration are designed in Phase 2, not after go-live.

SOX, HIPAA, and industry compliance

Business Central's cloud platform maintains these certifications. We document compliance mapping as part of enterprise migration delivery.

SOC 1 SOC 2 ISO 27001 HIPAA GDPR

After Business Central Migration: What Happens in the First 90 Days

Most Migrations Fall Apart Post Go-live, But We Ensure Better Adoption.

Go-live is not the end of the project. It is the start of optimisation. In our experience, organisations that invest in the 90 days after going-live achieve significantly better adoption and ROI than those that treat go-live as the finish line.

Training completion by role

Role-based training continues in the weeks after go-live, focusing on edge cases and transactions users encounter for the first time in production.

Performance tuning

Real usage patterns expose issues test environments do not. We tune query structures, posting group configurations, and report designs based on actual production behaviour.

Microsoft Copilot activation

Once data quality is confirmed in production, Copilot is activated for bank reconciliation, late payment prediction, inventory forecasting, and sales suggestions. We configure and train your team on each relevant feature.

Phase 2 scoping

Every migration surfaces requirements not in the original scope. Additional modules, integrations, Power BI reporting, and automation workflows are scoped and planned for Phase 2.

Frequently Asked Questions

Talk to our Migration Specialist

If you want a direct conversation about your specific migration situation, share your needs and one of our specialists will respond quickly.