Why MercuryGate operators switch
MercuryGate is a serious piece of software — built for shippers and 3PLs managing complex LTL optimization at enterprise scale. That engineering investment is reflected in the price tag. The problem for freight brokers is you're paying for capabilities you'll never use, while the broker-specific features you need most are bolt-ons or missing entirely.
The specific triggers we see most often:
- $8k–$20k/month for a 15–30 agent brokerage operation — enterprise pricing for a mid-market shop.
- LTL optimization engine that's irrelevant for truckload brokers — you're subsidizing features you don't use.
- No AI employees — workflow rules and reporting, not autonomous agents that work while you sleep.
- Complex implementation: 90–180 day onboarding timelines are standard, not exceptional.
- Commission engine requires external spreadsheets — disputes every settlement period.
What to export before you start
Do this before any vendor conversation. Your data is yours — get it out regardless of what you decide next.
- Carrier records — MC#, DOT#, contacts, insurance certs, payment method (CSV)
- Customer/shipper accounts — name, billing address, credit terms, contacts (CSV)
- Lane rate history — origin/dest pairs, equipment type, rates, dates (CSV)
- Open shipments — every load not yet invoiced or settled; this is the critical list
- Commission history — by agent, by period, last 12 months minimum (CSV)
- Document templates — rate confirmations, BOL formats (PDF or Word)
14-Day Migration Timeline
Account setup + configuration
HatchOS account creation, branding, office structure, user accounts. Vendor-led — you review and approve.
Data import: carriers + accounts
Import carrier and customer records from CSV exports. Validate row counts against your MercuryGate export. Flag records with missing insurance or banking data.
Commission contracts + factor integration
Configure commission contracts per agent. Set up factor associations and ACH routing rules. Test a payment end-to-end before going live.
Dispatcher and agent training
Core workflows: load creation, carrier assignment, tracking, POD collection, invoicing. Most teams are productive within 4 hours of hands-on use.
Parallel operation
All new loads enter HatchOS. In-flight loads tracked in both systems. Do not skip this — it's your safety net during cutover.
Full cutover
No new entries in MercuryGate. Archive access (do not delete — you'll need historical records). HatchOS is live.
Common failure points
- Assuming MercuryGate data exports are clean — They're not. Run row counts and validate key fields before import. Budget time for cleanup.
- Commission contract discrepancies — Reconcile with each agent before import. Surprises at first settlement are avoidable.
- Missing carrier banking data — Flag carriers without ACH info before cutover. You can't pay them if this is wrong.
- Dropping in-flight loads at cutover — Print an explicit list of every open load on cutover day. Track them manually through settlement.
- No internal champion — Your most experienced dispatcher needs to be bought in early. They'll set the tone for the rest of the team.
See HatchOS live before you commit
We'll walk through the full migration process — carrier import, commission setup, AI employees — in 30 minutes.
Book a Demo →