Moving From Excel to Garage Software: A Step-by-Step Plan
How to move a workshop from a notebook or Excel to garage software: what to prepare, importing your lists, a first-week plan, the team and common mistakes.
Fatih Bilgiç · · 7 min read
Plenty of workshops run for years on a notebook, a couple of Excel files and the memory of the people who work there. It works, until questions such as “which pads did we fit on this car last time?” or “how much does he still owe us?” come up several times a day and nobody can answer without searching. This guide is for workshop owners who want to move from paper and spreadsheets to garage software without losing a week of work: what to prepare, how to bring your lists across, how to plan the first week, how to get the team on board and which mistakes to avoid.
Where the notebook and Excel fall short
There is nothing wrong with a notebook as such. The problem is that the information lives in one place and often in one head. A workshop that works on paper usually knows these situations:
- Vehicle history gets lost. The customer says “you changed the timing belt last year”, and finding the date and the mileage means going through old books.
- Open balances are scattered. Some are at the back of the notebook, some in a spreadsheet and some only in the owner’s memory. One payment that was not crossed off becomes an awkward conversation.
- Stock is a guess. The spreadsheet says four oil filters, the shelf says one, because nobody updates a file with greasy hands.
- Only one person can use it. A file on the office computer cannot be opened at the lift, and two people cannot safely edit it at once.
- There is no overview. What the workshop earned this month is something you work out, not something you look up.
If two or three of these sound familiar, the notebook has reached its limit. The move itself is less work than most owners expect, as long as it is prepared.
What to prepare before you switch
You do not need to move your whole past. Old job cards can stay in the old books; what you need on day one are the lists you work with every day.
| List | What it should contain |
|---|---|
| Customers | Name or company, phone number, and for business customers the tax number and address. |
| Vehicles | Plate, make, model, year, VIN and current mileage, linked to the customer. |
| Parts and products | Name, part number or barcode, cost and selling price, tax rate, quantity on the shelf. |
| Open balances | Who owes you how much on the day you switch. One figure per customer is enough. |
Clean the lists before you move them; it is far easier in a spreadsheet than afterwards:
- One row per customer. Merge “J. Smith”, “John Smith” and “Smith John”.
- Phone numbers in one format, with no notes in the same cell.
- One column per piece of information: plate in one column, model in another.
- Count the shelf. Importing stock quantities that were wrong for years only moves the problem.
Bring your lists across instead of retyping
Retyping years of product cards and customers is the reason many workshops put the move off. It is rarely necessary: almost every program, and every spreadsheet, can save its lists as an Excel or CSV file, and good workshop software can read those files.
In Baktam the import works in four steps. You upload the Excel or CSV file, and the header row and columns are recognized; you can change any match. Before anything is saved you see how many rows are new, how many would update an existing record and which rows contain errors. Then you import. Stock quantities are booked into the branch you choose as opening stock, and a balance column can be written to new customers as an opening balance. Rows with errors can be downloaded, corrected and uploaded again.
Uploading a file twice does not create duplicates: products are matched by SKU, barcode or OEM number, customers by phone number and then tax number, and vehicles by plate. The full list of fields is on the data import page.
A plan for the first week
Pick a start date and stick to it. From that morning, every new car goes into the software. Running the notebook and the program side by side “for safety” doubles the work and guarantees that neither is complete.
- Before day one: import customers, vehicles and parts. Enter your business details, tax rate and the terms that are printed on your documents. Create a login for each person.
- Day one and two: job cards only. Every car that arrives gets a job card with the complaint, the mileage and the work done. Nothing else has to be perfect yet.
- Day three and four: payments. Record what each customer paid and what stays open, so that balances are in one place from now on.
- Day five: parts. Add parts to job cards from stock, so that quantities go down by themselves, and book in deliveries when they arrive.
- End of the week: look at the week together. What took longer than on paper, and why? Most of the answers are a missing product or a habit, not the software.
If you have never written a structured job card, our guide on how to write a job card is a good place to start, and the garage stock management guide covers the parts side.
Getting technicians and the front desk on board
Software often fails in a workshop for a simple reason: the owner uses it and nobody else does. People go back to paper when the new way is slower for them personally. So make it faster for each of them:
- Show each person only their part. A technician needs to see the jobs assigned to them and how to mark one as finished, on a phone. That is ten minutes, not a training day.
- Start with the one who is curious. One colleague who likes it convinces the others better than any instruction from the boss.
- Take away the old way. As long as the notebook is on the counter, it will be used.
- Use it yourself, visibly. If the owner asks “is it on the job card?” every day, it will be by the second week.
Roles: who should see what
A notebook shows everything to whoever opens it. Software lets you decide. Before you create the logins, think about three questions: who may see prices and costs, who may take payments and who may change settings. In Baktam each user has a role such as owner, manager, cashier or technician. A technician sees the jobs but not the amounts or costs, and reports are for the owner and managers. That is often what makes an owner comfortable with putting the real figures into a system at all.
Common mistakes when switching
- Trying to move ten years of history. Start with current customers, vehicles and stock. The history builds itself with every new job card.
- Importing uncleaned lists. Duplicates and wrong quantities are easier to fix before the move than after.
- Switching in the busiest week. Choose a normal week, not the one before the holidays.
- Using everything at once. Job cards first, then payments, then stock. One new habit at a time.
- Keeping the notebook “just in case”. Two systems mean two versions of the truth.
A short checklist
- Customer, vehicle and parts lists cleaned and saved as Excel or CSV.
- Shelf counted, open balances listed per customer.
- Lists imported and spot-checked: five customers, five vehicles, five parts.
- Business details, tax rate and document terms entered.
- A login and a role for each person.
- Start date agreed with the team, notebook put away on that morning.
- A review at the end of the first week.
If you want to see what the daily work looks like after the move, our auto repair shop software page walks through job cards, stock and payments in one system.