Dynamics migration

Dynamics 365 migration: GP, NAV, AX, and on-premises CRM

Veratas delivers structured Dynamics 365 modernisation programmes for organisations moving off legacy Microsoft ERP and CRM platforms. Whether you are on GP, NAV, AX, or on-premises CRM, we cover the full migration: business process re-engineering, data migration, customisation rebuild, testing, and cutover. One team, one programme, one go-live.

Book a free migration scoping call
Migration paths we cover

Dynamics migration programmes

GP to Business Central, NAV to Business Central, AX to F&O, and on-premises CRM to Dynamics 365 online, each with a structured programme covering data, process, code, and cutover.

01.

Dynamics GP to Business Central

Structured modernisation from GP to cloud ERP

  • Legacy GP environment assessment: version, modules, customisations, and ISV solutions
  • Business process re-engineering: redesigning GP workflows for Business Central
  • Chart of accounts migration: GL structure, dimensions, and financial reporting rebuild in Power BI
  • Master data migration: customers, vendors, items, and GL accounts
  • Open balance migration: AR, AP, inventory, and bank reconciliation at cutover
  • Historical transactional data migration with full audit trail
  • Parallel run, cutover rehearsal, and post go-live hypercare support

02.

Dynamics NAV to Business Central

Upgrade from on-premises NAV to cloud Business Central

  • NAV version assessment: NAV 2013 through NAV 2018 upgrade roadmap planning
  • Customisation audit: identifying C/AL code that must be rewritten as AL extensions
  • AL extension development: converting NAV customisations to upgrade-safe extensions
  • Database migration from NAV SQL to Business Central cloud
  • Data validation and reconciliation: trial balance, open items, and inventory cross-checks
  • User training for the transition from NAV UI to Business Central web client
  • Phased or big-bang cutover with documented rollback procedures

03.

Dynamics AX to Dynamics 365 F&O

Enterprise upgrade from AX 2009 or 2012 to D365 F&O

  • AX environment analysis: code base, ISV solutions, integrations, and data volumes
  • Fit-gap analysis: AX customisations versus D365 F&O standard functionality
  • X++ code migration: converting AX customisations to D365 F&O extension model
  • Data migration using Data Management Framework for all AX entities
  • Integration re-architecture: replacing AX connectors with D365 APIs and Dataverse
  • Regression testing: RSAT, Task Recorder, and Azure DevOps test automation pipelines
  • Phased go-live by legal entity or by module to reduce cutover risk

04.

On-Premises CRM to Dynamics 365 Online

Moving from legacy on-premises CRM to cloud

  • On-premises CRM version assessment: CRM 2011 through CRM 2016 migration paths
  • Customisation audit: entities, workflows, plugins, and SSRS reports to migrate
  • Data migration: accounts, contacts, opportunities, cases, and full activity history
  • Plugin and workflow migration: rewriting legacy code for Dynamics 365 online
  • Integration re-architecture: replacing on-premises connectors with cloud-native APIs
  • User acceptance testing and phased user migration with adoption support

05.

Data migration execution

Technical ETL and validation across all Dynamics migrations

  • Source system data profiling: quality assessment, duplicates, and missing fields
  • Data mapping: source to target field mapping with transformation and cleansing rules
  • ETL pipeline development using Azure Data Factory, SSIS, or Fabric Pipelines
  • Staging environment validation: pilot loads with functional user sign-off before production
  • Production cutover: phased or big-bang with automated reconciliation reports
  • Post-migration validation: trial balance, open items, and transaction cross-checks
  • Rollback procedures and cutover rehearsal playbooks documented for every migration
Fixed-fee assessment

Dynamics migration readiness, from $3,500

A fixed-scope assessment of your current system and a costed plan to move, before you commit to the migration.

Fixed fee from $3,500   |   2 weeks   |   Price shown up front

Book your assessment
What $3,500 covers

A costed migration plan

We assess your current system and hand you a fixed-fee migration roadmap.

  • Current-state review of your existing system (GP, NAV, SL or other)
  • Data quality and volume assessment
  • Target Dynamics 365 fit and gap analysis
  • Migration approach and cutover plan
  • Risk and dependency review
  • Fixed-fee migration roadmap and quote

Dynamics 365 licences are billed per user per month through Microsoft CSP. The $3,500 covers the assessment services.

No surprises

What is in the $3,500, and what we quote separately

The migration itself is scoped from the roadmap and quoted before you commit.

In your $3,500The migration, quoted from the roadmap
Current-state and data assessmentThe migration build itself
Target fit and gap analysisData migration and validation
Migration and cutover planCustomisations and integrations rebuild
Fixed-fee migration roadmapGo-live and hypercare

You pay $3,500 for the assessment. The migration is scoped from the roadmap and quoted transparently, always shown before you decide.

Why Veratas for migrations

What makes our Dynamics migrations different

Most Dynamics migration projects exceed timeline and budget. Veratas delivers Dynamics migrations on time and on budget by using documented playbooks per source platform, GP, NAV, AX, on-premises CRM, and managing the migration as a programme, not a single project.

Documented migration playbooks for GP, NAV, AX

Dynamics GP → Business Central. NAV → Business Central. AX 2009/2012 → Dynamics 365 F&O. On-premises Dynamics CRM → Dynamics 365 Online. Each path documented with data mapping, customisation re-platforming, integration migration, and risk mitigation steps.

Data integrity from source to target

Documented data mapping per migration type. ETL pipelines with full reconciliation reports. Pre-cutover dry runs in UAT. Post-cutover data validation. Optional parallel run period during which both systems receive updates and reconcile.

Customisation re-platforming

GP Dexterity customisations → Business Central AL extensions. AX X++ customisations → F&O X++ (with cleanup) or Power Platform replacements. NAV C/AL → AL extensions. CRM 4.0/2011/2013/2015 customisations → modern Power Platform. We don’t just move data, we modernise the surrounding logic.

Zero-disruption cutover patterns

Cutover weekends managed minute-by-minute with documented runbooks. Pre-cutover communication and training. Hypercare with daily standups and accelerated SLAs. Rollback plans documented even when not used.

Migration paths

Supported Dynamics migration paths

The migration paths we deliver most frequently. Typical durations assume mid-market complexity; larger or more customised estates extend timelines. All durations include data migration, customisation re-platforming, user training, and 30-day hypercare.

From
To
Why
Typical duration
Dynamics GP
Business Central
Mid-market replacement of GP
16-28 wks
Dynamics NAV (2009-2018)
Business Central
Direct evolution path
12-20 wks
Dynamics SL
Business Central or F&O
End-of-life replacement
20-32 wks
Dynamics AX 2009
Dynamics 365 F&O
End-of-life replacement
26-44 wks
Dynamics AX 2012
Dynamics 365 F&O
Mainstream upgrade path
20-36 wks
Dynamics CRM 2011/2013/2015/2016
Dynamics 365 CRM (online)
End-of-life replacement
12-24 wks
Sage / NetSuite / SAP B1
Business Central or F&O
Competitive replacement
20-36 wks
Salesforce
Dynamics 365 CRM
Competitive replacement
12-20 wks
Migration phases

Standard Dynamics migration phases

Veratas Dynamics migrations follow five phases regardless of source platform. Phase durations vary by complexity but the structure is consistent.

01

Discovery

Source system audit, modules in scope, data volumes, customisations, integrations, users. Business process documentation. Microsoft fit-gap analysis. Output: fixed-price proposal with deliverables, timeline, and acceptance criteria.

02

Design

Target Dynamics 365 environment design. Data mapping document (source field → target field, with transformation logic). Customisation re-platform plan. Integration re-platform plan. Output: signed-off functional design document.

03

Build

Target Dynamics 365 environments provisioned (Dev → UAT → Pre-Prod → Prod). Configuration of all modules. AL extensions / X++ extensions developed. Power Automate flows built. Integration build. ETL pipelines built and tested in dev.

04

Data migration & UAT

Multiple test loads to UAT. Reconciliation report per load. Defect triage. User Acceptance Testing with business users. Defect remediation. Final UAT sign-off. Output: defect-free UAT ready for cutover dry run.

05

Cutover & hypercare

Cutover dry run in pre-prod environment. Detailed cutover runbook. Cutover weekend execution with hourly checkpoints. 30-day hypercare with daily standups. Microsoft Support engagement. Output: production system handed over to managed services.

Industries

Dynamics migration patterns by industry

Each industry has unique migration patterns based on which Dynamics product they came from and which target makes sense for their business.

Manufacturing

AX 2012 → F&O most common. Manufacturing module re-fit (routings, BOMs, MRP). Shop-floor integration migration. Production analytics moved to Microsoft Fabric.

Distribution & wholesale

GP or NAV → Business Central typical. Multi-location warehousing re-design. EDI migration. Retail trading partner re-integration. Shopify / Amazon connector migration.

Professional services

GP or Sage → Business Central + Project Operations. Project accounting migration. Time/expense system migration. Resource scheduling re-platforming.

Non-profit

GP fund accounting → Business Central with AL extensions for fund accounting. Grant tracking migration. Donor management migration to Dynamics 365 Sales.

Public sector

Often retains AX 2012 then moves to F&O. Compliance with regulatory data retention requirements. GCC tenant deployment where required.

Healthcare

GP or NAV → Business Central. HIPAA Microsoft compliance baseline. Clinical billing integration. Microsoft Cloud for Healthcare alignment where applicable.

FAQ

Dynamics migration questions answered

GP end-of-life, cost, timeline, data history, customisations, and risk-mitigation questions.

Dynamics GP mainstream support has ended. Extended support continues through April 2028 for some versions, but Microsoft will stop adding new features, regulatory updates may lag, and the support cost grows. Most GP customers should plan migration to Business Central within 24 months. Veratas runs GP-to-Business Central migration assessments as fixed-price engagements.
A fixed-scope migration readiness assessment starts from $3,500. Implementation services: $80,000-$300,000 depending on complexity (number of companies, customisations, integrations, historical data depth). Add Microsoft licensing (Business Central Essentials $70/user/mo or Premium $100/user/mo), ISV solutions, and any custom AL extension development. Larger enterprise migrations exceed $500,000.
AX 2012 → F&O: typical 20-36 weeks. AX 2009 → F&O: 26-44 weeks (older versions require more customisation re-platforming). Programmes with significant customisation, multi-entity, or compliance complexity can exceed 12 months. Real timelines confirmed after a discovery workshop.
Generally:
We catalog source customisations during discovery. Then per customisation: (1) Replace with target platform standard functionality, preferred. (2) Replace with Power Platform (Power Automate flow, Power App), modern, low-code. (3) Re-implement as AL extension (Business Central) or X++ extension (F&O), preserved, but cost more. (4) Decommission, for customisations no longer needed. Output is a customisation disposition document.
Three options: (1) Full historical migration, all transactions imported with full history (expensive, slow, but seamless). (2) Open balance migration, opening balances + open transactions only (cheaper, faster, requires retained access to source system for historical lookup). (3) Open balance + summary history, opening balances + monthly summary roll-ups for history (compromise). Decision depends on regulatory requirements and budget.
Most cutovers run over a 48-72 hour weekend window. Source system frozen Friday evening, final data extraction, target system loaded and validated, business users go live Monday morning. For 24/7 operations we use minimal-downtime patterns (Database Migration Service for live replication), downtime reduced to 1-4 hours at a planned moment.
Yes. Parallel run: both source and target systems receive transactions for a defined period (typically 2-4 weeks), with reconciliation between them. Used when business risk requires absolute confidence before cutting over. Adds 4-8 weeks to project but reduces business risk for high-stakes migrations (financial services, healthcare).
Yes. Microsoft provides upgrade tooling for Dynamics CRM 2011, 2013, 2015, 2016 → Dynamics 365 Online. We extend this with customisation re-platforming (Microsoft tooling preserves customisations but doesn't modernise them), reporting migration, and integration migration. Typical duration 12-24 weeks.
Every cutover has a documented rollback plan: criteria that trigger rollback, technical steps to revert, communication plan, and recovery procedures. Source system is kept available (read-only) for the hypercare period and beyond. In practice, rollback is rare, by cutover weekend we have completed multiple test runs in UAT and pre-prod.
A current-state review of your existing system, a data quality and volume assessment, a Dynamics 365 fit and gap analysis, a migration and cutover plan, a risk review, and a fixed-fee migration roadmap and quote. Typically 2 weeks.
The migration build itself, data migration and validation, rebuilding customisations and integrations, and go-live with hypercare are scoped from the roadmap and quoted transparently.
Get started

Ready to modernise from legacy Dynamics?

GP, NAV, AX, or on-premises CRM, structured Dynamics 365 migration programmes from Veratas.

Schedule a discovery call