If you’ve been in the industry for a while, this sounds familiar: an Excel spreadsheet with five tabs that only its creator understands. A red column nobody can explain. And a macro that breaks everything if you touch it. The good news: moving beyond Excel doesn’t mean throwing away years of work. It means moving what already works into a system that grows with you.

In this article, I explain how we made the change at an eight-coach company in Madrid. What went well. What didn’t. And what we’d do differently today.

Why Excel stops being enough

Excel works well while the team can keep bookings and changes up to date. Three signs show that your company has outgrown it:

  • Double bookings. It happens once a month. Then once a week. Without a central system, it’s only a matter of time.
  • Bottlenecks at month-end. Three days to produce invoices that should be generated automatically.
  • ‘Only X knows how to do this’. If X goes on holiday, operations stop.
If one person can derail operations by going away for 15 days, you don’t have a business: you have a personal routine.

Step 1: clean up before migrating

The most common mistake is taking the Excel file as it is and importing it into a new system. Don’t do it. Use the migration to remove what you no longer need:

  • Customers with no services in the past two years.
  • Old rates you no longer use.
  • Drivers who no longer work for the company.

This also makes you realise how much clutter had built up. In our case, only 340 of the 1,200 customers in Excel were active.

Step 2: define what ‘a booking’ means

It sounds obvious. It isn’t. Ask three people in your company what counts as a confirmed booking and you’ll get three answers. Before migrating anything, decide together:

  • When does it move from ‘request’ to ‘confirmed’?
  • When is the driver assigned: on confirmation or the day before?
  • Who can change the price once it’s confirmed?
A practical tip Write it on a sheet of paper and put it up in the office for the first week. It’s the best way to get the whole team speaking the same language from day one.

Step 3: migrate in stages, not all at once

Migrating everything in one weekend is tempting. And risky. What worked best for us was doing it in stages:

  1. Week 1: customers and rates.
  2. Week 2: future bookings.
  3. Week 3: invoicing.
  4. Week 4: schedules and drivers.

Each stage has a day of ‘double entry’ in the new system and old Excel file to check everything matches. It’s tedious. But it prevents a lost booking in the first month.

Step 4: train your team, don’t just tell them

Your traffic manager has used the same spreadsheet for 10 years. Change is difficult, especially when the current setup works. The quickest way to kill a migration is to say: ‘here, this is how it works now’. It doesn’t work.

What does work:

  • Thirty-minute sessions, not three-hour ones.
  • One real case at a time: customer X’s booking, Monday’s schedule…
  • Give each person a ‘buddy’ for the first two weeks.

Step 5: measure to see if it works

Three simple metrics to see whether the migration is going well:

  • Average time to quote a service. Before: 18 min. After: 2 min.
  • Bookings lost to human error. Before: 4–5 a month. After: 0–1.
  • Days to close the month. Before: 4. After: 1.

If these numbers haven’t changed after four weeks, something isn’t right. Go back to step 4.

What we’d do differently today

Migrate a month before the busy season. We started in March, with weddings just around the corner. Bad timing. If we did it again, we’d choose January or November.

And above all: don’t look for the perfect system. Look for the one your team will use on Monday morning. Because a poorly used spreadsheet will always be worse than an imperfect system people actually use.

Thinking of making the switch? At Ruttio, we help you migrate bookings, customers and rates in a week, without stopping operations. Tell us about your business →