Our experience over the last 25 years regarding to Data migration in aviation varies and is dependent very much on the needs of the customer. We have been on site in a purely consultant’s capacity help to answer AMOS questions and overview of migration, to migrating data produced by third parties to construction, extraction and migration of MRO data. CrossConsense has in depth knowledge of the AMOS database, its usage and engineering and logistics background. In addition to the plausibility checks provided by the AMOS software we are using our own business intelligence software in order to get the data quality as good as possible. And with the support of our consulting expertise we always know which steps to take next when it comes to data migration.
We gained a lot of experience in data migration from older AMOS versions to newer ones as well in migrating data from one MRO system into another (e.g. from Trax, Oases, Amasis and others to AMOS or vice versa).
Each migration project is different but a high level timeline from a data migration perspective only would be:
Construction of data extract scripts.
The timeline for this will depend on the knowledge of the legacy database. With little or no knowledge we calculate 5-7 months for the complete process of data migration.
Data migration cycles.
The number will depend upon the quality of the data. The time between cycles should ideally be 6 weeks. This takes into account time to migrate the data, time for the business to verify the data and feedback issues and time for re-writing of scripts.
Dry run for go live.
This checks the final timings for migration so that the business can judge the down time of both systems.
Go live migration.