Home Services Guides
Moving off spreadsheets without stopping the business
The fear is losing a week of work to the switch. The trick is to move one workflow at a time and let old work finish where it started.
Signs you have outgrown the spreadsheet
- Two people edited the schedule and one change was lost.
- A technician was double-booked or sent to an old address.
- Finished jobs were invoiced late, or not at all.
- Only one person really understands the file.
What to move, and what to leave behind
| Move | Leave behind |
|---|---|
| Active customers with addresses and contacts | Customers you have not served in years |
| Services and prices | Old price lists no one uses |
| Upcoming and recurring jobs | Completed jobs from past years (keep the old file as an archive) |
| Open quotes and unpaid invoices | Paid invoices from previous periods |
A four-week plan
| Week | What happens |
|---|---|
| Week 1 | Set up services, team and service areas. Import active customers and check duplicates. |
| Week 2 | From a fixed date, every new enquiry and job starts in the new system. Old jobs finish in the spreadsheet. |
| Week 3 | Technicians use the field app on real jobs. Fix access, checklists and roles. |
| Week 4 | Invoices and payment links from completed jobs. Stop editing the spreadsheet; keep it read-only. |
Pick the start date for week 2 and tell the whole team. A clear “from Monday, new jobs go here” avoids two systems running side by side for months.
Bringing the team with you
Start with the person who suffers most from the spreadsheet, usually the dispatcher or office manager, and let them lead. Technicians adopt a field app fastest when it removes a phone call they dislike, such as calling the office for the address.
Importing customers without making a mess
- Export active customers only, with name, phone, address and customer type.
- Put one customer per row and one location per row for customers with several addresses.
- Use one phone format, including the country code.
- Mark business customers and add their legal names and TRNs where you have them.
- Import a small batch first, check it, then import the rest.
What the first week feels like
Slower, for a few days. Someone will look for a job in the old file; a technician will call the office out of habit. That is normal. By the second week, the questions change from “where is it?” to “can it also do this?”, which is the sign the switch has worked.
Frequently asked questions
Can we run both systems for a while?
Only for jobs already in progress. New work should start in one place from a fixed date, or both systems will be half right.
How clean does our data need to be first?
Not perfect. Import active customers, fix duplicates as they show up and correct details the next time you serve each customer.