ABS: modernise now or wait

When the fork appears

Bank’s ABS is 10-20 years old. Vendor support deteriorating. Every new product — weeks of integration. CFO sees cost ratio rising, CIO afraid of 36-month project with regulatory risk.

Critical replacement signs

Time to launch new product >90 days.

Vendor support losing specialists.

Integration with new systems requires custom adapter.

Reconciliation rates rising — ABS not keeping up.

Regulatory mandates (new tax, new reporting) trigger major change requests.

Operations downtime growing.

If 3-4 signs — ABS at a critical stage.

Strategies

Big bang — full switchover. High risk.

Greenfield + migration — parallel, phased. 24-30 months.

Strangle pattern — new ABS for new accounts, old legacy. 30-48 months.

Modular replacement — component by component. 36-60 months.

Wrap (without replacement) — modern API/event layer around. 6-12 months. Delays replacement.

When to modernise now

Critical signs present.

Strategic horizon 5+ years.

Operations leadership stable.

CFO commitment on CapEx ($30-100M) and double run cost during migration.

Parallel initiatives planned around ABS migration.

When to wait

Current ABS works functionally.

Another major migration is in flight.

Regulator preparing significant changes in next 12 months.

Financial situation does not allow double cost.

When to wrap

Business velocity bottleneck — but ABS is stable.

Capital constraints — wrap cheaper.

Want to buy time for better technology selection in 2-3 years.

What to discuss at the committee

What exactly blocks us in ABS (specific use cases).

Alternatives — wrap may solve 70% of the pain.

5-year TCO replacement vs status quo.

Migration risk assessment.

Vendor longlist + reference checks.

Related

• /en/architecture/banking-around-core-architecture/ — wrap strategy
• /en/insights/banking-core-modernization/ — core modernisation
• /en/decisions/banking-build-vs-buy-cdp/ — CDP decision
• /en/insights/banking-vendor-management/ — vendor