Card Management System (CMS) Migration:
The Card Management system migration projects is one of the critical projects for any institutions or bank processors; as it involves the data which is extremely critical to banks and data migration is challenging in nature. Data migration is a prominent data-movement technique that is usually combined with other techniques.
The CMS migration includes the migration from legacy system to newer system, which includes data and other internal & external systems like Cards, Collections, Dispute, Statements, Embossing, PIN Mailer, HSM & keys, Payment Scheme and Authorizations etc.
What is CMS Migration Testing?
The CMS Migration Testing is a verification process of migration of the legacy CMS to the new CMS with minimal disruption/downtime, with data integrity and no loss of data (Data correctness), while ensuring that all the specified functional and non-functional aspects of the CMS are met post-migration.
CMS Migration testing includes
The regression testing is to perform testing with old data, new data or combination of the both, old features (unchanged features of CMS), and the new features of CMS, if any. The functional regression testing is to perform testing with newer data as per test cases defined by the testing team.
The mock testing is to perform testing with migrated data to perform data validation, data sampling and data reconciliation. The dress rehearsal testing is critical activity for CMS migration projects. This includes the migration from legacy to newer CMS along with data migration, HSM & key migration, other internal & external systems.
The Certification testing is to perform and validate the payment scheme (VISA & MasterCard) set of pre-defined test cases. The Performance testing is to determine how a system performs in terms of responsiveness and stability.
Designing the test strategy for migration include a set of activities to be performed and few aspects to be considered. This is to minimize the errors and risks that occur because of migration and to perform the migration testing effectively.
Critical Points for CMS migration:
Below are the critical points for CMS migration:
Why CMS Migration Testing?
The CMS migration to a new system could be for various reasons, system consolidation, obsolete technology, optimization or any other reasons.
While the existing legacy system in use needs to be migrated to a new CMS, it is essential to ensure the below points:
Example: downtime, loss of data, transactions declines etc.
Example: change in the functionality, removal of a particular functionality
In order to ensure a smooth migration of the CMS, it is essential to carry out Migration Testing.
Technically, it is also required to be executed for the below purposes:
Migration testing life cycle
Before migrating the data, set of testing activities are performed as a part of Pre-Migration test phase. The important activity is to create “migration strategy” document along with identified set of test scenarios, test plans and test cases.
Migration Strategy needs to be strictly followed to carry out the migration activity. Ideally, the migration activity begins with the data back up and conversion, so that, any time the legacy system can be restored.
This activity is extremely important and need to perform Mock runs for data sampling, data validation and data reconciliation with both legacy and newer CMS.
In addition, EOD validation need to be check with legacy and newer system to validate the accuracy of transaction amounts and statements.
Migration Test Summary Report
The test summary report should be produced after completing the migration testing and should cover the report on the summary of the various tests/scenarios carried out as part of various phases of migration with the result status (pass/fail) and the test logs.
Following activities need to be recorded during migration:
In addition to the above information, any observations /recommendations can also be reported.
During Post migration testing, perform out the functional testing with older and newer records in the CMS. In addition, data reconciliation and CMS end points with ESB middleware, Collections, Payment scheme’s and other internal system need to be checked. As this might have customer impact.