web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Supply Chain Management forum

Best practice for migrating from Legacy system to Dynamics

(0) ShareShare
ReportReport
Posted on by 332

Hello,

Does anyone have tips / can refer me to  a good post on best practice when moving from a Legacy system to Dynamics AX/ 365?

I'm looking to read more about what types of rules to follow when bringing in vendors etc. with old number series to new.

What are pros and cons of establishing the same number series / intelligent number series in the new system?  what do we gain if we make the number series automatic in new system?

This is just an example. What other things should be consider as best practice when migrating into Dynamics world?

 

Thanks!

Loku

I have the same question (0)
  • Suggested answer
    Siv Sagar Profile Picture
    5,268 Super User 2025 Season 2 on at

    Hi

    When migrating from a legacy system to Dynamics 365 Finance and Operations (formerly known as Dynamics AX), it is important to follow best practices to ensure a smooth transition. Here are some suggestions:

    Assess your current system: Start by understanding the functionality and data structure of your legacy system. Identify the critical business processes and data that need to be migrated to Dynamics 365.

    Engage stakeholders: Involve key stakeholders from different departments in the planning process. This ensures that their requirements are considered, and they are invested in the success of the migration.

    Develop a migration strategy: Create a comprehensive migration strategy that outlines the scope, timelines, and resources required for the project. Consider factors such as data migration, system configuration, integration with other systems, and user training.

    Cleanse and validate data: Before migrating data, clean and validate it to ensure accuracy and completeness. Eliminate duplicate, obsolete, and irrelevant data. Data cleansing can help prevent issues and ensure a smooth transition.

    Plan for customizations and integrations: Identify any customizations or integrations in your legacy system and evaluate their relevance in Dynamics 365. Determine if they can be replaced by out-of-the-box features or require reimplementation. Plan and prioritize these modifications accordingly.

    Test thoroughly: Create a test environment to validate the migration process. Test data migration, business processes, customizations, integrations, and reporting to ensure everything works as expected. Engage end-users in user acceptance testing (UAT) to gather feedback and address any issues.

    Develop a training plan: Prepare a comprehensive training plan to ensure that users are familiar with the new system. Provide training sessions, user guides, and documentation to help them understand the features and functionalities of Dynamics 365.

    Execute a phased approach: Consider adopting a phased migration approach to minimize disruption. Start with a pilot group or a smaller set of functionalities before rolling out to the entire organization. This allows for learning and adjustments along the way.

    Monitor and optimize: After the migration, closely monitor the system's performance and address any post-migration issues promptly. Continuously optimize the system based on user feedback and evolving business requirements.

    Engage with an experienced partner: Working with a Microsoft-certified implementation partner or a Dynamics 365 expert can greatly help in ensuring a successful migration. They have the knowledge, experience, and tools to guide you through the process and mitigate risks.

    Remember that every organization's migration journey may vary based on its specific needs and complexities. Following these best practices will help you navigate the migration process more effectively and achieve a successful transition to Dynamics 365 Finance and Operations.

    Best regards,

    Siv Sagar

    This post is my own opinion and does not necessarily reflect the opinion or view of my company.

    Please mark as verified if the answer is helpful. Welcome to join hot discussions in Dynamics 365 Forums.

  • André Arnaud de Calavon Profile Picture
    300,911 Super User 2025 Season 2 on at

    Hi Loku,

    The reply from Siv illustrates that sharing best practices is not something that can be easily shared on a forum. I would recommend engaging with an experienced partner that is able to listen to your requirements and guide you what would be the best for your implementation.

    Looking at your example, using old number or new ones, manual of automatic numbering depends on several details from your organization which we can't guess.

  • Suggested answer
    Hana Xue Profile Picture
    Microsoft Employee on at

    Hi Indiguna,

    I found related documentation on data migration and the tools needed for data migration.

    Hope these will be helpful!

    Legacy system to Dynamics - CRM Software Blog | Dynamics 365

    The Simplified Guide to Dynamics 365 Data Integration and Migration (crmsoftwareblog.com)

    AX 2009 upgrade - Use the Data migration tool to migrate from Dynamics AX 2009 to finance and operations - Finance & Operations | Dynamics 365 | Microsoft Learn

    AX 2009 migration - Install the Data migration tool - Finance & Operations | Dynamics 365 | Microsoft Learn

    Best Regards,

    Hana

    This post is my own opinion and does not necessarily reflect the opinion or view of my company.

    Please mark as verified if the answer is helpful. Welcome to join hot discussions in Dynamics 365 Forums.

  • PT-22040759-0 Profile Picture
    5 on at

    Hello!

    In addition to everything mentioned above, I would recommend applying to the SMA program from Microsoft (link: learn.microsoft.com/.../standard-migration-assessment). It can address a significant portion of your inquiries and preparatory work by granting access to migration professionals. The program is funded by Microsoft and provided to clients free of charge.

    If you have any questions regarding the program, I would be happy to assist you.

  • Bill Ngo Profile Picture
    372 on at

    Hi Loku,

    Through some projects, I would like to share some experiences when moving from a Legacy system to Dynamics AX/ 365 (New). If there is anything wrong or missing, please add more.

    1. In the same number series between the Legacy system to the New. There are two cases to be considered:

    - If your old number series does not match with the prefix of sequence number, then you need to make the number series manual in the New.

    - If your old number series does match with the prefix of sequence number of the New, you can make the number series automatic in the New. Ex: VHKD_00001 (VHKD is prefix, 00001 is increasing sequence number #####)

    Pros:

     - Easily migrate data from old system to New.

     - No need to do the work of converting old code to the New.

     - Users can easily manipulate and familiarize themselves with the old code when working in the New.

     - Automatic code generation can be applied on the system if the old code can be split according to the principle of obtaining prefix codes.

     - If the frequency of generating new codes is not much, manual creation is the most effective method.

    Cons:

     - When users create new code in a manual way. It can be easy to create errors due to duplicated, or mistyped code.

     - Sorting/indexing old code can be difficult to retrieve.

     - An important point is that: If the frequency of generating new codes is a many every day/week, you should not apply the number series manual method.

    2. Intelligent number series in the new system: Intelligent number series depends on the built-in functions of sequence number in the New.

    You can utilize the advantages of the sequence number and set up the rule to meet these requirements. There are two types of rules for generating sequence number:

    - Manual: the user must manually enter the data to generate the code, you can set up a rule to control when creating the new code in your specified way.

    - Automatic: the system will automatically generate a new code according to the incrementing number and pre-set way in the sequence number. There are 2 ways for you to choose whether the number of consecutive jumps or the number of breaks is allowed.

    Pros:

     - Again: If the frequency of generating new codes is a many every day/week, the number series automatic method is a great advantage.

     - Avoid users creating new code in the wrong way.

     - Sorting/indexing old code can be easy to retrieve.

    Cons:

     - Take time to convert the old code to the new when migrating data.

     - Some time users required a referenced old code in the New.

     - Users take time to manipulate and family with the new code in the New.

     - We might have to utilize existing fields in the New such as Group/category to cover old code (if have).

    Note: the length of these code fields is usually 20 characters (Alphanumeric format).

    I hope what I have shared above will be of help to you.

    Kind regards,

    Bill

    This post is my own opinion and does not necessarily reflect the opinion or view of my company.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

November Spotlight Star - Khushbu Rajvi

Congratulations to a top community star!

Forum Structure Changes Coming on 11/8!

In our never-ending quest to help the Dynamics 365 Community members get answers faster …

Dynamics 365 Community Platform update – Oct 28

Welcome to the next edition of the Community Platform Update. This is a status …

Leaderboard > Supply Chain Management

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans