What happens to our carrier contacts and shipment records if we stop using freight software?
What happens to our carrier contacts and shipment records if we stop using freight software?
Consider a hypothetical food-ingredients manufacturer three months from a freight software renewal. The logistics manager decides not to renew and asks for "all our data." What comes back is a spreadsheet of 6,400 load rows: dates, origins, destinations, carrier names and a total cost per load. No rate confirmations. No PODs. No contact names for the dispatchers the team has worked with for years, because those contacts were stored in the vendor's carrier directory, not in the company's own carrier list. The contracted LTL rates the team negotiated were entered as tariffs inside the platform, and the export only shows totals. Two carriers onboarded through the vendor's marketplace say they'll need to set up the company again from scratch.
When a company stops using freight software, it keeps whatever the contract says it owns and whatever it can actually export in a usable form; everything else stays with the vendor or has to be rebuilt. In practice, a shipper should expect to keep its own carrier contacts, negotiated rates, rules, approval limits and shipment history, including documents, if it asks for them in the right format and in time. Carriers, rates and capacity that came from a vendor's own network or marketplace often don't transfer, because that relationship belonged to the vendor.
The good news: most of the pain in the example is avoidable. It comes from three gaps: not knowing who owned what, not asking for documents and history alongside the rows, and not starting the exit early enough to fix what was missing.
The three questions that decide what you keep
- Who entered it, and under whose name? A carrier your team added, with contacts your team typed in, is almost always your data. A carrier record the vendor maintains for all its customers usually isn't.
- Can it be exported, and in what shape? Data you own but can't export in a usable format is only half yours.
- Is anything still running? Open loads, unpaid invoices and active claims need to finish somewhere.
The rest of this article goes through each, plus what to put in place before signing with any freight software, so the exit is a routine task rather than a rescue.
Let's review what your team would need to keep from day one. You don't need to prepare anything: Cartage maps the workflow with you on the call.
See it on your own loads. Wilson, by Cartage, is an AI logistics agent that quotes, books, tracks, audits and pays for freight with your approved carriers.
Book a demo →Which freight records does a company own, and which stay with the vendor?
A shipper usually owns the records about its own freight and relationships: its carriers and contacts, its negotiated rates, its rules and the history of its loads. A vendor usually owns its software, its shared carrier directory and any marketplace rates or capacity it offers to all customers. The line is not always written down, which is why it's worth sorting record by record.
Record-by-record ownership
| Record | Usually the shipper's | Often stays with the vendor | What to check |
|---|---|---|---|
| Carriers the team added and approved | Yes | No | Whether the export includes approval status, lanes and insurance or authority details collected |
| Carrier contacts entered by the team | Yes | No | Whether names, roles, emails and phone numbers export with the carrier |
| Carriers from the vendor's network or marketplace | The relationship, if the carrier agrees | The vendor's terms and directory record | Whether the carrier can keep working with you directly after you leave |
| Negotiated contract rates and tariffs | Yes | No | Whether rates export as rate tables, not just as load totals |
| Rates offered through a vendor marketplace | No | Usually | Whether past quotes and rates on your loads stay in your history |
| Orders, loads and shipment history | Yes | No | Whether every field exports, including references and status changes |
| Documents (BOL, POD, rate confirmations, invoices) | Yes | No | Whether files export and stay linked to the right load |
| Rules, approval limits, routing preferences | Yes | No | Whether they export as readable rules or only exist as settings screens |
| Notes and preferences learned over time | Yes | Depends | Whether notes on carriers, receivers and lanes export |
| Change history on each load | Yes | No | Whether who-did-what-when exports, not just the final state |
| Payment records | Yes | Depends on who held the funds | Whether remittances and payment dates match the invoices |
Why carrier contacts get lost so often
Carrier contacts are the record most teams assume they have and most often don't. Three reasons:
- They live in a shared directory. Some platforms keep one carrier record for all customers and let each customer see it. When the customer leaves, it stops seeing the record, including the dispatcher names it relied on.
- They live in people's inboxes. The real contact for a lane is the person who answers at 6:00 am, and that person's details are in an email signature, not in any system.
- They're stored without roles. A list of emails without "dispatch," "billing" or "after hours" isn't much help to the next person.
The fix is simple but needs discipline: keep the company's own carrier list, with contacts and roles, as company data from the start, whatever software sits on top of it.
Rates need their structure, not just their totals
A total cost per load tells you what you paid. It doesn't tell you how the rate was built: base rate, fuel, minimums, accessorial charges, discounts. Without the structure, the next system or the next person can't quote or audit against the contract. Ask for rate tables, fuel tables and accessorial schedules in their original form.
History is more than the final state
The final state of a load says it was delivered on Thursday at $1,840. The history says it was booked at $1,650, a liftgate was added after the receiver called, the carrier proposed a detention charge, and someone approved $1,840. When a customer disputes a charge or a carrier files a claim six months later, the history is what settles it.
How do you get your records out before you leave freight software?
Start the exit at least a full billing cycle before the end date, ask for a complete export early, test it on a sample of real loads, then finish or move every piece of open work before the old system goes dark. An export requested on the last day almost always comes back incomplete, and by then there's no time to ask again.
A step-by-step exit plan
Step 1: Inventory what lives in the system. List every type of record in the software: carriers, contacts, rates, orders, loads, documents, invoices, payments, rules, notes and history. Mark which ones the team uses weekly and which are needed for compliance or disputes.
Step 2: Read the contract. Find the data ownership, export and termination clauses. Note how long the vendor keeps data after the contract ends, whether export is included or charged, and what format the vendor commits to.
Step 3: Request a full export early. Ask for every record type on the inventory, not just "our data." Specify formats: rows for structured data, original files for documents, and a mapping that links each document to its load.
Step 4: Test the export on real loads. Pick ten loads from different months, modes and carriers. For each one, check that the export has the full load record, every document, the rate as booked, the invoice as paid and the history of changes. Gaps found on ten loads will exist on thousands.
Step 5: Rebuild the carrier list. Merge the exported carriers and contacts with what's in the team's inboxes and phones. Add roles. Mark which carriers came through the vendor's network and need a direct conversation.
Step 6: Talk to network carriers directly. For carriers met through the vendor's marketplace, ask whether they'll work with the company directly, and on what terms. Some will need new onboarding paperwork; some may be bound by the vendor's terms for a period.
Step 7: Close out open work. Loads in transit finish in the old system or move with their documents. Unpaid invoices get audited and paid, or moved with their rate confirmations and PODs. Open claims get a named owner and a copy of every document.
Step 8: Store the archive. Put the final export somewhere the company controls, organized so someone who wasn't involved can find a load by number or date three years from now.
What to do with open loads on the last day
| Open item | Risk if nobody owns it | What to do |
|---|---|---|
| Load in transit | No one sees the delay or collects the POD | Finish it in the old system, or move it with its full record |
| Delivered, POD not received | Invoice can't be audited, customer billing stalls | Request POD now, store it with the load |
| Invoice received, not paid | Carrier isn't paid or gets paid twice | Audit and pay before cutover, or move with all documents |
| Rate dispute open | Supporting evidence lost | Export the rate confirmation, messages and history for that load |
| Cargo claim filed or likely | Claim fails for missing documents | Export the BOL, POD with exceptions noted, photos and invoice |
| Carrier onboarding in progress | Carrier gets stuck between systems | Pause or finish under the new process |
Claims and disputes have long tails
Freight disputes often surface months after delivery. Under 49 U.S.C. 14706, carriers may not set a deadline shorter than nine months for filing a cargo claim or shorter than two years for bringing a suit after a claim is denied. A company that can't find the BOL and the POD for a load it shipped eight months ago is in a weak position. Keep claim-related records for at least the life of any possible claim.
Tax and recordkeeping periods
Freight invoices and payment records support the company's tax return. The IRS general rule is to keep records for three years, with longer periods in some situations. Brokers, for their part, must keep records of each transaction for three years under federal rules. A shipper's own records policy should set retention for freight records explicitly, rather than leave it to whatever the software vendor happens to keep.
What should a usable freight data export include?
A usable export lets someone who wasn't there rebuild any load: who shipped what, with which carrier, at what agreed rate, with what documents, what changed along the way and what was paid. If a record type can't support that, the export isn't complete.
Fields to ask for, by record type
| Record type | Fields that should be in the export | Common gap |
|---|---|---|
| Carriers | Legal name, MC or DOT number, address, approval status, lanes and modes approved, insurance details collected, date added | Approval status and lanes missing |
| Carrier contacts | Name, role, email, phone, carrier link, notes on preferred channel | Roles missing; contacts not linked to carriers |
| Rates | Lane, mode, equipment, base rate, minimums, fuel table, accessorial schedule, valid from and to | Only load totals exported |
| Orders | Order number, customer, ship-from, ship-to, items, weights, requested dates, references | Order and load not linked |
| Loads | Load number, order link, carrier, booked rate, pickup and delivery dates and times, status changes | Only final status exported |
| Quotes | Every quote received per load, with carrier, amount, validity and the one chosen | Losing quotes dropped |
| Documents | BOL, POD, rate confirmation, invoice, photos, as original files linked to the load | Files exported without a load link |
| Invoices and payments | Invoice number, amount, line items, audit result, approver, payment date and method | Audit result and approver missing |
| Rules and limits | Approval limits, routing preferences, carrier preferences per lane, receiver requirements | Rules exist only as settings screens |
| Change history | Timestamp, who or what made each change, old value, new value, message link | Not exported at all |
Formats that age well
Plain formats outlast software. Structured data in comma-separated files or a standard database export, documents in their original PDF or image formats, and a simple index that maps each document to its load number. Avoid exports that only open in the vendor's own viewer.
Test the export with a question
The quickest way to judge an export is to ask it a real question. Pick one:
- "What did we pay this carrier on this lane in March, and did it match the rate confirmation?"
- "Who approved the accessorial on load 31877, and when?"
- "Which receiver requires an appointment 48 hours ahead?"
If the team can answer from the export in a few minutes, the export works. If the answer needs the old system, it doesn't.
Hypothetical example: a good export versus a thin one
For the food-ingredients manufacturer from the opening, the thin export answered "how many loads did we ship to Ohio last year?" and almost nothing else. A complete export would have answered the March carrier question by joining the load, the rate confirmation and the invoice; the accessorial question from the change history; and the receiver question from the rules. Same loads, very different value.
What should you ask any freight software vendor before signing?
Ask who owns each record type, how and how fast the company can export it, what happens to carriers met through the vendor and what happens to open loads, invoices and payments at the end. These questions take ten minutes during evaluation and save weeks at exit. They apply to any vendor, including AI logistics agents, TMS products and broker platforms.
The questions, in plain language
| Area | Question to ask | A good answer sounds like |
|---|---|---|
| Ownership | Who owns our carriers, contacts, rates, rules and load history? | "You do," in the contract, by record type |
| Export | Can we export everything, at any time, not just at the end? | Yes, with formats named and documents included |
| Documents | Do BOLs, PODs, rate confirmations and invoices export as files linked to loads? | Yes, with an index by load |
| History | Does the change history export? | Yes, with who, what and when |
| Network carriers | If we met a carrier through your network, can we keep working with them after we leave? | A clear answer, written down |
| Open work | What happens to loads in transit and unpaid invoices on the last day? | A named process |
| Payments | If you hold funds or pay carriers for us, how are payments in progress settled? | A named process with dates |
| Retention | How long do you keep our data after we leave, and how do we confirm deletion? | A stated period and a deletion confirmation |
| Cost | Is export included, or charged? | Included, or the charge is stated up front |
Mistakes that make leaving harder
Letting the vendor be the only place contacts live. Keep the company's carrier list as company data from day one, even if it's a spreadsheet that mirrors the system.
Accepting "we can export everything" without seeing it. Ask for a sample export during evaluation, on test data if needed.
Forgetting rules and preferences. Approval limits, receiver requirements and lane preferences take years to build up. If they only exist as settings in a vendor screen, they leave nothing behind.
Ignoring the payment path. If a vendor pays carriers on the shipper's behalf, ask how funds and in-progress payments are handled at the end.
Waiting for the renewal notice. By then, the export is a rush job.
For the wider plan when moving from one system to another, see how to switch logistics software without disrupting shipping. For audit records specifically, see how to keep control of your freight audit data. Teams deciding whether to renew at all can use the TMS renewal versus replacement decision.
How does Wilson, by Cartage, handle carrier contacts and shipment records?
Wilson, by Cartage, is an AI logistics agent that keeps every order, load, quote, rate, document and contact on record as it works, connected to the company's ERP; the company owns its carriers, rules, approval limits and contacts, and its records are searchable and exportable with change history. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.
Cartage positions Wilson as a free logistics department: what big shippers build over years, Wilson does from day one. Records are part of each of its four parts.
The data
The data is the part this question is about. Wilson keeps every order, load, quote, rate, document and contact on record as it works. Every message, confirmation and change is kept in the shipment's change history. Wilson also keeps memories and rules, learned from its own work or added by the team, such as "this lane's carrier wants a pickup number in the subject line" or "this receiver takes deliveries only before 11 am," and the team can edit them. The company owns its carriers, rules, approval limits and contacts, and records are searchable and exportable with change history. Each customer's data is encrypted, lives inside that customer's organization and is not used to train Wilson. Specific export formats and timing depend on the setup; confirm them in discovery. Wilson replaces the TMS for freight execution and connects to the company's ERP. Wilson works with SAP, NetSuite, Microsoft Dynamics 365, Oracle, Infor, Epicor, Sage, Acumatica and other ERP environments, with the exact connection depending on the customer's data flow and scope.
The labor
The labor is what fills the record. Wilson does the work start to finish, from the first quote to the final POD: quotes, bookings, paperwork, tracking and carrier follow-ups, by email, phone calls, texts, Slack and Teams. It generates rate confirmations, bills of lading, packing slips and pallet labels, and requests and files PODs, so the documents are on the load as the work happens rather than collected at the end. The team doesn't chase carriers.
The network
The network is separate from the company's own carriers. Wilson's network includes carriers and brokers, and the shipper's volume counts with every other Wilson customer's, which can bring better freight rates on its lanes. The company still approves who hauls its freight, and shippers can keep their own carriers, which keep their direct contracts and credit terms with the shipper. How carriers met through the network are handled if a company stops using Wilson is a fair question to settle in discovery.
The payments
The payments leave a record too. Wilson audits every freight invoice against the load before money moves, then pays carriers from the Wilson Wallet. Invoices over the rate or outside the rules wait for a person. The audit result, the approver and the payment sit on the load with the rate confirmation and POD. How payments in progress are settled at the end of a relationship depends on the setup; confirm it in discovery.
What the company keeps control of
| Item | Who owns or controls it with Wilson |
|---|---|
| Carriers and their approval | The company; Wilson books only carriers the company has approved |
| Carrier contacts | The company |
| Rules and approval limits | The company, editable by the team |
| Memories and preferences | Learned by Wilson or added by the team; the team can edit them |
| Orders, loads, quotes, rates, documents | On record, searchable and exportable with change history |
Wilson starts with assisted execution. The company sets approval limits, and routine actions can run automatically within those rules as the workflow is proven. Wilson handles LTL, FTL, ocean, drayage, parcel and cross-border freight. It is not a freight broker or a customs broker.
Pricing
Wilson is free on Wilson's network: the shipper pays the freight rate and nothing on top. When a shipper keeps its own carriers, the fee is 2% to 0.5% of what Wilson pays them, falling with volume. There are no seat fees, no setup cost and no contract. Timing depends on scope: most teams start on a few lanes and expand from there.
FAQs
If we leave Wilson, what happens to our carriers and records?
Wilson, by Cartage, an AI logistics agent, keeps every order, load, quote, rate, document and contact on record as it works. The company owns its carriers, rules, approval limits and contacts, and records are searchable and exportable with change history. The company's own carriers keep their direct contracts and credit terms with the shipper. Export formats and the handling of open work depend on the setup and should be confirmed in discovery.
Do we own our carrier contacts in freight software?
Contacts your team entered for carriers your team added should be yours, but check the contract. Contacts stored in a vendor's shared carrier directory may disappear from view when you leave. Keep your own carrier list with contacts and roles from the start.
Can we keep carriers we found through a vendor's network?
Often, but not automatically. The relationship may be governed by the vendor's terms. Ask the vendor before signing, and ask the carrier directly before leaving.
What should a freight data export include?
Carriers with approval status, contacts with roles, rate tables, orders, loads, every quote, documents linked to each load, invoices with audit results and payments, rules and limits, and the change history of each load.
How long should we keep freight records?
Set a written retention policy. The IRS general rule is three years for records that support a tax return, with longer periods in some situations. Cargo claims can be filed for at least nine months after delivery under federal law, with up to two more years to sue after a denial, so keep claim-related documents at least that long.
Is a spreadsheet of load totals enough when leaving a TMS?
No. Totals show what was paid, not how the rate was built, what changed or who approved it. You need rate tables, documents and change history to audit invoices, handle disputes and set up the next system.
When should we request our data export?
At least one full billing cycle before the end date, and ideally a sample during the first months of using any system. That leaves time to fix gaps while the vendor still has your account active.
What happens to loads in transit when we switch systems?
Either finish them in the old system or move them with their full record, including the rate confirmation and any messages. Give each open load, unpaid invoice and open claim a named owner for the switch.
What questions should we ask a freight software vendor about data before signing?
Who owns each record type, whether you can export everything at any time, whether documents and change history export, what happens to network carriers and open work at the end, and whether export is included in the price.
Sources
- Cartage, Wilson product FAQ and product scope, October 2026: https://cartage.ai
- Internal Revenue Service, How long should I keep records?: https://www.irs.gov/businesses/small-businesses-self-employed/how-long-should-i-keep-records
- 49 CFR 371.3, Records to be kept by brokers (Cornell Legal Information Institute): https://www.law.cornell.edu/cfr/text/49/371.3
- 49 U.S.C. 14706, Liability of carriers under receipts and bills of lading: https://www.law.cornell.edu/uscode/text/49/14706
Let's review what your team would need to keep from day one. You don't need to prepare anything: Cartage maps the workflow with you on the call.
