Dynamics AX to Dynamics 365 Migration: Guide & Best Practices

Key Takeaways

• Timeline: Most AX 2012 to Dynamics 365 projects take around 9 to 18 months, depending on scope, customizations, data, integrations, and testing.

• Migration path: AX 2012 R2/R3 have supported upgrade paths, while AX 2009 follows a separate migration approach.

• Customizations: Assess each one to retain, replace, redesign, or retire rather than rebuilding everything.

• Data: Clean and validate data before migration, and migrate only what the business needs.

• Integrations: Review every integration and determine whether to retain, redesign, replace, or retire it.

• Key risks: Legacy customizations, poor data quality, complex integrations, ISV dependencies, testing, and cutover planning.

• Best approach: Start with an assessment and use standard Dynamics 365 functionality wherever practical.

• Bottom line: The goal is not to recreate AX in Dynamics 365, but to build a simpler, scalable, and future-ready ERP environment.

• Why Dynamics Square: With 14+ years of experience, 500+ implementations, 150+ Microsoft Certified Consultants, and Microsoft Solutions Partner status, Dynamics Square supports organizations across the USA, UK, and Canada.

Organizations running Microsoft Dynamics AX are increasingly looking to modernize their ERP environments with Dynamics 365 Finance and Dynamics 365 Supply Chain Management. But the decision to migrate from Dynamics AX to Dynamics 365 should not be approached as a simple technical upgrade.

A successful migration is an opportunity to simplify business processes, reduce technical debt, modernize integrations, improve data quality, and create an ERP environment that can support future growth.

The right question is not simply, "How do we move AX to Dynamics 365?"

It is:

What should we migrate, what should we redesign, what can be replaced with standard Dynamics 365 functionality, and what should we retire?

This guide answers the most important questions businesses ask when planning an AX to Dynamics 365 migration, with practical considerations around timelines, costs, data, customizations, integrations, testing, and go-live.

How Long Does an AX to D365 F&O Migration Take?

Most AX 2012 to Dynamics 365 Finance and Supply Chain Management projects should be planned as a multi-phase transformation, with many organizations requiring roughly 9 to 18 months depending on their environment. 

Smaller and more standardized implementations can take less time, while heavily customized, multinational, or integration-intensive environments can take considerably longer.

The main factors affecting the timeline are:

• Number of legal entities and countries

• Functional scope and modules

• Customization and X++ footprint

• Data volume and quality

• Number and complexity of integrations

• ISV dependencies

• Reporting requirements

• Testing cycles

• User acceptance and training

• Cutover and deployment strategy

The 9 to 18 month range should be treated as a planning benchmark, not a guaranteed delivery timeline. A reliable estimate requires an assessment of the existing AX environment.

For AX 2012 upgrade projects, Microsoft itself structures the process around Analyze, Execute, and Validate phases and recommends using the analysis work to estimate the effort, resources, time, and cost of the project.

Can You Directly Migrate Dynamics AX to Dynamics 365?

Yes, but the migration approach depends on the AX version. Microsoft currently supports upgrades from Dynamics AX 2012 R2 and AX 2012 R3 to finance and operations apps. AX 2009 follows a separate migration approach using Microsoft's Data Migration Tool.

This distinction is important because "AX to D365 migration" can describe very different technical scenarios.

Microsoft also warns that AX 2012 upgrades are complex and should not be assumed to run end to end without data cleanup, tuning, customization work, and remediation.

That makes a version-specific assessment the logical first step.

Why Migrate from Dynamics AX to Dynamics 365?

The primary reason to modernize AX is that the AX product family has reached the end of Microsoft's extended support lifecycle. AX 2009, AX 2012, and AX 2012 R2 reached the end of extended support in 2022, while AX 2012 R3 reached the end of extended support in January 2023.

For businesses, the implications go beyond support dates. A legacy ERP can become increasingly difficult to maintain as specialist skills become less available and customizations, integrations, and infrastructure accumulate technical debt.

Dynamics 365 provides a modern cloud ERP platform and gives organizations an opportunity to rethink how finance, supply chain, reporting, integration, and automation should work.

Common business drivers include:

• Reducing legacy technical debt

• Modernizing finance and supply chain processes

• Improving analytics and reporting

• Simplifying integrations

• Supporting business growth

• Reducing dependence on legacy infrastructure

• Improving operational visibility

• Creating a more sustainable application lifecycle

However, migration should not be justified solely by the end of AX support. The strongest business cases connect modernization to measurable operational and financial outcomes.

What Happens to AX Customizations?

Not every AX customization should be migrated to Dynamics 365. Each customization should be assessed based on its business value, current usage, availability of standard functionality, technical feasibility, and future maintenance requirements.

A useful framework is to classify each customization as retain, replace, redesign, or retire.

For example, if an AX customization duplicates functionality that is now available in standard Dynamics 365, rebuilding it may create unnecessary cost and technical debt. If the customization supports a critical regulatory or business requirement, it may need to be redesigned using the target platform's supported extensibility approach.

This is one of the most important differences between a basic system upgrade and a successful modernization project.

The goal should not be to make Dynamics 365 behave exactly like the old AX system. The goal should be to preserve important business outcomes while reducing unnecessary complexity.

What Happens to AX X++ Code?

AX 2012 code can be brought forward as part of Microsoft's supported upgrade process, but it should not be treated as a simple copy-and-paste exercise. Microsoft provides code upgrade tools that analyze existing code and identify conflicts and remediation work.

The practical process involves reviewing:

• Custom X++ code

• Modified application objects

• Dependencies

• Deprecated functionality

• Extensions

• Reports

• Workflows

• Batch processes

The resulting target code should be maintainable within the Dynamics 365 application lifecycle rather than simply reproducing every legacy implementation decision.

Can AX Data Be Migrated to Dynamics 365?

Yes. AX data can be migrated to Dynamics 365, but organizations should decide what data actually needs to remain operational before starting the migration.

For AX 2012 upgrade scenarios, Microsoft provides a data upgrade process that can bring forward the database and transactional history. Microsoft also recommends data cleanup because database size and data quality can affect the upgrade process.

A strong data strategy separates:

• Master data

• Reference and configuration data

• Open transactions

• Current balances

• Historical transactions

• Documents and attachments

• Data required only for archive or compliance

The important question is not:

"Can we migrate everything?"

It is:

"Which information must remain operational in Dynamics 365, and which information can be archived?"

That decision can significantly influence project complexity.

Should You Migrate All Historical AX Data?

No. Migrating every historical record is not always the best business or technical decision. Historical data that is required for operational processing, audit, regulatory purposes, or active reporting may need to remain accessible. Older information that is rarely accessed may be better handled through an appropriate archive or reporting strategy.

The right approach depends on the organization's retention requirements, reporting needs, audit obligations, and target architecture.

For supported AX 2012 upgrades, Microsoft provides a data-upgrade process capable of bringing forward full transactional history, but organizations should still evaluate whether that is the most appropriate strategy for their particular environment.

What Happens to AX Integrations?

AX integrations should be inventoried and assessed before migration begins. A legacy ERP may have dozens of interfaces that connect finance, supply chain, banking, e-commerce, CRM, warehouse, manufacturing, tax, and other systems.

For every integration, identify its purpose, owner, data, frequency, business criticality, technology, and future requirement.

Then determine whether it should be:

• Retained

• Redesigned

• Replaced

• Retired

This is an important opportunity to remove obsolete interfaces instead of transferring them into the new environment.

What Is the AX to Dynamics 365 Migration Process?

A typical AX to Dynamics 365 migration involves assessment, planning, solution design, data preparation, code remediation, integration development, testing, cutover, and post-go-live stabilization. AX to Dynamics 365 Migration includes the following steps:

1. Assess the current AX environment

Document the AX version, modules, legal entities, customizations, integrations, ISVs, reports, workflows, data, security, and critical business processes.

Microsoft's AX 2012 methodology begins with an Analyze phase specifically designed to identify upgrade effort and create a project plan.

2. Define the future-state solution

Determine which processes should be adopted as standard Dynamics 365 functionality and which require configuration, extension, integration, or redesign.

This is where organizations should challenge legacy processes rather than automatically reproduce them.

3. Prepare the data

Profile data quality, remove unnecessary records, establish mappings, define historical-data requirements, and determine how attachments and documents will be handled.

4. Remediate customizations

Analyze existing X++ and custom functionality. Retire unnecessary customizations and redesign those that remain essential.

5. Modernize integrations

Build or redesign interfaces based on the target Dynamics 365 architecture.

6. Test end-to-end business processes

Testing should cover complete processes such as order-to-cash, procure-to-pay, record-to-report, inventory management, warehouse operations, and manufacturing where applicable.

7. Perform a mock cutover

A mock cutover allows the project team to measure the actual migration process, identify bottlenecks, validate downtime assumptions, and refine responsibilities before production.

8. Go live and stabilize

After production cutover, the team should closely monitor financial reconciliation, integrations, data quality, performance, batch processing, security, and user issues.

What Are the Biggest AX to D365 Migration Challenges?

The most difficult part of an AX migration is often the accumulated complexity of the legacy environment rather than the migration technology itself.

Years of customizations, undocumented interfaces, inconsistent data, obsolete reports, and highly customized processes can make it difficult to determine what should actually move to Dynamics 365.

Based on Dynamics Square's experience delivering Dynamics AX and Dynamics 365 projects, the most common migration challenges are the following:

• Legacy customizations

• Data quality

• Integrations

• Deprecated functionality

• ISV compatibility

• Testing

• Cutover

• User adoption

Microsoft explicitly notes that AX 2012 upgrades require effort around data cleanup, tuning, and customization, and that the upgrade tools should be treated as a framework rather than a complete automated solution.

What We Learned From a Real Dynamics AX Implementation

We've seen first-hand that an AX project is about more than implementing ERP technology. In one of our Dynamics AX 2012 R2 implementations for a nonprofit organization in California, we addressed challenges across finance, inventory, membership, grants, reporting, and customer relationship management.

The implementation helped the organization improve operational visibility, manage inventory more effectively, strengthen financial management, and streamline customer interactions. The organization reported 3X productivity and a 68% reduction in input costs following the implementation.

This experience reinforced an important lesson for organizations planning to migrate from Dynamics AX to Dynamics 365: don't simply replicate the legacy environment. First understand what the business needs to improve, then determine which processes, data, customizations, and integrations should move forward.

The goal of modernization should be a better business system, not just a newer ERP system.

How Much Does It Cost to Migrate AX to Dynamics 365?

There is no reliable single price for an AX to Dynamics 365 migration because implementation scope varies substantially between organizations.

The largest cost drivers typically include the number of users and legal entities, functional scope, customizations, data migration, integrations, ISVs, reporting, testing, training, change management, and deployment complexity.

A meaningful business case should compare three areas:

• Cost of modernization: implementation, licensing, internal resources, data, integrations, testing, training, and change management.

• Cost of remaining on AX: support, infrastructure, specialist skills, maintenance, technical debt, and operational inefficiencies.

• Cost of delay: deferred modernization, increasing complexity, skills shortages, and potential business risk.

For organizations in the USA, the business case should also account for country-specific finance, tax, compliance, reporting, and integration requirements when defining the target solution.

What Are the Best Practices for AX to Dynamics 365 Migration?

The best migrations start with assessment rather than development. Before building anything, understand the current AX environment and establish the supported migration path.

Organizations should also favor standard Dynamics 365 functionality wherever practical. Every unnecessary customization creates additional development, testing, and lifecycle-management requirements.

Data should be treated as a business asset, with business owners involved in deciding what is accurate, necessary, and worth migrating.

Finally, conduct realistic mock cutovers. A successful mock cutover provides evidence about migration duration and downtime rather than relying only on theoretical estimates.

AX to Dynamics 365 Migration Checklist

Before beginning the project, confirm that you have assessed:

• AX version and cumulative updates

• Modules and legal entities

• Customizations and X++ code

• Data volume and quality

• Historical data requirements

• Integrations and external systems

• ISV dependencies

• Reports and workflows

• Security roles

• Future-state business processes

• Testing requirements

• Cutover strategy

• User training and change management

Why Choose Dynamics Square USA for Your AX to Dynamics 365 Migration?

Once an organization understands what an AX to Dynamics 365 migration involves, the next question is often more practical: who can help turn the assessment, decisions, and migration roadmap into a successful implementation?

That is where experience matters.

Turn AX to Dynamics 365 Migration plan into Actual Project with Dynamics Square USA

Dynamics Square has been working with Microsoft business applications since 2011, giving the company more than 14 years of experience helping organizations implement and modernize Microsoft Dynamics solutions. Over that period, the team has delivered 500+ implementations for clients, working across different industries, business processes, and organizational requirements.

That experience is supported by a team of 150+ Microsoft Certified Consultants and Dynamics Square's status as a Microsoft Solutions Partner. For organizations planning an AX modernization, that combination is important because migration decisions often span much more than the ERP application itself. They involve finance, supply chain, data, integrations, reporting, security, users, and the broader Microsoft technology ecosystem.

Dynamics Square also maintains a presence across the USA, UK, and Canada, enabling it to support organizations across multiple markets and business environments.

For a company considering its next ERP step, the objective should not simply be to find someone who can move AX data into Dynamics 365. It should be to find a partner that can help answer the harder questions first: What should be migrated? What should be redesigned? What should be retired? How can legacy complexity be reduced? And how can the new Dynamics 365 environment deliver measurable business value?

If you are planning to migrate from Dynamics AX to Dynamics 365, schedule a demo with Dynamics Square USA can help you assess your current environment, define the right migration approach, and build a roadmap around your business requirements rather than simply reproducing your legacy AX system.