4.5 Recommendations before moving to FDT stage

This topic provides information on the Recommendations before proceeding to FDT stage

Below are the recommendations to facilitate a systemic and coordinated migration involving multiple Migration Events.

• If there are multiple migrations applicable, like Account Migration, Financial Migration etc, then all the individual migrations must be run one after the other for the same set of Account numbers.
• For example, if Account Migration Stage I and II is run for Account numbers A1 to A100, then Financial migration Stage I and II also has to be run for the same set of account numbers A1 to A100.
• File naming conventions can be followed by including a label or version prefix to the file name corresponding to the set of accounts that are getting migrated. And same label/version prefix can be used for all related Migration Event files for the same set. This will facilitate easy reconciliation.
• It is recommended that Stage I and II must be executed in iteration as applicable for each set of account numbers as mentioned above for all the Migration Events as applicable.
• The above iteration must continue until data for all Account sets are exhausted across all applicable Migration Events.
• It is recommended to go through the dashboard and make sure that all records that went into error across migrations are corrected successfully in these iterations.
• Only after the above steps, the Migration Stage II should be submitted with PROCEED outcome to go to FDT Approval stage.
• FDT stage can be executed only once and hence it is imperative to check the consistency of all data that is migrated so far prior to this stage.
• In case of errors in any of the migrations, it is recommended to correct these errors, re attempt the failed migrations and make the state as 100 percent successful and then arrive at the FDT Approval Stage.