Point of view · Banking transformation

Banking Conversion 101

The problem, the landscape, and the technical and human architecture behind a successful conversion.

ASSIGNMENTFull conversion
WINDOW83 hours
LINES OF BUSINESS4 interconnected
DISCIPLINESArchitecture + human-centered change
01

The situation

You own the architecture and delivery of a large banking conversion. Where do you begin?

The assignment is to build a strategy, recognize architectural anti-patterns, and account for the operational realities of financial-services vendors.

The acquired firm must move onto the purchaser’s platforms across retail deposits and lending, commercial banking, wealth, and capital markets. Each line of business depends on services and data provided by the others, so the conversion cannot be planned as a collection of isolated migrations.

02

Conversion parameters

The weekend is short. The dependency chain is not.

01

Full conversion

Move from the acquired firm’s platforms to the purchaser’s systems—not a long-term lift and shift.

02

Early conversion

Move selected vendors earlier when coordination complexity or known anti-patterns create unacceptable risk.

03

Pre-staging

Stage data before the event when extraction and transformation processes cannot meet the conversion window.

04

LoB linkages

Sequence around services each line of business provides to the others, not just around individual applications.

03

The system landscape

Start by identifying what each system owns.

A useful conversion model separates systems by the records they control, the services they provide, and the identifiers that connect them.

01

Product systems

Financial product platforms that create account numbers and maintain balances, collateral, schedules, and available funds.

  • Network-based products connect to real-time networks such as Visa and Mastercard. Credit card and brokerage platforms often maintain the account number and balance.
  • Aggregate loan booking platforms maintain retail and commercial loans, collateral, balances, and payment schedules.
  • Specialized product systems may be internally maintained or vendor platforms with one operational instance and one authoritative copy of data.
02

Customer systems

Platforms that connect customers to accounts, rights, risk, and regulatory attributes.

  • Aggregate customer-account systems provide a unified customer view and represent legal or technology entitlements.
  • Master data management supports privacy, KYC, AML, and extensible customer attributes.
  • Risk relationship systems identify connected customers and aggregate exposure, especially in commercial banking.
03

Data and enterprise systems

Shared infrastructure that supplies reporting, documents, identities, integrations, and day-two processing.

  • Data warehouses and reporting platforms
  • Enterprise service buses and integration layers
  • Document management and identity platforms
04

Channels and money movement

Customer-facing channels and transaction services that rely on identifiers from multiple systems of record.

  • Online, mobile, call center, branch, ATM, and embedded channels
  • Zelle, bill pay, account transfer, ACH, wire, and card services
  • Payment schedules, nicknames, proxies, recipients, and transaction history

The landscape

See the entire conversion surface.

The banking reference landscape makes the scope visible across customer channels, shared services, systems of record, and day-two operations.

Click the diagram to inspect the original.

The human side of conversion

The systems move in 83 hours. People carry the change long after.

A conversion plan must account for the customers, employees, operators, risk partners, and vendors who experience the cutover—not only the applications and records being moved.

01 / REDUCE ANXIETY

Make the cutover understandable.

Clarify what changes, what remains available, when service is interrupted, where customers and employees can get help, and how exceptions will be resolved.

02 / PARTICIPATORY PLANNING

Build the schedule with the people who operate it.

Bring frontline, call-center, operations, risk, technology, and vendor teams into scenario reviews so hidden dependencies appear before the conversion window.

03 / REMOVE BURDEN

Design out rework and manual recovery.

Use dependency sequencing, clear ownership, rehearsed decisions, and visible escalation paths to reduce avoidable support volume, duplicate work, and post-conversion correction.

04

System data architecture

Map native data and every foreign key.

The migration plan depends on knowing where authoritative records live and which identifiers other systems use to retrieve them.

DomainSystem typeSystem-of-record dataReference keys
Operational systemsCustomer-facing recordsAggregate customerName, TIN, relationships, legal entitlements, customer IDAccount number
Checking and savingsAccount number, address, balance, available balance, deposits, interestCustomer ID
Loan bookingAccount number, product ID, outstanding balance, schedules, collateralCustomer ID
Payment processingACH, wire, debit, credit, and other transaction dataAccount number
Credit cardAccount number, balance, customer details, origination dataCustomer ID
Financial reportingProfitability, liquidity, aggregate balances, outstanding obligationsAccount and customer IDs
Enterprise systemsShared platformsData warehouse / service busIntegrated and transformed enterprise dataEnterprise identifiers
Document managementDocuments and retention metadataAccount number
Identity and accessUser ID, credentials, login historyCustomer ID
Master data managementKYC, privacy preferences, enterprise customer IDCustomer ID and account number
Money movementExternal servicesZelleProxy ID, history, recipientsDeposit account, email, mobile
Account transferTransfer proxy and historyDeposit account, email, mobile
Bill payPayees, schedules, historyDeposit account, email, mobile
ACHExternal movement instructionsAccount and routing details
ChannelsInteraction layersOnline / mobileSchedules, nicknames, customer proxyCustomer ID
Call center / branchAssisted-service contextAccount number, name, TIN
ATMCard session and transaction contextDebit card number and PIN
Third-party embeddedPartner-specific interaction dataCustomer and account proxies
05

Putting it together

Use case: retrieve a customer’s accounts and balances.

The request looks simple. The conversion dependency is not.

01
CORE SYSTEMS

Establish the customer identity first.

Migrate the customer into the aggregate customer system and generate a cross-reference between old and new customer IDs.

02
IDENTITY & ACCESS

Move access with the new reference.

Migrate user IDs and update them with the customer cross-reference created by the core migration.

03
PRODUCTS & CHANNELS

Reconnect accounts, balances, and views.

Move authoritative product records and update the references channels use to assemble the customer experience.

Section 5 · The retrieval sequence

One request crosses the architecture.

The completed use case makes the dependency sequence tangible: a simple balance request crosses identity, channel, integration, customer, and product systems.

Click the diagram to inspect the original.

Next step

Turn the dependency model into an 83-hour conversion schedule.

Discuss a banking conversion ↗