Nov 12, 2026Broker Tips
Switching Forex CRM: A Migration Runbook That Keeps Compliance, IBs and Clients Intact

Brokers rarely replace a CRM because a feature is missing. They replace it because the system no longer fits how the brokerage runs, and the risk sits in the migration, not the new platform. This runbook covers the broker-specific parts of a forex CRM migration: KYC evidence, IB hierarchies, trading-server links, the cutover itself, and the implementation mistakes that undo good planning.
Key Takeaways for Brokers
- Name one system of record per data type: before a single field moves, decide which system owns clients, KYC status, trading accounts, balances and IB trees at every stage of the project.
- Cut IB commissions at a period boundary: close and pay the final period in the old CRM, then start the new one clean. Mid-period switches are the most common source of IB disputes.
- Integrations are the migration: moving records is the easy part. Re-pointing trading servers, PSPs and KYC providers without losing in-flight transactions is where the real work lies.
- Define rollback before cutover: written rollback criteria, a named decision-maker and a read-only old system turn a bad cutover night into a recoverable one.
Why Brokers Switch CRM, and Why Migrations Fail
The triggers are operational. A broker adds MT5 or a second trading server and the CRM cannot handle both. A new licence brings reporting and onboarding rules the current workflows cannot enforce. The IB programme outgrows flat commission plans. Or vendor support has become the bottleneck for every change the desk requests.
Migrations fail for a narrower set of reasons:
- Treated as a data export: the project is scoped as moving a CSV, not as moving live processes with money and regulatory evidence attached.
- No single owner: compliance, finance, the dealing desk and IB management each assume someone else is signing off.
- Integrations discovered late: the PSP webhook, the KYC provider callback or the affiliate tracking script surfaces in the final week.
- No reconciliation standard: nobody defined what 'migrated correctly' means, so nobody can prove it.
Inventory and Data Mapping
Start with a full inventory of what the current CRM holds and what depends on it. Most brokers underestimate the second half.
What to inventory
- Clients and leads: profiles, lifecycle status, assigned agent, source and campaign attribution.
- KYC evidence: the documents themselves plus verification outcome, timestamps, reviewer, provider reference IDs and expiry dates for IDs and proof of address.
- Suitability records: risk classification, appropriateness test answers and results, client categorisation.
- Consent records: marketing opt-ins, accepted terms and their version, communication preferences, all with timestamps.
- Interaction history: notes, call logs, tickets, open complaints and their handling history.
- Trading account links: login IDs, server, group, leverage settings and account currency.
- Financial history: deposits, withdrawals, bonuses, adjustments, and anything currently pending.
- Staff users: roles, desk assignments and permission sets.
Mapping rules that prevent rework
- Map statuses explicitly: an old status such as 'Pending L2' needs a defined target in the new system, not a best guess during import.
- Preserve original timestamps: a KYC approval dated to the import day destroys your audit trail.
- Keep legacy IDs: store the old CRM's client ID in a reference field so support, finance and compliance can trace any record back.
- Decide what stays behind: duplicates, test accounts and dead leads should be excluded under your retention policy, documented, not dropped silently. Dormant clients with funds or open positions always migrate.
Run trial loads into a test environment and check samples by hand: a verified client, a rejected one, a dormant account, a corporate account, an IB with sub-IBs. Edge cases surface faster in ten real records than in a thousand-row count check.
Moving IB Hierarchies and Commission History Without Breaking Payouts
IBs judge the new system on one thing: whether they get paid correctly and on time. A migration that delays a payout cycle costs partner trust that took years to build.
- Export the tree, not a list: every IB record needs its parent, its level and its assigned clients. A flat export loses the hierarchy that multi-tier payouts depend on.
- Map deal types one by one: per-lot rebates, revenue share, CPA and hybrid plans each need an equivalent in the new system. Panda's IB Portal supports multi-level payouts up to five tiers and nine deal types, so check early whether any existing structure goes deeper or uses terms that need redesign.
- Cut over at a period boundary: close the commission period in the old CRM, pay it, and start the new period in the new system. Never split one period across two calculation engines.
- Import commission history as reference: IBs and finance will need past statements. Bring them across as read-only history, or keep them accessible in the archived system.
- Protect tracking links and referral codes: if partner links change, attribution breaks and new clients land without an IB. Preserve codes or redirect old links before cutover.
- Reconcile in parallel: during the parallel run, calculate commissions in both systems on the same trades and investigate every difference.
- Tell IBs before, not after: new portal login, statement format and the date of the first payout from the new system.
For how commission structures and multi-level hierarchies should work once you are live, see our IB system guide.
Re-pointing Integrations: Trading Servers, PSPs and KYC Providers
Trading servers
Every CRM client must map to the correct login on the correct server, with group and leverage intact. Agree which system creates new trading accounts during the transition: only one should, or you will create duplicates or orphans. If you run multiple servers, test each one separately. Our overview of trading server architecture covers what the CRM depends on at server level.
Payment service providers
PSP callbacks and webhooks must point to the new CRM at a defined moment. Deposits initiated in the old system and confirmed after cutover are the classic failure: money arrives, but no balance updates. Clear or freeze pending withdrawals before the switch, and reconcile PSP reports against CRM balances afterwards.
KYC providers
Move provider reference IDs with each client so ongoing monitoring and re-screening continue without re-verifying the whole book. Confirm how expiry alerts and periodic reviews carry over, and that rejected applicants stay rejected.
Everything else
VoIP, email and SMS gateways, marketing automation, affiliate tracking, BI tools and the client area. List each one with its owner and its test case. Panda CRM offers 300+ integrations; check your existing providers against the integrations list at scoping stage, not during build.
Compliance and Data-Protection Sign-Off Before Cutover
Compliance approves before production data moves, not after go-live. The sign-off pack should answer:
- Transfer security: how data is encrypted in transit, who handles export files, and when staging copies are deleted.
- Hosting and jurisdiction: where the new system stores data, and whether any cross-border transfer needs documented safeguards.
- Access control: which staff roles see what in the new system, reviewed rather than copied from the old one.
- Record retention: how long the old CRM stays accessible in read-only form, and how retention obligations are met for records you chose not to migrate.
- Audit trail continuity: evidence that KYC decisions, consent and complaint histories survived with original dates and actors.
Whether a CRM change counts as a material change requiring notice under your licence is a question for your compliance officer and legal counsel. Raise it at scoping, not cutover week. For security controls on the new platform, review our data security approach.
Parallel Run, Cutover and Rollback: A Phase-by-Phase Checklist
Phase 1: Scope and ownership
- One named owner and one approval gate per phase.
- System of record defined for each data type at each stage.
- Success criteria written down: what must reconcile, and to what tolerance.
Phase 2: Mapping and trial loads
- Field and status mapping approved by compliance and operations.
- At least two full trial migrations into a test environment.
- Manual sample checks on edge-case records.
Phase 3: Build and integration testing
- Every integration tested end to end in sandbox: account creation, deposit, withdrawal, KYC callback, IB attribution.
- Staff trained on the new workflows, not just the new screens.
Phase 4: Parallel run
- Cover at least one full IB commission cycle and one client statement cycle.
- Reconcile client balances, KYC status counts and commission totals between systems.
- Log every discrepancy with a root cause, not just a fix.
Phase 5: Cutover
- Announced freeze window for back-office changes.
- Delta migration of records changed since the last full load.
- Integrations switched in a fixed order, each followed by a smoke test.
- Client communication sent: new client area link, login or password reset steps if required.
Phase 6: Hypercare and rollback
- Rollback criteria agreed in advance, such as failed balance reconciliation or a broken PSP callback.
- One person authorised to call rollback.
- Old CRM kept read-only and intact until hypercare closes.
Common CRM Implementation Problems and How to Avoid Them
- Rebuilding the old CRM in the new one: replicating every legacy workaround imports the problems you were trying to leave. Review each workflow before rebuilding it.
- Copying permissions wholesale: old role sets usually carry years of exceptions. Rebuild access from current job functions.
- Desks that never adopt it: if sales and retention keep working from spreadsheets, the CRM data decays within weeks. Involve desk heads in workflow design.
- Forgotten client communication: a changed client area URL or forced password reset without notice floods support and looks like a security incident to clients.
- Reports rebuilt last: management and regulatory reports should be validated during the parallel run. Our post on CRM reporting and compliance covers what those reports need to show.
- Vendor dependence for small changes: confirm which workflows, fields and automations your team can configure without raising a ticket.
FAQ
How long does a forex CRM migration take?
It depends on data volume, the number of integrations, IB programme complexity and how clean the source data is. The parallel run alone should span a full commission and statement cycle, so plan around your own cycle dates.
Do clients have to repeat KYC after a migration?
Not if verification outcomes, documents, timestamps and provider references migrate intact and compliance accepts the evidence trail. Clients with expired documents follow your normal re-verification process.
What happens to the old CRM after cutover?
Keep it read-only through hypercare and for as long as your retention obligations require access to records you did not migrate. Decommission only after compliance signs off.
Do I need to notify my regulator when I change CRM?
That depends on your licence conditions and jurisdiction. Ask your compliance officer and legal counsel at the start of the project.
Planning a Move to Panda CRM
If you are scoping a switch, start with the questions in this runbook: where your KYC evidence lives, how your IB tree is built and which integrations must survive cutover. Book a demo of Panda CRM to walk through your current setup with the PandaTS team.