Freight broker migration guide
MercuryGate TMS is now Infios Transportation Management. Infios publicly positions the product for complex moves across modes, geographies, currencies, and industries, within a broader supply-chain execution suite. ARK TMS is a sharper fit when a U.S. freight brokerage wants a dedicated broker operating system without carrying global shipper optimization requirements into the implementation.
Current public positioning
Infios states that MercuryGate TMS is now Infios Transportation Management, with the same proven capabilities. Its current product page emphasizes multimodal planning, global transportation, rate optimization, visibility, risk, analytics, and connections to order and warehouse execution.
Read Infios Transportation Management product pageFit and proof
This is an evaluation framework, not a feature-count scorecard. Current contracts, plans, configurations, and integrations can change what either system supports.
| Decision area | MercuryGate / Infios TM | ARK TMS | Acceptance test |
|---|---|---|---|
| Primary operating model | Infios TM targets multimodal transportation across regions and industries, including complex shipper and 3PL networks. | ARK targets freight brokers managing customer, carrier, load, tracking, document, billing, and reporting work. | Classify every requirement as brokerage-critical, enterprise-shared, or no longer needed. |
| Planning and optimization | Infios promotes rate optimization, multimodal planning, shipment optimization, and global KPI analysis. | ARK focuses on broker execution and operational control rather than global transport optimization. | Do not switch until every optimization output your team depends on has a replacement or retirement decision. |
| Suite dependencies | Infios positions transportation as part of a modular execution suite connected to order and warehouse management. | ARK is a standalone broker TMS with provider integrations for the operating workflows it supports. | Trace order creation, warehouse events, tendering, status, settlement, and analytics across system boundaries. |
| Implementation surface | Enterprise, global, and multimodal configuration can create a large migration surface. | ARK can be evaluated through a bounded broker workflow with separately scoped migrations and custom integrations. | Build a smallest viable brokerage scope and reject inherited requirements that no owner can justify. |
Evaluation plan
Use the same people, source records, and acceptance criteria in both systems. A guided demo is useful; a completed workflow is stronger evidence.
Choose a real lane, customer, carrier profile, document set, and accounting path.
Enter or import the order, assign ownership, and confirm the operational fields.
Test the load-board, carrier, rate, safety, and confirmation steps you actually use.
Validate statuses, tracking, exceptions, documents, and team handoffs.
Generate the billing records and reconcile the supported accounting handoff.
Migration sequence
Confirm export rights, archive requirements, open-load ownership, provider credentials, and acceptance criteria before the prior system changes.
Inventory contracts, environments, documentation, integrations, and exports under both the legacy and current product names.
Separate freight-broker execution from shipper, global, warehouse, order, optimization, and multi-currency workflows.
Map the Infios object model to ARK loads, stops, customers, carriers, charges, documents, and status history.
Sequence order intake, EDI, providers, accounting, analytics, and downstream consumers with explicit ownership.
Choose a bounded U.S. brokerage flow with enough complexity to expose gaps before a wider rollout.
Data scope
Cutover controls
ARK evidence
Migration FAQ
Infios states that MercuryGate TMS is now Infios Transportation Management. Use both names while discovering contracts, files, integrations, and internal documentation so legacy references are not missed.
No. ARK is aimed at freight brokerage operations. Organizations that require global multimodal optimization, multi-currency execution, or close integration with order and warehouse suites may be better served by an enterprise platform unless those needs sit outside the migrating business unit.
Start with a bounded U.S. brokerage operation, a known customer set, representative freight, and a controlled integration list. Preserve the enterprise source systems until order intake, status, documents, billing, and reporting reconcile.
Prove the fit
Bring one representative load, the integration list, required exports, and the people who own each handoff. Leave with documented fit, gaps, and next steps.