Moving from notebooks and spreadsheets to service software takes three weeks: in week one enter only new jobs, in week two migrate customer and stock records, in week three drop the notebook. Trying to do all of it in a single day is the most common reason migrations fail.
This post covers where spreadsheets break down, which data to bring across, and how to get mechanics to actually use the system.
Where spreadsheets break down
Spreadsheets are not a bad tool. The problem is that workshop work is neither single-person nor single-moment.
Two people cannot edit at once. A mechanic updating a work order at the bench while you have the stock file open in the office means one of you cannot save. Before long everyone keeps their own copy.
Nothing connects. The part written on a work order does not come off the stock file. Forget to deduct it and the stock is wrong — and you find out when the shelf is empty.
History is not searchable. "What did we fit to this bike last year?" lives somewhere inside twelve separate monthly files. Because searching takes time, nobody searches.
Nothing reminds you. A spreadsheet will not tell you a customer is due for service. That customer goes elsewhere.
What to migrate
Do not bring everything. Three data sets are enough:
Customers and motorcycles. Name, phone, plate, make, model, year. The most critical field is the phone number — reminders go through it.
Active stock. The parts genuinely on the shelf. Do not import the old stock list as-is; it contains items unsold for two years. Migration is a good moment to clear out dead stock.
Open current accounts. Who owes you, who you owe. Closed accounts do not need to move.
What you do not need to migrate: closed work orders from past years, old invoices, closed accounts. You are not throwing the old notebook away — you are just writing new records in a new place.
The three-week plan
Week 1 — new jobs only
Migrate nothing. From today, open a work order in the system for every bike that comes in. Keep the notebook running alongside.
The goal is not data entry, it is getting mechanics used to the screen. By the end of the week there will be 30–40 work orders in the system, which is enough to learn the flow.
Week 2 — customers, bikes, stock
Import the customer and motorcycle list. Most products accept an Excel or CSV upload; match the column headers to the provider's template.
Before importing stock, count the shelf. The quantity in the spreadsheet almost never matches the quantity on the shelf. Import wrong stock and you have migrated the error too.
Week 3 — drop the notebook
If the two ran in parallel for two weeks, the system is now the single source. Put the notebook away but do not throw it out; keep it aside for three months.
Open the finance side this week too: income, expense, cash, current accounts. Once a month of data accumulates you get your first real report.
If the mechanics are not using it
The real risk in a migration is not technical. The system gets installed, mechanics do not use it, and three months later everyone is back on paper.
Have the mechanic open the work order, not you. If you open it, the mechanic becomes a spectator rather than a user.
Let them work from a phone. No system that requires walking to the office computer survives at the bench. If it does not work on a phone, it is the wrong product.
Make one person responsible. Usually the youngest mechanic. Let them answer questions and deal with the provider.
Physically remove the paper. As long as blank work order forms sit on the bench, someone will fill one in.
What you will see after the first month
Once a month of data has built up, you can answer three questions for the first time:
- How many jobs did we take, and how long did each take?
- How many of each part moved, and which sat on the shelf?
- What is in the cash account at month end, and who still owes us?
Those answers existed in the spreadsheet too — in three separate files, calculated by hand. That is where you will feel the difference.
We covered what belongs inside a work order with a worked example. Reading it before migrating clarifies which fields to bring across.