A familiar brand can conceal a different counterparty
A trading platform may keep its brand, login screen and account interface while changing the legal entity serving a client. For payment operations, that is not simply a change of logo on an invoice. Funding instructions, account ownership, contractual obligations and the treatment of existing balances may need separate decisions before a migration can proceed.
This guide offers an independent operational planning framework for lawful forex and CFD businesses. It does not determine whether a particular client transfer is permitted or whether an overseas entity may serve a market. Legal and compliance teams must settle those questions for the firms, clients and jurisdictions involved. Payment implementation should follow that assessment rather than become a workaround for it.
Identify the applicable transfer framework
For firms and money within its scope, the FCA's CASS 7 contains specific provisions on transfers of business and client money, including conditions, notifications and different treatment in particular circumstances. Those provisions should not be reduced to a general assumption that a client balance can move whenever a group company changes. The exact route must be reviewed by qualified specialists using the current rules.
The practical first step is an entity map. Identify the current contracting firm, proposed receiving firm, relevant permissions, bank accounts, payment providers and client populations. Distinguish a service-provider change from a transfer of the client relationship itself. If teams use the same word migration for both, unresolved legal questions can be hidden inside an apparently routine technical ticket.
Build a client-level migration record
Create a controlled record linking each affected client to the old entity, intended new entity, applicable decision and effective date. The record should identify the relevant communication and any consent or instruction required by the approved legal approach. Do not assume that the absence of a support complaint constitutes agreement to a material change.
Keep this record separate from marketing segmentation. A customer who receives a promotional email is not necessarily a customer cleared for transfer. Payment operations needs an authoritative status that can prevent new instructions from being displayed prematurely. If a client is excluded or has not completed a required step, the interface should route them to an appropriate explanation rather than silently directing funds to the new firm.
Control the funding-instruction cutover
Inventory every place where clients obtain beneficiary details: the portal, saved emails, invoices, support templates and automated messages. Assign an owner to update each location. A new portal screen is insufficient if an old email remains the most convenient source of instructions. Use clear effective dates and explain how clients can verify a change through the firm's established contact channels.
Before launch, test the entity name, account details, currency, reference format and provider identifiers for each supported route. A shared brand name must not obscure the actual beneficiary. Have a second reviewer compare the displayed instructions with the authorised banking and provider records. Keep evidence of the approved version so that an unexpected transfer can be investigated against what the client was told.
Reconcile balances and payments in transit
Define the balance snapshot and the treatment of deposits, withdrawals and adjustments that remain unsettled at the cutover. A client ledger balance, a provider receivable and cash in a bank account are related but different records. The migration plan should explain how each will be reconciled and which firm is responsible for resolving each outstanding item.
Consider a hypothetical deposit initiated before the cutover but credited afterwards. The operational response should follow a predetermined exception process, not an agent's guess about which entity now owns the customer. Record the payment's origin, beneficiary, status and associated client relationship. If a return or transfer is required, obtain the appropriate authorisation and preserve the complete audit trail rather than changing the original transaction date.
Keep refunds and complaints connected to history
A client may raise a funding complaint after their account has moved. Staff still need to identify the entity and provider involved in the original transaction. Preserve access to relevant historical references under an approved retention and access design. Do not rewrite old receipts or descriptors to make the entire relationship appear to have always belonged to the new firm.
Agree who will handle a refund, disputed payment or returned withdrawal relating to the pre-migration period. The customer-facing team should know where to route the case and who owns the response. Finance should avoid duplicate reimbursement when both entities receive the same complaint. A shared case reference can support coordination without giving every employee access to all client records across the group.
Rehearse a partial migration and a rollback
Test clients who complete the required steps, clients who decline, unresolved cases and clients with payments in transit. Include an operational failure after some instructions have changed but before all channels have updated. A rollback plan must account for money already received; restoring the old website alone cannot reverse a completed financial movement.
Use a small approved pilot where appropriate and compare portal status, client records, provider reporting and bank reconciliation. Record exceptions before expanding. Commercial pressure to finish a migration should not turn unexplained balances into manual adjustments. Require a clear decision on each material discrepancy, with an owner and supporting evidence, before declaring the funding transition complete.
What it means to Merchants
Forex and CFD businesses should treat entity migration as a controlled change in responsibility, not merely a new payment configuration. Establish the legal route first, then align client records, beneficiary instructions, balances in transit and historical complaint handling. A complete reconciliation and documented exception process provide a stronger operating foundation than a visually seamless cutover that leaves the underlying firm or funds ownership unclear.