Core banking migration: rehearsals, reconciliation and go / no-go gates

A core banking migration ends with one weekend when customer data moves for good. How calm that weekend is depends on the months before it: how many times the migration was rehearsed at full volume, how completely the result was reconciled, and whether every decision on the night was written down in advance.

Why migration weekends go wrong

Difficult cutovers tend to share the same causes, and each one is visible well before the weekend:

  • mappings kept in spreadsheets that drift away from the code that actually runs;
  • scripts tested on small extracts that meet full volumes and real data quality for the first time on the night;
  • reconciliation by sample and a few totals, so differences surface after go-live as customer complaints;
  • a rollback plan that exists on paper but has never been run or timed;
  • go / no-go decisions taken by whoever is still awake, against criteria nobody agreed beforehand.

Each is avoidable with planning and discipline that cost far less than a bad first business day.

Know exactly what you are moving

Write the scope in business terms, and include the data that is easy to forget. Customers, accounts, balances and financing contracts with their profit schedules are obvious. These are harder to remember and harder to get right:

  • holds and blocks, including those placed under enforcement orders, which must carry over exactly (see automating Tanfeeth enforcement orders);
  • standing orders, direct debit mandates and saved SADAD billers;
  • saved beneficiaries for SARIE and IPS transfers;
  • links between mada cards and the accounts behind them;
  • identity and address data, including national ID or Iqama details and the National Address;
  • dormant accounts, closed accounts with history, and the records you are required to retain.

IBANs deserve particular care. Customers have given them to employers, billers and government services, so they should not change. Validate every one against its ISO 13616 check digits in each rehearsal, and treat any change as a defect.

Interfaces move with the core

The core is rarely migrated on its own. Channels, the payment hub, cards, the enforcement channel, regulatory reporting and many internal systems all connect to it, and each interface needs a decision: repoint, rebuild or retire. Banks that already route these connections through an integration layer have an easier weekend, because repointing becomes a routing change. Banks with many point-to-point links tend to discover how many they have during the migration. Our note on retiring point-to-point integrations covers how to build that inventory first.

Instant payments add a constraint that older migration plans did not have. IPS does not stop for your weekend, so the plan must say how incoming instant payments are handled while the core is unavailable, how they are applied when it returns, and what customers are told. Agree the approach with the scheme early. Our note on what IPS changes for bank operations covers the wider picture.

Rehearse until the numbers agree

A rehearsal is a complete run of the migration, end to end, at full volume, on a production-shaped copy with personal data masked under your policy and the PDPL. Small-extract tests help to build mappings, but they say little about timing or real data quality.

A typical program plans three to five full rehearsals. Each one should:

  • use the same pipeline, scripts and runbook that will run on the night;
  • be timed step by step against the window available, including reconciliation and sign-off;
  • quarantine every rejected record with a reason code, and track rejects from one rehearsal to the next;
  • end with a written list of defects, each with an owner and a date.

Treat the final rehearsal as a dress rehearsal: the same people, the same hours and the same sequence, including the go / no-go meetings and a full rollback. If the plan fits the window only when everything goes right, it does not fit.

Reconcile every record and explain every difference

Sample checks are the most common weakness in migration sign-off. Reconciliation should run at three levels:

  • Control totals for each entity and product: record counts, balance totals, accrued profit and key hashes, agreed between source and target.
  • Row level: every customer, account, balance and financing record compared field by field, keyed on a cross-reference from legacy to new identifiers.
  • General ledger: the target ledger agrees with the source to the halala, by product and branch.

Every difference needs an explanation and an owner before sign-off. Accepting a difference as within tolerance is a business decision, recorded with the name of the person who made it. Sign-off belongs to the business owner of each data area, with finance and internal audit able to see the evidence behind it.

Write the gates before the weekend

A go / no-go gate is a point in the plan where a named person decides whether to continue, against criteria written in advance. Most migrations need at least these:

  1. Readiness gate, a week or more before: rehearsal results within the window, no open critical defects, readiness signed off by each team, and customer communications ready.
  2. Go / no-go 1, after the freeze and extract: source totals captured, legacy systems quiet, and interfaces stopped as planned.
  3. Go / no-go 2, after load and reconciliation: control totals and ledger agree, exceptions are explained, and smoke tests have passed on the target.
  4. Point of no return: the time after which rolling back would cost more than fixing forward. Set it in advance as a clock time, and make sure a full rollback still fits before it.
  5. Customers back: channels reopened in a planned order, with monitoring in place.

Name the decision owner for each gate, usually the COO or the program sponsor. Keep the criteria short enough to read aloud in a meeting at 03:00, and record each decision with the evidence behind it.

Rehearse the rollback

A rollback that has never been run cannot be relied on. Run it during rehearsals, time it, and confirm that the legacy system can resume with no lost transactions. Decide in advance how any transactions captured on the new platform before a rollback would be replayed onto the old one, and who would check them.

Choose the weekend with care

In Saudi Arabia the weekend is Friday and Saturday, so the first full test of the new core is Sunday morning. Keep the migration away from month-end, salary days, quarter-end regulatory reporting, Ramadan and the Eid holidays, and any seasonal peak your customers depend on. Confirm early what notice SAMA expects for a change of this size, and build that lead time into the plan.

Plan hypercare through the first month-end

The first end-of-day run, the first profit accrual, the first statements and the first month-end each exercise paths that rehearsals could only simulate. Keep hypercare in place until then: a war room with business and technology leads, a daily defect review, extra contact center capacity, and an operations view of every customer service against its normal behavior.

OpsCommand gives the operations team that single view during hypercare, and NotifyHub can carry planned-downtime and service messages to customers, in Arabic and English, before and after the weekend.

What to do next

  1. Write the scope in business terms. Include holds, mandates, beneficiaries, card links, identity data and history.
  2. Build the interface inventory. Decide for each interface whether to repoint, rebuild or retire it.
  3. Put mappings under version control. Link every mapping and rule to the pipeline that runs it, with approval before each change.
  4. Schedule full-volume rehearsals. Use masked, production-shaped data and time every step.
  5. Agree reconciliation and sign-off. Set the three levels, the tolerances and the business owner for each data area.
  6. Write the gates. Set the criteria, the decision owners and the point of no return.
  7. Run the rollback. Time it at least once, end to end, before the weekend.

If a core migration is on your roadmap, book an executive briefing. We will review your plan, rehearsal approach and gate criteria, and give you a written view of the risks to close before you choose a weekend.