Data is the key to a successful implementation which can make the implementation as painless as possible for Customer to transition from their legacy systems to the new Dynamics AX application. The data gives them an unparalleled familiarity to use and embrace the new application even though they are in the midst of transition. The end users have nothing more joy in viewing the results in Reports or Inquiries with their data when they achieve their objective using AX Business Process. So Data Migration phase is an important area which needs to be planned and analyzed with importance right from the requirements stages with just the level of priority as the business processes.
Data migration requirements planning allows the Consultant to estimate and analyze the data maintained or archived in the legacy system. The data analysis estimation involves both size and quality of data that can be migrated to AX. Most importantly estimate the efforts required if there are complications and can be flagged early to the Customer. There are possibilities to pick up some functionality that may be required based on the data available in legacy but which has not been discussed or identified during the requirements workshops. Overall the effective Data migration strategy is crucial for getting the application ready for Training and UAT milestones. This in turn is the precursor signoffs for the Production cutover finalization and rollouts.
The workshops for data migration will involve all the key users spanning across modules but related business processes to ensure smooth decision making with consensus and settle any clarifications that may arise immediately. The workshops also allows the Consultant to identify who owns the data. For the session to be effective, key users may share their module data by showcasing reports, screenshots, etc ahead so Consultant can do a simple analysis and prepare any questions ahead of the data migration workshops. Based on the business requirement sessions conducted earlier, the Consultant should be able to identify and narrow down on the entities to be migrated and classify them as Configuration setup (Ledger accounts, GST, Payment terms, Module Parameters, etc), Master data (Customers, Vendors, Products, etc), Orders (Sales quotations, SO, PO etc) and Opening balances (FA, Ledger, Inventory, Cust/Vend, etc). Few more workshop sessions can be conducted in this format to ensure buy in from all the stakeholders and finalize the templates along with the conversion values required for AX.
Customers IT team or the key users will normally prepare a first round extraction as per the template provided for the entity along with the conversion values provided by the Consultant. There may be more extractions based on the feedback from consultant and the data migration templates will locked. Around the same time more planning will be done for firming up the dates for the real extraction for UAT based on the project schedule, considering if there are any other developments that is required for the data entity import. Generally an accepted 2 rounds of import is done to ensure the efficacy of the data and estimate timelines for the actual migration in production.
To summarize the data migration strategy, you would need to do;
Objectives
Stakeholders
Templates or Scripts
Simulate
The key ingredient for a successful and a smooth migration is adequate planning, proper understanding, and do it early! Now that we have got the strategy part over (my understanding J), let’s do some import to AX 7 using Data Entities!!!
Data migration requirements planning allows the Consultant to estimate and analyze the data maintained or archived in the legacy system. The data analysis estimation involves both size and quality of data that can be migrated to AX. Most importantly estimate the efforts required if there are complications and can be flagged early to the Customer. There are possibilities to pick up some functionality that may be required based on the data available in legacy but which has not been discussed or identified during the requirements workshops. Overall the effective Data migration strategy is crucial for getting the application ready for Training and UAT milestones. This in turn is the precursor signoffs for the Production cutover finalization and rollouts.
The workshops for data migration will involve all the key users spanning across modules but related business processes to ensure smooth decision making with consensus and settle any clarifications that may arise immediately. The workshops also allows the Consultant to identify who owns the data. For the session to be effective, key users may share their module data by showcasing reports, screenshots, etc ahead so Consultant can do a simple analysis and prepare any questions ahead of the data migration workshops. Based on the business requirement sessions conducted earlier, the Consultant should be able to identify and narrow down on the entities to be migrated and classify them as Configuration setup (Ledger accounts, GST, Payment terms, Module Parameters, etc), Master data (Customers, Vendors, Products, etc), Orders (Sales quotations, SO, PO etc) and Opening balances (FA, Ledger, Inventory, Cust/Vend, etc). Few more workshop sessions can be conducted in this format to ensure buy in from all the stakeholders and finalize the templates along with the conversion values required for AX.
Customers IT team or the key users will normally prepare a first round extraction as per the template provided for the entity along with the conversion values provided by the Consultant. There may be more extractions based on the feedback from consultant and the data migration templates will locked. Around the same time more planning will be done for firming up the dates for the real extraction for UAT based on the project schedule, considering if there are any other developments that is required for the data entity import. Generally an accepted 2 rounds of import is done to ensure the efficacy of the data and estimate timelines for the actual migration in production.
To summarize the data migration strategy, you would need to do;
Objectives
- Identify What to migrate, Source of data and How to migrate
- Classify and communicate clearly so there is no misunderstandings
- Ensure what’s in scope and out of scope
Stakeholders
- Key users who own their respective module data
- IT team who deliver the data as per template agreed
- Consultant who plans from strategy to execution
- Anyone else who is part of Sign off
Templates or Scripts
- Proper definition of what qualifies as a clean data expected for AX
- Columns with Legacy data conversion requirements to AX data
- Sign off both Migration strategy and Templates/Scripts
Simulate
- Ensure at least two rounds of testing including with Customizations, if any
- Sign off to ensure data imported is as per expected format
The key ingredient for a successful and a smooth migration is adequate planning, proper understanding, and do it early! Now that we have got the strategy part over (my understanding J), let’s do some import to AX 7 using Data Entities!!!
Disclaimer: Views expressed are entirely my own! please follow rigorous processes and project methodology for Actual Customer Implementations.
No comments:
Post a Comment