Full conversion
Move from the acquired firm’s platforms to the purchaser’s systems—not a long-term lift and shift.
Point of view · Banking transformation
The problem, the landscape, and the technical and human architecture behind a successful conversion.
The situation
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.
Conversion parameters
Move from the acquired firm’s platforms to the purchaser’s systems—not a long-term lift and shift.
Move selected vendors earlier when coordination complexity or known anti-patterns create unacceptable risk.
Stage data before the event when extraction and transformation processes cannot meet the conversion window.
Sequence around services each line of business provides to the others, not just around individual applications.
The system landscape
A useful conversion model separates systems by the records they control, the services they provide, and the identifiers that connect them.
Financial product platforms that create account numbers and maintain balances, collateral, schedules, and available funds.
Platforms that connect customers to accounts, rights, risk, and regulatory attributes.
Shared infrastructure that supplies reporting, documents, identities, integrations, and day-two processing.
Customer-facing channels and transaction services that rely on identifiers from multiple systems of record.
The landscape
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
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.
Clarify what changes, what remains available, when service is interrupted, where customers and employees can get help, and how exceptions will be resolved.
Bring frontline, call-center, operations, risk, technology, and vendor teams into scenario reviews so hidden dependencies appear before the conversion window.
Use dependency sequencing, clear ownership, rehearsed decisions, and visible escalation paths to reduce avoidable support volume, duplicate work, and post-conversion correction.
System data architecture
The migration plan depends on knowing where authoritative records live and which identifiers other systems use to retrieve them.
| Domain | System type | System-of-record data | Reference keys |
|---|---|---|---|
| Operational systemsCustomer-facing records | Aggregate customer | Name, TIN, relationships, legal entitlements, customer ID | Account number |
| Checking and savings | Account number, address, balance, available balance, deposits, interest | Customer ID | |
| Loan booking | Account number, product ID, outstanding balance, schedules, collateral | Customer ID | |
| Payment processing | ACH, wire, debit, credit, and other transaction data | Account number | |
| Credit card | Account number, balance, customer details, origination data | Customer ID | |
| Financial reporting | Profitability, liquidity, aggregate balances, outstanding obligations | Account and customer IDs | |
| Enterprise systemsShared platforms | Data warehouse / service bus | Integrated and transformed enterprise data | Enterprise identifiers |
| Document management | Documents and retention metadata | Account number | |
| Identity and access | User ID, credentials, login history | Customer ID | |
| Master data management | KYC, privacy preferences, enterprise customer ID | Customer ID and account number | |
| Money movementExternal services | Zelle | Proxy ID, history, recipients | Deposit account, email, mobile |
| Account transfer | Transfer proxy and history | Deposit account, email, mobile | |
| Bill pay | Payees, schedules, history | Deposit account, email, mobile | |
| ACH | External movement instructions | Account and routing details | |
| ChannelsInteraction layers | Online / mobile | Schedules, nicknames, customer proxy | Customer ID |
| Call center / branch | Assisted-service context | Account number, name, TIN | |
| ATM | Card session and transaction context | Debit card number and PIN | |
| Third-party embedded | Partner-specific interaction data | Customer and account proxies |
Putting it together
The request looks simple. The conversion dependency is not.
Migrate the customer into the aggregate customer system and generate a cross-reference between old and new customer IDs.
Migrate user IDs and update them with the customer cross-reference created by the core migration.
Move authoritative product records and update the references channels use to assemble the customer experience.
Section 5 · The retrieval sequence
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