GAP Analysis: During the initial demonstration if there are variances highlighted by the prospect, time is spent and if required further meetings will be arranged to fully understand the detailed requirements. A detailed requirements document is produced to ensure that our interpretation of the requirement(s) have been accurately understood and sign off of is obtained.
Migration Process: A copy of the database will be obtained and analysed by our development team. Access to the GUI, where possible is preferable to confirm any assumptions made during this analysis process.
Once analysis has taken place a number of iterations of initial migration are carried out until IMVS is confident that the data is correct.
Data migration is a tailored process. Our process are iterative, the first iteration will require a high level of manual definition and during this process the code will be written to import data as per the prospects requirements. This code is then used to automate the subsequent iterations.
At this point IMVS will present the prospect with spreadsheets of static data to allow an element of data mapping and cleansing, if required. This may include all data or a subset of data defined specifically for testing. If a subset is used for the first migration, the second or third will include all data.
From the first iteration, our support and development team will be available, both during and after migration, to fix any inconsistent data.
Remote desktop facilities are particularly useful during this period as the data can be fixed directly within the database. If Remote desktop facilities are not available, data-fix scripts will be provided.
Typically, three iterations of migration will be performed, the third will be used for parallel running with a view to going live.
This will be extracted at noon on Friday and installed before noon on Monday.
The users will then parallel run on this data for the period of time that is agreed between IMVS and the prospect.
During this time, it is imperative that both databases are kept in sync and if no issues are found, the prospect will be able to go live on this data following parallel run.
If the APA database has not been updated with all transactions entered into the incumbent system, a decision will be made between both parties whether a further migration will be required.