SPREADSHEET MIGRATION GUIDE
How to move your service business off spreadsheets.
Spreadsheets can work well until too many people need to update the same job. This guide shows how to prepare your team for a shared system without losing important records.
Something to build on · 01
Spot the trouble before shopping
List the repeated mistakes that cost the most time: double booking, outdated addresses, missed reminders, duplicated contacts, unpaid invoices, and job notes trapped in text messages. If a spreadsheet is still working, keep it until there is a clear reason to change.
Something to build on · 02
Inventory the data you have
Make a copy of every active workbook and identify its owner. Note which columns describe customers, properties, technicians, appointments, jobs, parts, and payments. Check whether two spreadsheets use the same column name to mean different things.
Something to build on · 03
Clean a small sample
Normalize contact names and phone formats, identify duplicate addresses, and flag unknown statuses. Do not delete uncertain records. Create a mapping sheet that shows source column, destination field, required format, and the rule for blank values.
Something to build on · 04
Move the active work first
Tomorrow's jobs, open estimates, active customers, and unpaid balances deserve extra attention. Years-old archives may remain available separately if that is practical and legally appropriate. Reconcile record counts before and after import.
Something to build on · 05
Train with three everyday tasks
Have office staff book a visit, dispatch move a job, and a technician complete a work order. Make sure finance can find the invoice and that someone with admin access can export a sample record. Repeat these tasks until the team can do them confidently.
Something to build on · 06
Keep a fallback during cutover
Document who owns the source files, when new edits stop, how missed changes will be entered, and how the team will recover if the new system fails. Switching should reduce uncertainty, not create more of it.
Example to try: A spreadsheet has "John Smith" at two addresses. Preserve both property records until the business confirms whether they belong to one person or two.
Good questions
What else would
you like to know?
Do I need to move every old spreadsheet?
No. Start with data needed for current operations and a legal/business reason to retain history.
Can I import a CSV directly?
Only after mapping and supported import behavior have been verified in the destination software.
What if my customer list has duplicates?
Use an explicit review process. Never automatically merge records that may belong to different customers or properties.