Key takeaways
- Switch in your slowest month, and plan eight to twelve weeks from signed contract to go-live for a small or mid-sized shop.
- Clean customer, equipment and price book data before import; moving bad data only makes it harder to fix later.
- Run at least one full test import and a short parallel period with real jobs before cutover.
- Keep customer-facing details stable: the same phone number, texting number and payment experience wherever possible.
- Keep a complete export of the old system for as long as your record-keeping rules require.
Is it time to switch?
Changing field service software is disruptive, so be sure the problem is the software and not the way it is set up. Many shops that want to switch have never had their current system configured properly. Before you leave, ask your current vendor for a setup review and see whether the pain points can be fixed.
- Switch when the system cannot do something you need, such as job costing, multiple locations or a usable mobile app, and the vendor has no plan to add it.
- Switch when pricing has outgrown its value at your headcount.
- Switch when support is consistently slow during your busy season.
- Do not switch only because a competitor uses something else or a sales rep offered a discount.
Small businesses are changing their technology more often. The US Chamber of Commerce found that 84% of small businesses plan to increase their use of technology platforms, and that small business use of generative AI rose from 23% in 2023 to 58% in 2025[1]. More tools means more integrations to move when you switch, so list them early.
The migration plan
Week 1: name an owner and a date
Pick one person inside the company to own the project, and set a go-live date in your slowest period. Put blackout dates on the calendar for anyone key to the switch.
Weeks 1 to 2: inventory your data and tools
List every type of data in the old system and every tool connected to it: accounting, payments, phones, marketing, review requests and the website booking form.
Weeks 2 to 4: clean the data
Merge duplicate customers, fix addresses and phone numbers, close stale open jobs, archive customers you will never contact and tidy the price book.
Weeks 3 to 6: configure the new system
Set up job types, tags, price book, tax settings, forms, user roles and notification templates. Decide naming conventions before anyone starts typing.
Weeks 5 to 7: test import
Import a full copy of your cleaned data, then check 30 random customers, 10 maintenance agreements and the price book line by line against the old system.
Weeks 7 to 8: train and run in parallel
Train the office and techs, then run a few days of real jobs in both systems to find gaps.
Cutover weekend
Freeze the old system on Friday evening, run the final import, test with one live job on Saturday and go live on Monday.
Weeks 9 to 12: stabilize
Hold a daily 15-minute check for two weeks, log every issue and fix the top three each week.
What data to move, and how
| Data | Move it? | Cleanup before import | Watch out for |
|---|---|---|---|
| Customers and service addresses | Yes | Merge duplicates; separate billing and service addresses; fix phone formats | Landlords and property managers with many service addresses |
| Equipment records | Yes | Check water heater brand, model, size and install date | Free-text notes that need splitting into fields |
| Maintenance agreements | Yes, with next visit dates | Confirm active members, renewal dates and visits remaining | Agreements billed outside the system |
| Price book | Yes, after review | Remove dead items; update material costs and labor rates | Task codes that the new system formats differently |
| Open jobs and estimates | Yes, recent ones | Close or cancel stale ones first | Deposits already taken on open estimates |
| Job history | Summary or attachments | Decide how many years to import | Photos and attachments that may not transfer |
| Invoices and payments | Usually stays in accounting | Reconcile before cutover | Unpaid invoices that need follow-up after the switch |
Ask the new vendor exactly which fields their import tool accepts before you clean anything. Clean data into their format once, not twice.
Integrations and the cutover checklist
Integrations are where switches most often break on day one. Every tool that reads from or writes to the old system needs a new connection, a test and an owner. Work through the list in the week before cutover and tick each item only after a real transaction has passed through it.
- Accounting: map income accounts, tax codes, items and customers, and decide the date from which invoices sync from the new system.
- Payments: confirm the processor, deposit timing and how refunds and partial payments appear.
- Phones and texting: point call routing, missed-call texts and appointment reminders at the new system.
- Website: update booking forms and any embedded scheduling widget, and test a booking end to end.
- Marketing and reviews: reconnect review requests, email lists and any lead sources that create jobs.
- Reports: rebuild the five reports you check every week, and compare them with the old system for the same period.
- Access: set user roles, remove shared logins and turn on multi-factor authentication for admins.
Keep the customer experience stable
Customers should notice the switch only because things got better. The most common mistake is changing the number that texts and calls customers. Pew found that 80% of Americans don't generally answer cellphone calls from unknown numbers[2], and a new texting number looks unknown. Keep the same business number for calls and texts, or port it to the new system, and test arrival-window texts on staff phones before go-live.
- Keep the same booking link on your website, or redirect the old one.
- Match the old confirmation and reminder wording as closely as possible at first.
- Check that payment links, receipts and review requests come from your business name.
- Warn maintenance agreement members only if something they see will change, such as a new member portal.
Nearly all customers will see the change on a phone: 91% of US adults own a smartphone[3]. Test every customer message on both iPhone and Android before go-live.
Training that sticks
Train by role and by real tasks, not by menu. Dispatchers need two or three sessions on the board, booking and rescheduling. Techs need one session on the mobile app using a sample job, then a ride-along check in the first week. The office manager or bookkeeper needs a session on invoicing, payments and accounting sync.
- Write a one-page cheat sheet per role with the ten most common tasks.
- Name a super-user in the office and one among the techs who others ask first.
- Run practice jobs in a test environment until each person can complete their top tasks without help.
- Hold short refresher sessions in the second and fourth weeks after go-live to cover questions that came up.
Keep the old data long enough
Before you cancel the old system, take a complete export of customers, jobs, invoices, attachments and reports, and store it in two places. IRS guidance is to keep records for 3 years in most situations, longer in some cases, and employment tax records for at least 4 years after the tax is due or paid[4]. Your accountant and any warranty or licensing rules may require longer.
Source: Internal Revenue Service, 2026[4]
Show the data
| Item | Value |
|---|---|
| Most situations | 3 years |
| Employment tax records | 4 years |
| Unreported income over 25% of gross | 6 years |
| Bad debt or worthless securities claim | 7 years |
Check how long the old vendor will keep read-only access after you cancel, and whether attachments and photos are included in the export. If they are not, download the ones you need for warranty and permit records before the account closes.
Worked example: a ten-week switch
Example: a fictional nine-truck shop signs with a new platform in late January and targets go-live in early April, after the freeze season and before the spring rush. The office manager owns the project. In February she merges about 900 duplicate customers, retires 300 dead price book items and confirms 410 active maintenance agreements. A test import in early March shows equipment notes landing in the wrong field, so the import file is fixed and run again. Techs train on a sample job and ride along with the super-user for two days. Cutover happens over a weekend with one live test job on Saturday. In the first two weeks the team logs 37 issues, most of them notification wording and user permissions, and fixes all but two by the end of the month.
Common mistakes
- Switching in peak season because the contract started then.
- Importing everything as it is, duplicates and all.
- Leaving integrations such as accounting and phones until after go-live.
- Training techs on the office screens instead of the mobile app.
- Cancelling the old system before checking the export opens correctly.
- Letting each person invent their own job types and tags in the new system.
Plan the accounting link carefully; see getting the QuickBooks sync right. If you are still choosing, start with choosing field service software.
Frequently asked questions
How long does it take to switch field service software?
For a small or mid-sized plumbing shop, plan eight to twelve weeks from signing to go-live, including data cleanup, a test import, training and a short parallel run.
When is the best time to switch?
In your slowest month, away from freeze season and summer peaks, so staff have time to learn the new system before the phones get busy.
Can I keep my phone number and texting number?
Usually yes. Keep or port the same business number so customers recognize your texts and calls. Test it before go-live.
What should I do with data from the old system?
Take a complete export, check it opens correctly, store it in two places and keep it for as long as your accountant and record-keeping rules require.
References
U.S. Chamber of Commerce Technology Engagement Center (2025). Empowering Small Business: The Impact of Technology on U.S. Small Business (opens in a new tab) โ
Pew Research Center (2020). Most Americans don't answer cellphone calls from unknown numbers (opens in a new tab) โ
Pew Research Center (2026). Mobile Fact Sheet (opens in a new tab) โ
Internal Revenue Service (2026). How long should I keep records? (opens in a new tab) โ