Continuing my previous post on building migration utility, this post is going to be on the first phase of migration tool approach i.e. System Assessment. During System Assessment the following queries need to be answered:

  • What are the key customer requirements in terms of functionality when migrating between source and target?
  • What are the module differences between the source and target?
  • What are the functionality changes within the common modules?
  • What type of data do the source and target support?
  • What are basic input / output types, interface points in the different systems?
  • What are the external dependencies?
  • Do the products handled legacy file formats and / or high value transactions?
  • Have the customers customized their source system? If yes to what extent? Can the target system handle the customization without any customization?
  • What is the historical data requirement? This will be required to run reports.
  • Will the migration extend to data for Add-on modules?
  • What is the hardware support difference between the systems?

This query list is just a macro level view of the hundreds of questions that will rise during System Assessment. The end result of the System Assessment will be a defined ‘Scope document’. The scope document becomes crucial in migration tool building because during the actual implementation there is a huge possibility for scope creep. Once the scope is defined the stage is all set for Data Assessment & Mapping. More in the next post.