0 of 45 items completed 0%
Programme Initiation Board and executive approval obtained for the migration programme Programme sponsor and steering committee appointed Programme director and core team appointed with clear accountabilities Target operating model for the new core banking system defined Migration strategy selected (big bang, phased, parallel run, or strangler fig) Programme budget approved with contingency reserve Regulatory notification provided if required External programme assurance or advisory engagement confirmed
Data Preparation Full data inventory of the legacy system completed Data quality assessment completed — gaps and issues documented Data cleansing programme initiated for critical data issues Data mapping from legacy to target system completed and validated Data migration strategy approved (full migration, partial, or archive and migrate) Data migration tooling selected and configured Test migration completed and reconciliation results reviewed Data privacy and security controls for migration process confirmed
Integration & Interface Testing All integrations with the new core banking system identified and documented Integration architecture approved by Technology and Risk All integration points tested in a non-production environment End-to-end transaction testing completed across all product types Payment rails (SWIFT, SEPA, Faster Payments, etc.) tested and certified Regulatory reporting feeds tested and validated Third-party integrations (credit bureaus, fraud systems, etc.) tested Performance and load testing completed for peak volumes
Operational Readiness All staff trained on the new core banking system Operations runbooks updated for the new system Customer service team trained and ready for increased contact volumes Helpdesk and escalation procedures updated Reconciliation procedures for the migration period documented and tested Fraud monitoring rules configured and tested on the new system Business continuity plan updated to reflect the new system
Customer Communication Customer communication plan approved by Marketing, Legal, and Compliance Customer notification letters and emails prepared and approved Website and in-app notifications prepared FAQs for customers prepared and published Customer service team briefed on expected customer queries Communication schedule confirmed — timing relative to cutover
Cutover & Go-Live Cutover plan documented with minute-by-minute schedule Go/no-go criteria defined and agreed by the steering committee Rollback plan documented and tested War room established with all key teams available during cutover Regulator notified of cutover date and contingency arrangements Post-migration reconciliation completed and signed off System monitoring dashboards active and reviewed Post-migration review meeting scheduled within 48 hours of go-live