Merger Due Diligence Should Show the Cost of Running Two Banks at Once

A practical weekly article for community bank and credit union boards and senior leaders on merger and core-conversion due diligence, with emphasis on the temporary operating mo...

A merger deck gets dangerous when the technology section sounds too tidy.

The strategic logic is usually clear enough. More scale. Better market coverage. Expense saves. Stronger product mix. Maybe a cleaner path to growth.

Then you get to the integration assumptions and the slide starts lying by omission.

One core becomes another. Data moves. Channels align. Teams standardize. Customers and members adapt. Synergies show up.

That is the fairy tale version.

The real version is messier. For a while, the institution is often running two operating models at the same time. Two sets of workflows. Two exception paths. Two versions of where the data lives.

That period is where merger technology risk actually lives.

For community banks and credit unions, that matters because there is not much spare capacity hiding in the organization. Jack Henry's 2025 Strategy Benchmark found that 76 percent of financial institutions planned to increase technology spending in 2025 and 2026, while 54 percent of bank CEOs named efficiency as a top strategic priority. At the same time, BNY's 2025 Voice of Community Banks Survey found that more than 80 percent of small business clients experienced at least one operational inefficiency with their community bank. Read those together and the pressure becomes obvious.

That is why merger due diligence has to get more honest about conversion strain.

Most merger packets are better at explaining the destination than the ugly middle

Boards usually see the target state. One platform set. One customer experience. One vendor map. One operating model. That is useful.

What they often do not see clearly enough is the cost of living in between.

Which deposit operations tasks get slower before they get cleaner? Which lending workflows stay half manual while data fields are reconciled? Which digital servicing paths create confusion because customers or members are crossing from one institution's logic into another's? Which reports lose trust for a quarter because definitions changed faster than governance did? Which access rights, exception queues, and reconciliation steps multiply while leadership is still talking about simplification?

Those are not side issues. They are the work.

If the board approves the deal economics without seeing that temporary operating model in plain English, then the institution is not really governing the integration. It is hoping the integration team can absorb the strain quietly.

Example one: PeoplesBank showed what discipline looks like before the broader conversion

One useful public example comes from PeoplesBank in Massachusetts. According to a 2025 FinXTech case study, leadership did not bet the whole institution first. The bank launched ZYNLO Bank on a newer technology stack before moving the broader institution.

Boards should notice the sequencing discipline.

Leadership created a smaller environment to learn where the process friction lived, what the new platform changed, and how operating assumptions held up under real use. That is a much better governance posture than approving a giant integration plan built mostly on optimism.

In merger terms, the lesson is simple. If management cannot test the most fragile assumptions in a contained way, the board should be much more skeptical about forecasts that depend on smooth enterprise-wide conversion.

Example two: TSB showed how fully funded change can still fail as governance

TSB's 2018 migration failure is still one of the clearest warnings for any board treating conversion as a straightforward technology project. Customers were locked out. Payments were disrupted. Service broke down publicly. In 2022, the U.K. Financial Conduct Authority and Prudential Regulation Authority fined TSB £48.65 million for operational risk management and governance failings tied to the migration.

The failure was not that someone forgot to buy technology. The failure was governance around readiness, execution, and consequence.

A board packet can have a budget, a timeline, and a happy-path plan and still be dangerously incomplete if it does not surface the period when the institution is carrying duplicate processes, unstable handoffs, and concentrated operational knowledge.

Community institutions do not need TSB's scale to learn from that. The same pattern can hurt a smaller bank or credit union faster because there are fewer people available to absorb conversion friction when reality starts missing the slide deck.

Synergy is easy to model. Conversion drag is not. That is why the board has to force it into the room.

Merger math usually celebrates what gets removed. Duplicate vendors. Duplicate leadership roles. Duplicate systems. Duplicate real estate. Fine.

But during the transition, the institution often pays for overlap before it earns simplification.

Parallel contracts may stay alive longer than planned. Operations teams may work around field mismatches and account mapping issues. Branch and call center staff may carry customer confusion that never shows up as a line item in the integration budget. Compliance and risk teams may spend months proving that reports from the new combined environment actually mean what leaders think they mean.

It is not a reason to avoid deals. It is a reason to govern them like adults.

A merger becomes dangerous when leadership presents the drag as a short technical bridge instead of what it usually is: a temporary operating model with real service, control, labor, and decision-quality consequences.

What I would want in the packet before approving the next merger step

If I were sitting in the boardroom, I would want five things in plain English before management asked for another approval.

1. The list of workflows that get harder before they get better

Not every process. The critical ones.

Account opening. Loan boarding. Treasury or cash management servicing. Fraud review. Dispute handling. Statement production. General ledger reconciliation. Exception processing.

Which of those will become more manual, slower, or more error-prone during integration, and for how long?

2. The period when the institution is effectively running two banks at once

How long will core data, channels, reporting, and customer support logic remain split across old and new environments?

This is not just a technology timeline. It is an operating risk timeline.

3. The concentration risk hidden inside the conversion

Which steps only a few people understand? Which reconciliation tasks depend on institutional memory? Which vendor assumptions are carrying too much weight? Which team becomes the human middleware when systems disagree?

Community institutions especially cannot afford to discover during week three of conversion fallout that resilience was really just one experienced operator and a heroic spreadsheet.

4. The service impact thresholds that would force executive escalation

At what point does backlog, error rate, abandoned account opening, delayed funding, call volume, or unresolved exception count become a board issue?

If those triggers are not defined before the next approval vote, the institution is leaving itself room to normalize deterioration.

5. The no-kidding cleanup plan

What temporary reports, duplicate systems, side reconciliations, and manual rescue steps must die after stabilization?

If leadership cannot name what gets retired, then the merger is at risk of becoming permanent complexity disguised as integration progress.

The board's job is not to become an integration office

Directors do not need to choose the platform sequence or approve the field mapping.

They do need to force sharper honesty.

That means asking whether the economics still make sense after adding conversion drag. It means asking whether management has named the operating model instead of pretending it does not exist. It means asking whether customer and member friction is being measured where it actually shows up, not just where the project dashboard is easiest to color green.

Merger due diligence should not be anti-growth. It should be anti-fantasy.

If the packet only works in the upside case, it is not diligence. It is storytelling.

The institutions that handle this well are not the ones with the prettiest strategy decks. They are the ones willing to say, out loud, where the integration will hurt before it helps and what leadership will do about it.

That is governance.

And in a community bank or credit union, that honesty is often the difference between a hard integration and a damaging one.

Discussion questions

1. Which workflow in a merger would create the most hidden customer or member friction if your institution had to run two operating models for six months? 2. What conversion assumption in your current merger or core strategy would you want forced into plain numbers before the next board vote? 3. Where is your institution most likely to normalize temporary complexity instead of retiring it?

Sources

• Jack Henry, 2025 Strategy Benchmark
• BNY, Voice of Community Banks Survey 2025
• FinXTech, "Lessons From a Community Bank's Core Conversion," October 7, 2025
• U.K. Financial Conduct Authority and Prudential Regulation Authority, final notices regarding TSB Bank plc migration-related operational risk and governance failings, 2022
• FFIEC IT Examination Handbook, Architecture, Infrastructure, and Operations booklet