Migrating from one liquidity solution to another does not have to mean replacing the entire setup at once.
Takeprofit Bridge can be introduced alongside the existing oneZero Hub, allowing brokers to move clients and liquidity providers gradually while keeping the previous route available during the migration.
Let’s see what are the migration steps and what to expect during Takeprofit Bridge setup and onboarding.
Why the Migration Can Be Done Gradually
The key is that Takeprofit Bridge supports oneZero on both sides of the connection:
- oneZero can be used as a maker, allowing Takeprofit Bridge to receive liquidity from the existing oneZero Hub,
- and as a taker, allowing systems using oneZero’s client protocol to connect to Takeprofit Bridge.
This makes a staged migration possible. Instead of disconnecting the existing hub and rebuilding the entire liquidity setup in one cutover, Takeprofit Bridge can first be added to the current infrastructure. Individual clients and providers can then be moved one by one.
With Takeprofit Bridge API and FIX integration, brokers can recreate and test provider and client connections in parallel, validate routing and pricing, and then switch traffic gradually once the new setup is ready.
Stage 1 — Install Takeprofit Bridge Alongside oneZero
Takeprofit Bridge is deployed on a separate server and connected to the existing oneZero Hub as a maker.
At this stage, the live trading chain remains unchanged. Real prices can already flow from oneZero into Takeprofit Bridge while the broker prepares and validates instruments, price channels, risk profiles, margin accounts, and other required settings.
One configuration point to keep in mind: if the oneZero side returns an error such as “Taker ‘TPT_Hub’ is not authorized to trade on behalf of taker ‘Taker_1’”, this normally means that the corresponding margin account has not been configured for that taker on the oneZero side.
Stage 2 — Validate the Setup Before Moving Live Traffic
Before switching any live client connection, the broker can test the new configuration inside Takeprofit Bridge.
The built-in test-order function creates an order as if it had been submitted by a selected client and runs it through the configured price channel, risk profile, and routing rules. The order is stopped before it reaches the liquidity provider.
This allows the broker to verify how the new setup behaves without sending a real trade to the market.
Stage 3 — Move Takers One at a Time
Trading platforms, white labels, and API clients can then be moved individually from oneZero Hub to Takeprofit Bridge.
Rather than switching every connection simultaneously, the broker can start with a test account or a small client group. Takeprofit Bridge generates credentials for each new taker connection, while clients that have not yet been migrated continue to use the existing oneZero route.
This makes it possible to validate each connection before moving the next one.
Stage 4 — Move Liquidity Providers
Liquidity providers can then be connected directly to Takeprofit Bridge as makers while the existing oneZero maker remains active.
Several makers can supply the same instrument and can be arranged by priority. A newly connected provider can therefore be introduced at a lower priority, monitored, and then moved higher once its pricing and execution have been validated.
The transition can also be managed at instrument level rather than shifting all liquidity at once. Adding or removing a maker does not require restarting Takeprofit Bridge.
Stage 5 — Remove the Old oneZero Connection
Once all required takers and liquidity providers have been migrated and no instruments depend on the oneZero connection, the oneZero maker can be disabled and removed.
At that point, Takeprofit Bridge becomes the primary liquidity aggregation and routing layer.
The Migration Remains Reversible
An important part of this approach is that the existing oneZero Hub remains available throughout the main migration stages. The same staged logic can also apply when moving from PrimeXM XCore.
Makers and takers can be enabled or disabled individually, while each instrument has its own provider priority list. If a newly migrated connection does not behave as expected, the broker can change the configuration and return traffic to the previous route rather than restoring the whole environment from a backup.
The migration therefore works as a sequence of controlled changes rather than a single one-way cutover.
Carrying the Existing Configuration Over
For larger environments, rebuilding every instrument and routing rule manually would make migration unnecessarily time-consuming.
Takeprofit Bridge supports TSV import and export for instrument settings, price-channel rules, and provider symbol mappings. Symbol sets can also be imported from an MT4, MT5, or other trading platform server export. A combined import can create an instrument, its provider mapping, price-channel rule, and risk-profile override from the same file.
Routing can also be recreated for setups that rely on standard FIX fields. Brokers migrating from oneZero commonly use FIX tag 1 for the account and tag 115 for on-behalf-of routing. Takeprofit Bridge supports both through a routing table in the GUI, allowing rules to be configured per margin account.
Several oneZero-specific behaviors are also available as dedicated maker settings, reducing the amount of logic that needs to be rebuilt during migration.
What Brokers Gain After the Migration
When comparing oneZero Hub pricing with the cost of migrating to another liquidity solution, brokers also need to consider which functions remain available after the switch and how customizable Takeprofit Bridge is for their existing setup.
With Takeprofit Bridge, the core areas handled by oneZero Hub — liquidity connectivity, aggregation, routing, pricing, risk management, and monitoring — remain part of the broker’s setup after migration.
Liquidity aggregation and connectivity
Takeprofit Bridge supports around 30 provider APIs that can be aggregated into a single order book per instrument. Brokers can connect multiple liquidity sources and manage them from one interface.
Per-instrument failover
Failover can be configured at instrument level. The system can react not only when a session disconnects, but also when a price feed stops updating for a defined period.
Client-specific price channels
Price channels allow brokers to control what each client receives, including the instrument list, markup, and market depth, without changing settings for other clients.
Risk and exposure management
Risk profiles can be combined with A-book/B-book exposure management, NOP limits, and alerts, giving the broker more control over how trading flow is handled.
Monitoring dashboards
Takeprofit Bridge provides monitoring dashboards for key performance metrics and trading risk.
Brokers can track performance indicators such as:
- orders per second
- order processing
- connection status
- latency
- execution activity
Risk monitoring includes:
- exposure
- net open position
- A-book/B-book distribution
- risk-limit breaches
- concentration by symbol or liquidity source
For deeper infrastructure monitoring, Prometheus can collect technical metrics, while Grafana displays them in dashboards and alerts.
REST API
A signed REST API is available for retrieving operational data, including information about takers and account positions.
Conclusion
Learn more about Takeprofit bridge as an alternative to oneZero Hub.