Back to overview
Lesson 5 of 5

Implementation Planning and Go-Live

8 min read

The Parallel-Run Approach

Switching IB management platforms is not a weekend migration. Active IBs have ongoing commission balances, pending payouts, and live client referral links. A hard cutover risks commission calculation gaps, broken attribution chains, and IB trust damage that takes months to repair. The parallel-run approach keeps the existing system operational while the new platform is configured, tested, and validated alongside it.

During the parallel period, both systems receive the same trade data and calculate commissions independently. The broker compares outputs daily. When the new system matches the old system within an acceptable variance (typically under 0.1% per IB) for a full payout cycle, the cutover can proceed with confidence.

Implementation Phase Timeline

PhaseDurationKey ActivitiesExit Criteria
Phase 1: Setup and integration2-4 weeksMT4/MT5 API connection, CRM integration, commission rule configurationAll data sources connected and producing clean output
Phase 2: Data migration1-2 weeksIB accounts, hierarchy structures, historical commission records, agreement documentsAll active IBs migrated with correct hierarchy positions and commission rates
Phase 3: Parallel run2-4 weeksBoth systems calculate commissions on live data; daily comparison reportsCommission variance under 0.1% per IB for one full payout cycle
Phase 4: IB portal rollout1-2 weeksInvite IBs to new portal in batches; support desk trained on new system80% of active IBs have logged into the new portal
Phase 5: Cutover and decommission1 weekSwitch primary system; redirect referral links; archive old system dataAll new commissions calculated exclusively on new platform

Total implementation typically takes 8-14 weeks for a broker with 100-300 IBs. Brokers with simpler commission structures (single-tier, fixed lot-based only) can compress this to 6-8 weeks. Brokers with complex multi-tier hierarchies, multiple MT4/MT5 servers, and regulatory requirements across jurisdictions should plan for the longer end.

Data Migration Priorities

Not all data from the old system carries equal importance. The migration must prioritize active operational data that affects current commissions and IB relationships. Historical reporting data can be migrated later or archived separately.

  • Priority 1 -- Active IB accounts: Name, contact, tier assignment, commission rates, agreement status, KYC documents. These must be accurate before any parallel run begins
  • Priority 2 -- Hierarchy structures: Parent-child relationships between master IBs and sub-IBs. One misplaced sub-IB means override commissions flow to the wrong parent
  • Priority 3 -- Pending commission balances: Amounts earned but not yet paid. These must carry over so IBs do not lose unpaid earnings during the transition
  • Priority 4 -- Active referral links: URL mapping from old tracking links to new system. Broken referral links mean lost attribution and angry IBs
  • Priority 5 -- Historical commission records: Past payout history for IB accounting and dispute resolution. Can be migrated in bulk after cutover

IB Communication Plan

IBs are partners, not employees. They cannot be forced to adopt a new system -- they must be shown why it benefits them. The communication plan should start 4-6 weeks before the portal rollout and focus on what IBs gain: faster commission visibility, better reporting, sub-IB management tools, and more reliable payouts.

  • Week -6: Announce the upgrade to top-tier IBs personally. Explain the timeline and ask for feedback on portal requirements
  • Week -4: Send a broad announcement to all IBs with a timeline and FAQ. Emphasize that commission balances will carry over and referral links will continue working
  • Week -2: Invite the first batch of IBs (top 20% by volume) to the new portal for early testing. Collect feedback and fix issues before the full rollout
  • Week 0: Full portal rollout with step-by-step login guide, video walkthrough, and dedicated support channel for transition questions
  • Week +2: Follow up with IBs who have not logged in. Offer one-on-one onboarding calls for high-value partners

The most common IB concern during platform transitions is commission accuracy. Before the cutover, send each IB a comparison showing their last three months of commissions calculated on both the old and new systems. When IBs see identical numbers, their trust in the new platform is established before they even log in.

Post-Go-Live Monitoring

The first 30 days after cutover require active monitoring. Commission discrepancies that were invisible during the parallel run may surface when the new system handles edge cases -- IBs with unusual rate structures, clients who registered before the migration but trade afterward, or trades that span the cutover timestamp. Assign a dedicated team member to review commission calculations daily for the first two weeks, then weekly for the next two.

  • Daily commission audit for the first 14 days: Compare total commission output against expected ranges based on historical averages
  • IB portal adoption tracking: Monitor login rates and identify IBs who have not accessed the new system
  • Support ticket categorization: Track whether migration-related issues (broken links, missing data, portal access) are trending down
  • Performance benchmarking: Confirm that commission calculation time, API response time, and portal load time meet SLA targets under production load

Key Takeaways

  • Use a parallel-run approach where both old and new systems calculate commissions on live data simultaneously until variance drops below 0.1%
  • Plan 8-14 weeks for full implementation including setup, migration, parallel run, portal rollout, and cutover
  • Prioritize migrating active IB accounts, hierarchies, and pending balances before historical data
  • Communicate with IBs 4-6 weeks before portal rollout, start with top-tier partners, and provide commission comparison reports to build trust
  • Monitor commission calculations daily for the first 14 days post-cutover to catch edge cases missed during parallel testing