Move the core over one weekend nobody notices.
A core banking migration proposal for Pell & Ward Bank, from Ledgerline.
Four sentences from September, reconciled.
Each of you gave us one line in the discovery sessions. We've set our answer against each one the way your finance team closes a month. Nothing on this page is left unmatched.
If a customer notices, we've failed. If the press notices, I've failed.Helen, Chief Executive
Zero minutes offline. Cards, the app and ATMs stay up all weekend, and 35 percent of our fee is only paid when we call go.
MatchedMy team has kept this core alive for 26 years. They need to be in the room, running it.Tobias, Chief Information Officer
31 of your people hold named roles on the weekend rota. They run all four rehearsals with us first, so by May they've done the weekend four times.
MatchedI want to be able to stop it at any point and know where we'd be.Priya, Chief Risk Officer
Seven checkpoints. You can call a hold at any of them without giving a reason, and the rollback point is printed beside each one.
MatchedSunday afternoon is when people check their balance before the week. That screen has to look like every other Sunday.Marcus, Head of Customer
The app reads from a live mirror of your current core until Monday morning. Sunday's balance is the same number in the same place.
MatchedRun the weekend before you sign.
This is the cutover plan for Saturday 22 May 2027, hour by hour. Drag the clock and watch 1.4M accounts move in five waves, each one reconciled to the cent before the next starts. Then break it on purpose.
RUNNING NOW
Freeze the old core and seal the snapshot.
Wave 0 of 5
WHAT CUSTOMERS SEE
- Card paymentsOld core
- App and onlineOld core
- ATMsOld core
- Approved so far0
MINUTES OFFLINE
Rehearse a hold. Pick a checkpoint and its reconciliation fails. One hold costs 75 minutes and we still go. A second hold in the same weekend means no-go, whatever the clock says, and the old core is back serving before branches open.
By May, your team has done this four times.
Each dress rehearsal runs the whole weekend on a full copy of your data, against the clock, with the same people on the same shifts. These are the run times we plan each one to hit, from our last nine migrations.
Four rehearsals bring the run to go or no-go down to 26 hours. That leaves five hours of buffer inside the window, almost twice what a full rollback needs.
Rehearsal results go to Priya and your regulator the Monday after each one, with every mismatch we found and who fixed it.
Four people sign. Each has one question.
Every chapter below answers one of you, in the words you used, so nobody needs a call to get to yes.
Will anyone outside this building know it happened?
Helen, Chief Executive
How does it run, and what do my people do that weekend?
Tobias, Chief Information Officer
What must be true at each checkpoint, and who can stop it?
Priya, Chief Risk Officer
What do customers see, and what do my teams say?
Marcus, Head of Customer
Will anyone outside this building know it happened?
That's the share of our fee Ledgerline is only paid when we call go at the end of the weekend. If we call no-go, it waits, and the next attempt costs Pell & Ward nothing.
The worst weekend, played out.
Two reconciliations fail. We call no-go on Sunday, switch every channel back to your current core and finish by Monday 05:40, before a single branch opens. Customers bank as usual. The papers have nothing to write.
Then we go again on 5 June at our cost. The one weekend we've ever called no-go went this way, and that bank went live a fortnight later.
How does it run, and what do my people do that weekend?
Every channel keeps a home all weekend. Pick a moment and see where each one is served from.
The weekend rota
Your engineers own the old core's freeze, the snapshot and the rollback switch. Nobody on our side touches them. Every checkpoint has one of yours and one of ours signing it off together.
What must be true at each checkpoint, and who can stop it?
T1Every balance matches to the cent+
T2General ledger totals match by product+
T3Accrued interest matches+
T4Card holds and pending items carried+
T5No rejected record without an owner+
T6Weekend payments replay cleanly+
Three people can call a hold.
- PRPriya, Chief Risk Officer
- TOTobias, Chief Information Officer
- JOJoanna, Ledgerline cutover lead
Any one of them can stop the weekend with one word. Nobody needs to explain why until Monday. A hold freezes the current wave, backs out its last batch and reruns it. Every checkpoint card in the console shows the point we'd roll back to.
Your regulator gets 60 days' notice of the date, the evidence pack from each rehearsal, and a call from Priya at go or no-go.
What do customers see, and what do my teams say?
What stays the same for every customer
- Account and routing numbersUnchanged
- Debit cards and PINsUnchanged
- Saved payees and transfersUnchanged
- Direct deposits and autopayUnchanged
- App login and face IDUnchanged
- Statement layoutUnchanged until you choose
Contact centre staffing on Sunday 08:00 to 20:00 and Monday 08:00 to 12:00, with one script your team writes and we rehearse with them in April.
We don't email customers in advance. Nothing they use changes, and a warning creates the calls it's meant to prevent. Branch staff get a one-page brief on Friday 21 May and a Monday 07:00 huddle.
One fixed price, line by line.
The licence and the migration are the same in every version of this. Everything below them can come down on its own, and each line says what you'd give up.
Ledgerline core licence, five years
The core for 1.4M accounts and 212 products, hosted in two regions, upgrades included.
Migration and the cutover weekend
Data mapping, the five waves, the 46-person rota, the stand-in for cards and the live mirror for the app.
Dress rehearsals
$310,000 each. A full weekend on a copy of your data with the live rota.
Parallel run
$185,000 a week. Both cores process every day after go, and we reconcile them each night.
Extended hypercare
Our cutover team stays on your floor for 90 days after go instead of 30.
Cutover command on site
Our 46 people work the weekend from your operations centre on Harbour Street.
We'd sign it as it opens. Four rehearsals is what gets the run to 26 hours, and six weeks of parallel run is the shortest that carries your first quarter-end on both cores. If something has to come out, take the on-site command first. It's the line that costs you least in risk.
December to August, with one weekend in the middle.
The plan moves with the price above. Change the parallel run or hypercare and the bars here follow.
The four people in the room that weekend.
They lead the rehearsals, the weekend and the parallel run. None of them hands over to anyone else once you've signed.
Joanna
Cutover lead
Runs the clock and calls go with Priya and Tobias. Ran the no-go weekend in 2024 and the clean one a fortnight later.
7 cutovers led
Dev
Data migration lead
Owns the mapping of your 212 products and the five waves. Starts with your data team on 11 January.
9 migrations, 11.2M accounts
Ruth
Risk and controls lead
Writes the six tests with Priya's team and builds the evidence pack your regulator receives after each rehearsal.
Former bank examiner, 12 years
Sam
Customer operations lead
Works with Marcus on the contact centre script, the branch brief and the Monday 07:00 huddle.
4 cutovers, 0 complaint spikes
The terms, plainly.
What can change the fixed price
If we call no-go
Your data
The licence after year five
Your current core
What we don't know yet.
- Will your examiner want 90 days' notice?We've planned on 60. At 90, signing needs to move to 20 November or the cutover moves to 5 June.
- What stand-in limit will your card network allow?We've assumed $2,500 a day per card over the weekend. A lower limit means a lower ATM cash limit that Sunday, and Marcus's script would need to say so.
- Who cleans the 3,140 addresses we couldn't parse?They showed up in the sample you shared. They need an owner on your side before rehearsal two.
- Is 22 May clear of your own calendar?We've checked for month-ends and holidays. We haven't seen your marketing or rate-change plans.
Sign by 4 December and rehearsal one is 13 March.
After that date the March slot goes to another bank and every date on this page moves back three weeks, including the cutover.
- 4 DecSignatures from Helen, Tobias, Priya and Marcus
- 11 JanDev and your data team start mapping
- 13 MarRehearsal one, the full weekend on a copy
- 22 MayCutover, Saturday 23:00