AX 2012 to D365 F&O Upgrade: Best Approach?

zarasiddiqui
zarasiddiqui Member Posts: 2
in Dynamics AX

Hi everyone,

We’re currently running Dynamics AX 2012 and planning a move to Dynamics 365 Finance & Operations. I’d appreciate some practical insights from those who’ve already gone through this journey.

  • Did you go with reimplementation or code upgrade? What influenced your decision?
  • How did you handle existing customizations and ISV solutions?
  • What challenges did you face during data migration?
  • What timeline should we realistically expect for a mid-sized business?
  • How did you approach user training and change management?

We’re particularly concerned about handling custom modules and ensuring good performance after go-live.

Would be great to hear real experiences, lessons learned, or things to avoid.

Thanks in advance.

Comments

  • vignesh2498
    vignesh2498 Member Posts: 1

    Hi Zara,

    This is a common scenario right now, and the approach really depends on how complex your current AX 2012 setup is.

    From most recent projects, reimplementation is generally the preferred route, especially for mid-sized businesses. It allows you to start fresh, remove outdated customizations, and take full advantage of standard features in D365 F&O. Code upgrade is usually chosen only when there are heavy custom modules that are still business-critical and cannot be replaced easily.

    For customizations and ISVs, the key is evaluation. Many AX 2012 customizations are no longer needed because D365 has stronger native capabilities. For ISVs, you’ll need to check if your current solutions are supported in D365 or if you need to switch to newer alternatives. Trying to carry everything forward often leads to unnecessary complexity.

    Data migration is where most teams face challenges. Data quality issues, duplicate records, and large volumes of historical data can slow things down. It’s better to clean data early and only migrate what is actually needed for operations. Archiving older data helps improve performance and reduces risk during migration.

    In terms of timeline, for a mid-sized organization, reimplementation typically takes around 6 to 12 months. This can vary based on the number of integrations, customizations, and internal readiness.

    For training and change management, early involvement is critical. Identify key users, involve them during testing phases, and let them support broader user adoption. Many issues post go-live are due to lack of user readiness rather than system limitations.

    Regarding performance, most post-migration issues come from trying to replicate old AX designs instead of aligning with D365 architecture. Redesigning processes with the new system in mind makes a big difference.

    Teams like Dynamic Netsoft Technologies have been working with organizations on this transition by focusing more on transformation rather than just technical upgrade, which helps in achieving better long-term outcomes.

    Hope this gives you a clearer direction. Would be good to know how complex your current AX environment is.

Categories