TMS replacement carrier contract checklist: preserve rates and open commitments
Key Takeaways
Published October 20, 2026
A TMS replacement should preserve the carrier agreement, its applicable rate version, and every open shipment commitment. Moving a rate table does not prove those obligations moved correctly. Build a cutover checklist that connects each carrier account and agreement to usable shipment instructions. Wilson uses customer-approved carriers and replaces the TMS for freight execution; the migration method requires customer-specific scoping.
- Software migration does not by itself amend a carrier agreement.
- Match account identity, rate applicability, and shipment evidence before testing a quote.
- Separate future shipments from loads already accepted under earlier terms.
- Treat missing agreement evidence as an unresolved migration item with an owner.
Build a carrier agreement migration checklist
The checklist should explain which commercial records the new workflow needs and how the team will validate them. Use actual agreements and shipment evidence.
| Record | What to inspect | Validation example | Responsible owner |
|---|---|---|---|
| Carrier identity | Legal entity and operating account | Match the account used on an accepted shipment | Carrier relationship owner |
| Rate basis | Applicable agreement, tariff, or quote | Reproduce the basis for a representative movement | Procurement |
| Service conditions | Equipment, locations, timing, and included services | Compare the agreement with the live shipping requirement | Logistics |
| Effective version | Relevant dates and accepted amendments | Explain which terms apply to an open load | Procurement and finance |
| Open commitment | Carrier acceptance and remaining work | Trace tracking, documents, charges, and payment ownership | Cutover lead |
This is an operating checklist, not a legal interpretation of a particular agreement. The agreement owner should resolve contractual questions.
Preserve agreement identity before copying prices
A rate needs its commercial context to remain usable. Copying a numeric amount without that context can produce a misleading quote comparison.
Identify the shipper entity, carrier account, agreement reference, locations, mode, service, and relevant conditions. Record the current source and the person responsible for correcting it. If a carrier uses separate accounts for different facilities, keep that distinction visible.
Check the conditions behind a familiar lane rate. Equipment, shipment characteristics, included services, and other terms can affect applicability. A price used successfully on one movement may not apply to a different movement with similar addresses.
Wilson works with customer-approved carriers. That preserves the customer's carrier approval role, but it does not prove that every commercial record transfers automatically. The existing carrier contract workflow provides context for retaining relationships while changing the execution process.
Validate rate versions against representative shipments
A migration test should establish which rate version applies and show how the workflow uses it. A complete-looking file is insufficient evidence.
Choose representative shipments from the actual operation. Include a normal case, a shipment with an additional service, and a case affected by changed terms. Use the corresponding carrier agreement and booking evidence as the expected basis for review.
Ask the implementation team to explain each result. If the returned amount differs, identify whether the difference comes from freight details, account selection, rate version, or an unresolved mapping. Do not adjust the expected figure merely to make the import pass.
Record any dependency on a carrier connection or external rate source. Access to a rate may depend on the specific account and interface. Define the agreed method before presenting a migrated rate table as proof that all quoting is ready.
Separate open loads from the next shipping cycle
Open loads need explicit ownership during cutover. Their remaining work can continue after the old system stops creating new shipments.
List accepted bookings, in-transit freight, missing PODs, disputed invoices, and pending payments. For each, identify the governing terms, carrier reference, current owner, and remaining action. A delivered shipment may still require financial or document work.
Decide which commitments finish in the current process and which move into the replacement. Give the carrier one clear instruction path. Avoid having two teams independently change the same accepted booking because both can see a record.
The TMS replacement guide explains the broader order-to-payment scope. This checklist focuses on the commercial evidence that must survive the transition. A new shipment record should not erase the origin or terms of an existing carrier commitment.
Test a changed agreement and an inherited invoice
The cutover evaluation should include a case that began before the new workflow. This reveals gaps that a clean new shipment cannot expose.
Use an illustrative accepted load whose carrier invoice arrives after cutover. Supply the original booking, applicable agreement, and a later documented service change. Ask the supplier to show who obtains missing evidence and how the payable amount is reviewed.
Then introduce a rate amendment for future loads. The workflow should distinguish that amendment from the earlier shipment's commercial basis. These are required buyer tests, not a claim about a standard migration feature in Wilson or another product.
Wilson audits and reconciles carrier invoices before Wallet-coordinated payment. Confirm the exact treatment of inherited loads and evidence during scoping. The approved lifecycle does not establish that every historical file or unresolved invoice can enter a new deployment unchanged.
Approve the cutover from evidence, not file counts
Approve the carrier migration when the team can demonstrate applicable terms, clear commitment ownership, and a workable exception path. A count of imported rows cannot establish those outcomes.
Keep a register of unresolved items. Record the carrier, affected workflow, missing evidence, owner, and decision needed. Separate an optional reporting field from a missing commercial condition that prevents a valid booking.
Wilson connects to the ERP order flow and replaces the TMS for freight execution. It does not integrate with another TMS. Define how the necessary commercial and historical evidence will reach the new process without assuming a universal migration connector.
The customer keeps carrier approval and decisions outside configured limits. Cartage-introduced capacity also requires customer approval. A successful transition makes that authority easier to exercise because the team can identify the right agreement, current commitment, and remaining work for each shipment.
FAQs
What happens to carrier contracts and rates during a TMS replacement?
The team must preserve applicable agreements, rate versions, account identity, and open commitments. Replacing software does not itself establish that those records transferred correctly.
Can we migrate only a price spreadsheet?
A spreadsheet may supply useful data, but prices need their applicable service, account, conditions, and version. Validate them against representative shipments.
Should open invoices follow the new rate version?
Do not assume that. Review the agreement, booked terms, and documented changes for the shipment in question. Assign contractual questions to the agreement owner.
Does Wilson require us to replace our carriers?
Wilson uses customer-approved carriers. Any additional carrier capacity requires customer approval before use. Scope the account and agreement handoff separately.