Like what you see? Discover the benefits of the D365UG/AXUG Community. Learn More
Our company also did not bring over detail history. We entered an ale to bring in one year of history for the prior year so that users could run budget vs actual reports for the prior year and could see comparison data during the first year after conversion. We are a county government and reply a lot on budgets and revenues reports, revenues by month etc. So we also created a custom table that housed the revenues and expense information for five years of historical data. We used Atlas to read this table and created some reports for this comparative data. Management Reporter may well do the same thing. We will keep our legacy system up and running to maintain our required five year history, but have found we rarely need to go back.
Migrating data from Legacy system is subjective, time consuming and need good strategy to overcome hurdles later in the game.
If you have an AX system which is already in use you might have archival process in place (say x years) then it is safe to migrate same years of data.
Assuming you are implementing AX newly, your company has no prior experience in AX and have an implementation partner you might have to decide on your archival period (say 3 or 4 years) and migrate that much amount of data. This will help you in load and performance testing as you are mimicking your system as 3/4 years old with respect to amount of data.
Bottom-line is you must decide on archival period based on your business requirements, auditing needs to know how old data you need and plan your data migration.
Site designed by Brightfind
Powered by Cobalt xRM and Higher Logic