Ask a Transport Manager why the ageing transport management system (TMS) is still running and the answer is rarely loyalty. It is fear. Jobs are live, invoices are half-billed, drivers are mid-route, and the DVSA does not pause your operator licence obligations while you change software. So the dated system stays, the workarounds multiply, and the renewal quietly rolls over for another term.
The fear is understandable. It is also mostly fixable with planning. This is the playbook for how to switch TMS without stopping the trucks: what actually moves, what stays exactly where it is, how the four phases of a migration run, and the questions that separate a vendor with a real migration process from one with a sales deck.
Why switching a TMS feels riskier than it is
A haulage operation never has a quiet week to change systems in. There are always open orders, unbilled jobs and a planning desk that cannot go dark for a morning, let alone a fortnight. Add the compliance layer, walkaround records, defect reports and safety inspection files that must stay available whatever software you run, and doing nothing starts to look like the safe option.
It is not. The safest moment to switch TMS never arrives on its own, and an ageing TMS carries its own quiet risk: planners working around the system instead of in it, data that disagrees between tools, and new starters who have to learn years of accumulated workarounds before they can plan a full day. The real cost of running on broken tools compounds monthly, whether you measure it or not. The question is not whether to switch, but how to switch TMS without the operation feeling it.
The answer is that a well-run migration never has a moment where the trucks depend on an untested system. The old and new systems overlap, deliberately, until the office is confident. Here is how that works in practice.
What moves when you switch TMS, and what stays
The first thing to get clear is that a TMS migration is not one big data transfer. Different data has different jobs, and each category is handled differently.
Master data moves across
Customers, delivery points, tariffs and rate cards, drivers, vehicles and trailers: this is the data the new system is built on, and it moves across as a structured import. This is also your one genuine chance to clean house. Duplicate customer records, dead delivery points and tariffs nobody has used in years should not make the journey. Budget proper time for the clean-up: duplicates, outdated delivery points and obsolete tariffs are far easier to deal with before import than after go-live.
Live work moves last
Plan for open orders and forward bookings to be entered or imported into the new system close to go-live, so nothing is planned in two places for longer than necessary.
Compliance history stays available, wherever it lives
This is the part operators most often get wrong. DVSA’s Guide to Maintaining Roadworthiness requires safety inspection records and drivers’ defect reports, including rectification work, to be kept for at least 15 months, and confirms that electronic records are acceptable provided they are complete, tamper-proof and available for examination. The same guide is explicit that records must remain available even for vehicles that have been sold or removed from the licence. Changing software does not reset that clock.
Practically, the outcome that matters is access: historic checks, defects and inspection records must remain producible for the applicable retention period. Depending on what the outgoing system offers, that may mean exporting and archiving the records in a format you can produce on request, or retaining read access where the vendor supports it and the commercial terms allow. Agree which, in writing, before you serve notice. An examiner will not accept “we changed systems” as an answer. Historic PODs are a separate commercial record: migrate or archive them according to your customer contracts and your own dispute-history needs. Invoices and accounting records are different again, and should be retained in line with the applicable HMRC and accounting record requirements.
Your integrations are reconnected, not replaced
Switching the TMS should not mean switching everything around it. Your accounts package and your vehicle tracker have their own contracts, their own data and their own users, and a modern platform connects to them rather than displacing them. HaulierMagic integrates with the tools operators already run, including accounting packages such as Xero and Sage, so the finance team’s month-end process survives the migration intact.
The four-phase migration plan
A structured switch runs in four overlapping phases. On HaulierMagic the whole project typically takes two to four weeks, run alongside your day-to-day operations rather than instead of them, but the shape of the plan applies whichever system you choose.
Phase 1: audit and map
Export everything from the old system and audit it. Which customers are live? Which tariffs are current? Which delivery points still exist? Map each field in the old system to its home in the new one and decide, item by item, what gets cleaned, what gets archived and what gets imported. This phase is desk work, not disruption; the operation does not notice it happening.
Phase 2: build and import
The new tenant is configured: users and roles, tariffs and scales, vehicle and trailer profiles, customer records and delivery points, all imported in bulk. This is also when the accounts connection and tracker feed are set up and tested with real data, not sample files. On the vendor’s side, this is a supported workflow, not a favour; if a supplier treats bulk import as an afterthought, treat that as your answer.
Phase 3: parallel running
The stage that removes the risk. For a defined window, planners run the day in the old system as normal while shadowing the same work in the new one, so discrepancies surface while they are cheap to fix and confidence builds on real work rather than training data. Ask any vendor to plan for this explicitly. Operators moving to HaulierMagic run alongside the existing system until the office is confident, and only then go live.
Phase 4: cutover
Pick a natural boundary, a Monday or the start of an invoicing period. Open orders move across and the new system becomes the single source of truth, with drivers ideally already familiar with the new app from parallel running. What happens to the old system depends on its vendor and your exit terms: whether it can be held open for reference, exported wholesale, or archived. Whichever route applies, preserve access to the compliance history per the retention rules above before anything is switched off.
Keeping planners and drivers onside
A technically successful migration can still struggle if the people who run the day do not adopt the new system. Two groups decide whether the switch sticks.
Planners are won during parallel running, not in a training room. Shadow-planning real work for a week or two teaches the new screens faster than any course, and it surfaces the awkward jobs, the split loads, the multi-collection runs, the customer with the strange tariff, while the old system is still there as a safety net. Insist that your most sceptical senior planner is in the parallel-running group, not excluded from it. If the system convinces them, it will convince everyone.
Drivers need less than most operators fear. They install one app on their own Android or iOS phone and see their jobs, checks and PODs in one place. The Driver App works offline and syncs when the signal returns, so a dead spot on the A66 does not become a support call. Roll the app out during parallel running and let drivers complete a few real PODs on it before it becomes the system of record, so cutover morning is a non-event rather than a first encounter.
The questions to ask any vendor before you sign
A vendor’s migration process is part of the product. Ask these before commercial terms, and get the answers in writing.
What exactly is included in getting us live? Each element should be a named line item with an owner, not a vague promise of support. HaulierMagic’s implementation covers data setup and import, team training, parallel running and go-live support, typically over two to four weeks; any integration work is scoped separately and quoted up front, so it appears in your comparison as its own line.
What does connecting our existing tools cost? Integration work should be scoped and quoted up front as a one-off, not discovered on the first invoice. HaulierMagic publishes its integration pricing alongside its per-user subscription rates, which makes the total cost of the move a calculation rather than a negotiation.
How does parallel running work, and for how long? If the vendor’s plan goes straight from training to live, the risk sits with you.
Who do we call in week six? A named contact through setup, go-live and afterwards is worth more than a ticket queue. Ask to meet the person, not the process.
How do we get our data out again? The exit terms you sign today are the migration you will run in five years. A vendor confident in the product will not object to clear export rights.
If consolidation is part of why you are moving, our page for Transport Managers replacing an ageing TMS sets out what the destination looks like; the questions above establish whether any vendor, us included, can get you there safely.
What good looks like on cutover morning
The cutover checklist
- Every open order visible in the new system, and the totals reconciled against the old one.
- Compliance record access preserved: the archive or retained-access arrangement documented, and a named person able to produce records on request.
- Accounts connection tested with a real invoice, and the nominal codes checked by the finance team, not the vendor.
- Tracker feed live and vehicle positions showing on the map.
- Every driver logged into the app, with at least one real POD already completed during parallel running.
- A named support contact on call for the first week, and the senior planner’s list of open snags owned, dated and shrinking.
If all six hold, the trucks never noticed. That is the standard to hold any vendor to, including us. The operators who switch well are not the ones who found a risk-free moment; there is no such moment in haulage. They are the ones who made the risk boring: cleaned data, an overlap period, a real checklist, and a vendor whose migration process was examined as hard as its planning screen.
Planning a TMS switch? In a 30-minute demo we will map your current setup, walk the migration of your data, and show how HaulierMagic runs alongside your existing system before go-live.
Switching TMS: the questions operators ask
What should we ask our current TMS provider before giving notice?
Four things, in writing: the full data export they will provide and in what format; what access, if any, remains after termination and at what cost; the exact notice mechanics, date, method and any auto-renewal term; and confirmation of any deletion timelines, so records are not purged while you still need them. The answers shape your archive plan and your timetable, so get them before the evaluation starts, not after you have chosen a replacement.
What if our old TMS does not offer read-only access after we leave?
Then the export becomes the plan, and it needs doing before the contract ends. Take a complete export of safety inspection records, defect reports and their rectification history in a producible format, store it somewhere durable with a named owner, and test that you can actually retrieve a specific vehicle’s records from it. The legal requirement is that the records remain available for the applicable retention period; the mechanism, archive or retained access, is yours to choose from what the outgoing vendor actually offers.
Should we switch TMS at renewal or start planning earlier?
For many operators, renewal is the cleanest commercial point to switch, but planning should start well before it. The audit, requirements and vendor evaluation take longer than most operators expect, and leaving them inside the notice period turns a considered decision into a rollover. Working back from the renewal date by nine to twelve months, as set out in our 12-month TMS renewal plan, keeps every option open, including renegotiating with the incumbent from a position of knowledge, and it lets you choose the migration slot rather than have the calendar choose it.
