Contents
- Write down why you're switching
- Pick the right switch date
- Inventory everything the old system holds
- Export early and check what you get
- Clean the data before you import it
- Map the fields and run a small test import
- Decide how to cut over
- Train people by role
- Update every link and connection
- A week-by-week plan
- The first week: what to watch
- When to cancel the old system
- Mistakes that cost owners days
Most owners put off switching software for the same reason: fear of the week when nothing works. Jobs get lost, techs can't find addresses, invoices go out twice and the phone keeps ringing anyway. That week isn't inevitable. With a few weeks of planning, most of the work happens before the switch, and the day itself is almost dull. Here's how to do it.
Write down why you're switching
Before you look at a single export, write down the three problems the new system must fix. For example:
- "Techs can't see equipment history on site, so they call the office."
- "We retype every invoice into our accounting software."
- "Membership renewals live on a spreadsheet and some slip through."
Then list everything the old system does that you rely on, including the things nobody thinks about. This list keeps you from trading one problem for another, and it's what you'll check the new system against in demos.
Pick the right switch date
- Choose a slow stretch. For HVAC that's often spring or fall, between the heating and cooling rushes. Landscapers and pool companies have winter. Roofers can plan around storm season. Cleaning companies might avoid the end of the month, when move-out cleans pile up.
- Avoid month-end and payroll days. Your bookkeeper will thank you.
- Start midweek. A Tuesday or Wednesday switch gives you a few working days to fix problems before the weekend, and avoids Monday's backlog.
- Check your old contract. Note the renewal date, how much notice you must give and whether you keep access to your data after you cancel. Don't let an auto-renewal set your timeline.
Inventory everything the old system holds
Make a list. This table covers what most home service businesses have:
| What | Why it matters | Watch for |
|---|---|---|
| Customers and contacts | The core of everything | Duplicates and old phone numbers |
| Service addresses | Landlords and property managers may have many | One customer with many locations |
| Equipment and history | Techs need make, model, serial and install date on site | Details buried in notes, not proper fields |
| Job history, notes and photos | Warranty work and repeat visits | Photos and attachments may export separately |
| Scheduled appointments | Jobs already booked | Decide which system finishes them |
| Recurring jobs and memberships | Revenue you've already sold | Renewal dates and visits remaining |
| Open estimates | Work you might still win | Follow-up dates |
| Unpaid invoices | Money you're owed | Agree a plan with your bookkeeper |
| Price book | What techs quote from | A good moment to clean it up |
| Stored cards and autopay | Recurring billing | May not transfer (see below) |
| Tags and lead sources | Your marketing tracking | Several names for the same source |
| Forms and checklists | Inspections, safety and job sign-off | Need rebuilding |
| Automations | Reminders, review requests, follow-ups | Easy to forget until they stop |
| Integrations | Accounting, phones, website forms, marketing | Each needs reconnecting |
| Templates | Estimate terms, emails and texts | Copy the wording before you lose access |
The automations are the ones that bite. If your old system quietly sends appointment reminders and review requests, those stop the moment you switch unless you set them up again.
Export early and check what you get
Run a test export in the first week of planning, not the week of the switch. Open the files and check:
- Does it include every field you need, or only some?
- Are notes, photos and attachments included, or do they need a separate download?
- Can you export job history and invoices, not just the customer list?
Ask your current provider exactly what a full export includes and how to request one. Save the raw files somewhere safe and never edit them. Work on copies.
Clean the data before you import it
Moving messy data into a new system just gives you a messier new system.
If your price book needs work, see how to build a price book your team will actually use.
Map the fields and run a small test import
Match each column in your export to a field in the new system. Then import a small batch, around 20 to 50 records, chosen to cover the awkward cases:
- A landlord with several properties
- A membership customer with a visit due next month
- A commercial account with a separate billing contact
- A customer with equipment history and photos
Open each record in the new system, including on a tech's phone. If they look right there, you're ready for the full import. If not, fix the mapping and try again. It's much easier to fix 30 records than 3,000.
Decide how to cut over
| Approach | How it works | Good for | Risk |
|---|---|---|---|
| Hard switch | Everything moves on one day | Small teams with simple setups | Little time to fix surprises |
| Finish old, start new | Jobs booked before the date finish in the old system; everything new goes into the new one | Most service businesses | Two systems running for a few weeks |
| Long parallel run | Both systems used for everything | Rarely worth it | Double entry, confusion and records that don't match |
For most businesses, "finish old, start new" is the safest. Pick a date. From that morning, every new booking goes into the new system. Jobs already scheduled in the old system finish there. Within a few weeks, the old system has nothing left to do.
Money needs extra care
- Accounting. Set a clear cutoff date so invoices don't sync into your books twice. Agree with your bookkeeper how unpaid invoices will be handled: collected in the old system, or moved across as opening balances. See bookkeeping basics for contractors.
- Stored cards and autopay. Card details are usually held by the payment processor as a secure token, not by the software itself. Moving them to a new processor may need a transfer between the two companies, and not every provider supports one. If they can't move, customers on autopay will have to enter their details again. Ask both providers early, and plan a clear, friendly message for the customers affected.
Train people by role
Nobody needs to learn every screen. They need to learn their part.
- Techs (about 30 minutes each, on their own phone). Seeing the day's schedule, opening a job, reading history and notes, adding photos, completing checklists, building an estimate from the price book, taking payment and closing the job. Finish with a practice job from start to finish.
- Office and dispatch. Booking, scheduling and rescheduling, sending invoices, handling payments and running the daily reports.
- Owner. Reports, user permissions and the settings only you should change.
Name one person as your in-house expert and give them extra time with the vendor's support team. Make a one-page cheat sheet for techs covering the five things they'll do every day.
Update every link and connection
This checklist covers the things customers notice first:
A week-by-week plan
Imagine a four-tech HVAC company switching during its spring lull. Its plan might look like this:
| When | What happens |
|---|---|
| Three weeks before | Confirm contract dates. Run a test export. Write the must-have list. Open the new account. |
| Two weeks before | Clean data. Build the price book, templates, forms and automations. Map fields and run the test import. |
| One week before | Train techs and office. Prepare the website and Google profile link changes. Tell autopay customers if their details need re-entering. |
| Switch day (a Tuesday) | Final import. New bookings go into the new system. Update links. Fifteen-minute team check-in at the end of the day. |
| First week after | Fifteen-minute check-in every day. Keep a running fix list. Confirm reminders, invoices and payments are working. |
| Two to four weeks after | Old jobs finished. Unpaid invoices collected or moved. Final full export saved. Old system cancelled. |
A plumbing shop, a cleaning company or a pest control business would follow the same shape. What changes is the slow season you pick and which records matter most: recurring visits for a cleaner, service agreements for pest control, equipment history for HVAC.
The first week: what to watch
Each day, check:
- Did every appointment reminder go out?
- Did every completed job get invoiced?
- Are payments arriving and matching invoices?
- Are techs adding notes and photos?
- Did any calls or form requests fall through the gap?
Fix problems the same day and keep a list. Most issues show up in the first few days, and the team check-in is where you'll hear about them.
When to cancel the old system
Only after:
- All old jobs are finished and invoiced
- Unpaid invoices are collected or moved
- Memberships and recurring jobs are running in the new system
- You've saved a final full export, including the invoice records your accountant may need
Ask your accountant how long you need to keep old records.
Mistakes that cost owners days
- Switching in peak season
- Importing messy data and planning to fix it later (later rarely comes)
- Forgetting automations that ran quietly in the background
- Skipping tech training because the app "looks simple"
- Changing processors without telling autopay customers
- Cancelling the old system before the last invoice is paid
If you're still deciding what to switch to, read all-in-one platform or best-of-breed tools? and how field service software is priced first.
A switch is also a good time to check the parts customers see before they ever reach your software, like your website and your Google profile. Zome's free AI report gives you a quick read on those while you rebuild the back office.
