Logistics and distribution
TMS migration for freight brokers: preserving load and rate history
By SourceX Editorial · Updated
Short answer
A TMS migration for a freight broker usually moves active customers, carriers and open loads, while closed loads, check-call notes, documents and the links between quote, rate confirmation and invoice often stay behind. Export every record family with its original load number before the old contract ends, and keep notes and documents mapped to the loads they belong to.
Key takeaways
- Closed load history is rarely in the default conversion scope, so plan to export it yourself.
- The load number is the master key; keep it alongside customer reference numbers, carrier IDs and invoice numbers.
- Notes, check calls and document images are the records most often lost in a switch.
- Read the termination and data return clauses before giving notice, because access after the contract ends may be limited.
What load and rate history is at risk in a TMS switch?#
The load and rate history at risk in a TMS switch is everything outside the new vendor's import scope, which usually means closed loads and the records around them. Conversions focus on what the brokerage needs on go-live day: customers, carriers, lanes, open loads and receivables.
What gets left behind is the record of how the business worked: customer quotes that won or lost, carrier rate confirmations, check-call notes, accessorial disputes, claims and the documents attached to each load. These are also the records that AI quoting, carrier matching and tracking tools learn from.
Ask the new vendor for a written conversion scope that lists record types and date ranges. Anything not listed is your responsibility to export from the old system before access ends.
Cutover checklist: what to export#
Export every record family, not only the ones the new TMS will import, and keep each family's own identifiers. The table lists the families most brokerages hold and the keys that tie them together.
Rate history deserves special attention. Customer quotes and carrier pay on the same load show the margin a desk accepted under real market conditions, and they usually live in different tables. Export them together with the load number so the spread can be rebuilt.
| Record family | What to include | Keys to keep |
|---|---|---|
| Loads and stops | Shipper, consignee, appointments, actual times, equipment, status history | Load number, stop IDs, customer reference numbers |
| Customer quotes | Spot and contract quotes, won or lost, lost reason | Quote ID, load number when booked |
| Carrier pay and rate confirmations | Rates, accessorials, signed rate confirmation PDFs | Rate confirmation number, carrier ID, load number |
| Customer invoices | Linehaul, accessorials, adjustments, payment status | Invoice number, load number |
| Check calls and tracking | Notes, ETA changes, status messages, exceptions | Load number, timestamps, user IDs |
| Carrier profiles | Authority snapshots, insurance, contacts, onboarding decisions | Carrier ID, MC and DOT numbers |
| Documents | Bills of lading, proofs of delivery, claims files | Document ID and a manifest mapping files to loads |
| EDI logs | Tenders, responses, status messages, invoices | Interchange control numbers and load number |
Link keys you cannot afford to lose#
Link keys are what turn a set of exported tables back into a history; lose them and the records become disconnected lists. Confirm that each of these keys appears in every export before the old system is turned off.
Keep a crosswalk table that maps old load numbers to new ones for any loads that do migrate. Without it, the same shipment appears twice with no way to tell the copies apart.
- The load number from the old TMS, kept even if the new system assigns new numbers.
- Customer reference numbers such as PO, BOL and PRO numbers.
- Carrier IDs plus MC and DOT numbers, so carriers can be matched across systems.
- Quote IDs linked to the loads they produced.
- Invoice and rate confirmation numbers linked to loads.
- User IDs for reps and carrier sales, so desk-level history survives staff changes.
- Document IDs with a manifest that maps each file to its load.
Notes and documents are the first casualties#
Notes and documents are the first casualties of a TMS migration because they rarely sit in the main load table. Free-text notes are often stored in separate tables, and document images may sit in the vendor's storage rather than in your database.
Check how the old system stores both. If the vendor holds the documents, ask for a bulk export with file names or a manifest that ties each file to a load. If notes are stored by user and timestamp, export them in full rather than as a single summary field.
Do not rely on screenshots or canned reports as a substitute. A report of loads by customer is useful for finance but loses the sequence of events that shows how a problem was handled, which is the part a new team, an auditor or an AI developer would actually want.
Mistakes that cost brokerages their history#
The mistakes that cost brokerages their history are predictable, which makes them avoidable. Each is paired here with its later cost and a prevention step.
Most of these mistakes come from treating the switch as an IT project. The people who know which notes matter are the operations leads and carrier reps, so include them when the export plan is reviewed.
| Mistake | What it costs later | Prevention |
|---|---|---|
| Giving notice before checking data return terms | Limited or paid access to your own history | Read termination and export clauses first |
| Exporting summary reports instead of tables | No way to rebuild loads and events | Request full table exports or a database backup |
| Dropping old load numbers | Documents and claims cannot be matched | Keep the old number on every record |
| Skipping notes and check calls | No record of how exceptions were handled | Export notes tables in full |
| Leaving documents in vendor storage | Missing proofs of delivery and rate confirmations | Bulk download with a manifest |
| No owner for the archive | Files scattered across laptops and shared drives | Name an owner and a single storage location |
Illustrative: a brokerage moves to a cloud TMS#
Illustrative: Copperline Logistics, a fictional freight brokerage with several desks, is moving from an older TMS to a cloud platform. The new vendor's plan converts customers, carriers and open loads; closed loads are out of scope.
The COO names an archive owner, asks the old vendor for full table exports and a document manifest, and confirms that old load numbers will be stored as a reference field on every migrated record. Before giving notice, the team verifies the exports by rebuilding a sample of loads end to end, from quote to invoice.
The closed-load archive goes into encrypted company storage. When the brokerage later evaluates AI quoting tools and asks whether its load and rate history could be licensed, the archive is complete, documented and ready to describe.
Why the archive matters, and how SourceX works with it#
A complete load archive matters because rate, lane, carrier and exception history is what AI freight tools are built on, and because it is evidence in disputes and in a future sale of the business. A brokerage that loses it in a migration cannot recreate it.
SourceX works with archives where they already sit; large datasets stay in your storage or ship on encrypted drives. The SourceX five-step transaction starts with metadata only, and customer and carrier rights are reviewed before a single file is prepared. The SourceX Evidence Packet then records what was included and who authorized its release.
Frequently asked questions
Should we migrate closed loads into the new TMS?
Only if the new system and your team will use them. Many brokerages migrate recent closed loads for reference and archive the rest. Either way, keep a full export of every closed load with its original keys, because a partial migration is not an archive.
How long should we keep access to the old TMS?
Long enough to verify every export against the source, which should be planned before giving notice. Some vendors offer read-only access for a fee; others end access when the contract ends. Your agreement decides, so check it before setting a cutover date.
Who owns customer rate history?
Your rates and margins are your business records, but customer contracts may treat pricing as confidential information. Internal use is usually straightforward. Outside use, including licensing, needs a review of customer agreements and typically removes customer identities.
What about carrier and driver personal information in the archive?
Carrier packets include tax IDs, bank details and contact information, and check-call notes can include driver names and phone numbers. Store the archive with access controls and an access log, and remove personal details before any outside use.
Can we license load history after the migration?
Possibly, if the archive is complete and the rights are clear. Linked loads, quotes, rate confirmations and exceptions are the kind of history AI developers ask about. The quality of the exports made during the migration decides whether that option exists at all.
Should EDI history be part of the archive?
Yes, if you can get it. Tender, status and invoice messages exchanged with shippers and carriers show what each party was told and when, which settles many disputes. Ask the EDI provider or TMS vendor for raw message logs keyed to load numbers, not only acknowledgment reports.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.