How a small carrier moves off spreadsheets to a TMS

Move off the spreadsheet when the cost of keeping it has become other people's time: when a driver's status only exists in someone's phone, when finding last March's CMR takes twenty minutes, or when one person is the only reason the whole thing still works. The switch itself is boring if you do it in the right order, which is one lane first, real loads, everything else left running until the new system has earned it.

This guide is about the general problem. If you are on some other TMS and just want the map of how these moves go, that map works the same regardless of what you end up buying.

Why the spreadsheet lasted this long

It is worth being fair to the spreadsheet, because most advice on this topic is not.

It was free. It fit your operation exactly, because you shaped it yourself, one column at a time, over years. It never made you sit through a demo. And for a fleet of six with one dispatcher who remembers everything, it genuinely is a reasonable tool. Plenty of software sold to replace it is worse.

The problem is not the spreadsheet. The problem is what grows around it. A file cannot tell a driver anything, so the status lives in WhatsApp. A file cannot hold a photo of a CMR, so the paperwork lives in an inbox. A file cannot answer at 11pm, so the dispatcher does. What you end up running is not a spreadsheet, it is a spreadsheet plus three chat threads plus a phone plus one person's memory, and only the last of those knows how it all fits together.

The four signals it is time

None of these is about fleet size. They are all about where knowledge lives.

Someone calls to ask where a truck is. Not the customer, you. If finding out costs a phone call, the status does not exist as data anywhere, and you cannot report on something that only exists in a conversation.

A document takes more than a minute to find. A CMR from four months ago, for a dispute or an audit. If the answer involves scrolling a chat thread, you do not have an archive, you have sediment.

The dispatcher cannot take a week off. This is the big one. If one person going on holiday means the operation degrades, you have a knowledge problem, and no spreadsheet has ever fixed a knowledge problem.

Invoicing lags the delivery by more than a few days. Usually because the proof of delivery has to be hunted down before anything can be raised. That lag is working capital, and it is money.

If none of those apply, keep the spreadsheet. Seriously. Come back when one of them does.

What to actually look for

Once you decide to move, the market will happily sell you the wrong thing. Three questions cut most of it away.

Does the price go up when the work goes up? Per-shipment billing means the tool takes a cut of your growth. Per-seat bundles bought in advance mean you pay for the quarter you hoped for rather than the one you had. Both are worth noticing before you sign anything, because both bite hardest in the year when things go well.

Can a driver use it without training? Whatever the office system does, it fails if the cab does not cooperate. The driver app has to work with cold hands, one thumb, and no signal. If it needs an account, an email address, and a tutorial, your drivers will use the phone instead, and you are back where you started.

Can you change it yourself? Every transport company has a field nobody else has: a customer reference, a permit number, a way of marking a load that made sense in 2019 and still does. If adding it means a support ticket and a quote, the system will slowly stop matching the work.

Ask about export before you buy, too. The polite version of the question is "what happens to my data if I leave", and the answer tells you what kind of company you are dealing with.

The move, in the order that works

Do not migrate history. This is the single most common way these projects die. Three years of old loads have almost no operational value and they will cost you a fortnight. Keep the old file, freeze it, and treat it as an archive you can read.

Start with the register, not the orders. Vehicles, trailers, drivers, contractors. It is an afternoon of typing and it is the foundation for everything else. Nothing else works until the system knows what you own and who you work with.

Then run one lane in parallel. One customer, one regular route, real loads, both systems at once for a week or two. Yes, it is double entry, and yes, it is the cheapest insurance you will ever buy. You will find the three things nobody thought about, and you will find them on a route where you already know what "correct" looks like.

Get the drivers on next, before you widen it. Ideally the ones on that lane. Watch what they actually do, not what the manual says they should. Whatever confuses a driver in week one confuses every driver forever.

Then widen it, and set a date to stop. Pick the day the spreadsheet becomes read-only and say it out loud. Migrations that never end are migrations that fail, because a team maintaining two systems will always quietly prefer the one they already know.

Expect a bad fortnight somewhere in there. Everything is slower before it is faster, and the dispatcher who has run the board for six years will hate it for about ten days. That is not a sign it is going wrong. It is what learning looks like.

Where LiteTMS fits, honestly

We built LiteTMS for exactly the company in this post: past the spreadsheet, nowhere near an enterprise rollout. So the three questions above have deliberate answers. Orders and contractors are free and unlimited, so a busy month does not cost more per load. The driver app is included, works offline, and a driver signs in with a company prefix and a PIN rather than an account. And you can add your own fields and tabs yourself.

It also suits the parallel-run advice, because there is no setup fee and no minimum term. Running one lane next to your current system for two weeks costs you the typing and nothing else.

If you want the pricing reasoning in full, it is in what LiteTMS is and why it bills pay-as-you-go. And if your reason for moving is paperwork rather than dispatch, the e-CMR and eFTI outlook is the more useful read.