Replace the trading platform one component at a time.

Clients keep trading on MetaTrader, cTrader, or your own server while the CRM, client portal, payments, and back office are replaced, and the trading core goes last. A one-page PDF gives twelve checks: map what the platform does, replace it in order, and switch the old one off.

Get the one-page PDF

Map

The platform is the spec. Every component, integration, and per-group setting it runs in production is listed, and every number that touches client money is reconciled before anything is replaced.

Replace

Around the core first: CRM, client portal, payments, back office. The trading core goes last, one account group at a time. Every replaced component has a way back.

Switch off

One person on your team owns each replaced component. The old platform is switched off one piece at a time, and the last licence has a date.

What is in the PDF

Twelve checks. One page. Four to map what the platform does, four to replace it without stopping trading, four to switch the old one off. Three are below. The other nine are in the PDF.

Map

Every component that touches client money runs in parallel with the old one and is reconciled daily, per account, to the cent: balance, equity, margin, swap, and commission. Nothing switches until the numbers match.

Replace

Components around the trading core go first: CRM, client portal, payments, back office, reporting. The trading core goes last, on its own milestone. Clients keep trading on the old server until then.

Switch off

The old platform is switched off one component at a time, and the last licence has an end date. Running both forever is two platforms and two bills.

The architecture is led by practitioners like Alexey Kichin. His prior work is enterprise architecture across banking and FinTech, including six years at Deutsche Bank.

Email me the checklist

One page, PDF, free. The link is on the next screen and in your inbox. One email. We do not start a sequence from this form.

Your information stays confidential and is only used to respond to your request. See our Privacy Policy.

The checklist is ready.

Download the PDF. The same link is on its way to your inbox. A 30-minute scoping call is optional — reply to that email if you want one.

Download the PDF

Swap vendors over one weekend.

A weekend window works for the trading core, one account group at a time, after a reconciled dry run. Moving the CRM, portal, payments, and back office in the same weekend bets that every integration nobody listed still works on Monday.

We will rewrite it from scratch.

A ground-up rewrite freezes the platform until the new one does everything the old one did, including the settings nobody wrote down. One component at a time keeps clients trading on a working platform the whole way.

An agent can write it.

Coding agents can write a lot of a new CRM or back office. They cannot tell you whether the balances match. The daily reconciliation in check 2 can, and it decides what switches.

Common questions

Yes. One page, PDF. The form puts the link on the next screen and sends it to your inbox. One email. We do not start a sequence from this form.

The replacement is a sequence of fixed milestones, sized after the first one. The first is shaped for four weeks: the decision on what is replaced and in what order, and one replaced component in production. We do not publish a price, and we do not quote a whole platform in four weeks.

No. The checklist keeps the reports you file today running through each switch. Your compliance officer decides what the regulator needs to hear and when. We do not file reports for you or give regulatory advice.

Read access to the components you want replaced and their integrations, the account group and symbol configuration from MetaTrader, cTrader, or your own server, one day of reconciliation output, and someone who knows why the odd settings exist. Without that there is no baseline and no engagement. If coding agents wrote your in-house components and nobody owns them, the first step is AI Code Cleanup. The work is a fixed milestone, and a senior practitioner leads every engagement.