EventWe're exhibiting at Forex Expo Dubai πŸ‡¦πŸ‡ͺMeet us at Forex Expo Dubai πŸ‡¦πŸ‡ͺAt Forex Expo Dubai πŸ‡¦πŸ‡ͺ22–23 Sep 202622–23 SepSee the schedule
By use case

Move the firm without losing history.

Traders, accounts, challenge history, payouts and documents mapped, dry-run against staging, reconciled with you line by line, then cut over in a window you choose. No trader loses their record.

Migration Β· staging run 3History intact
Traders41,208 / 41,208
Accounts63,114 / 63,114
Challenge history217,845 rows
Payout ledger88,410 / 96,200
Count reconciliationmatches source
The problem

Migration fear keeps firms on bad systems.

History that won't map

The old system has no concept of a phase or a reset, so the export flattens years of trader history into nothing.

Downtime nobody can afford

A cutover that stops trading or payouts for a day costs more in trust than the migration saves in a year.

Silent data loss

Records arrive but nobody reconciles counts, and the gaps only surface during a dispute months later.

The path

How we de-risk it.

Nothing is irreversible until you sign off on the reconciliation.

1
Stage 1

Map

We inspect your schema and agree a field-by-field mapping, including how legacy phases and resets translate.

2
Stage 2

Dry run

Full import into a staging tenant. Nothing touches production and nothing is visible to traders.

3
Stage 3

Reconcile

Counts and balances compared line by line against your source. You sign off before we proceed.

4
Stage 4

Cut over

Delta sync and switch in a window you choose, with the old system readable as a fallback.

Total time to live
Under 1 week
What moves

What's included

Standard on every firm running on the platform. No add-on tier, no per-seat unlock.

06capabilities
included by default
  • 01Trader identities and contact records
  • 02All accounts across every platform
  • 03Challenge history including resets
  • 04Payout and transaction ledger
  • 05KYC documents and verification state
  • 06Parallel run before any cutover
Questions

Questions operators ask

It usually is. Duplicate traders, orphaned accounts and inconsistent statuses are normal, and the mapping stage is where we find them. You get a data-quality report before import, so cleanup is a decision rather than a surprise.
No. The cutover is a delta sync into an already-populated tenant, scheduled in a window you choose. Traders keep their accounts, history and credentials.
Yes, and most firms do for a week or two. The legacy system stays readable as a fallback until you're confident, and we keep the delta sync running through that period.
Let's talk

Send us a schema, get a plan.

We'll map your export and come back with a dated migration plan and a data-quality read.