Switching field service software without losing data

Why switches go wrong

Owners usually switch field service software because the old system is holding them back: poor reporting, a weak mobile app, rising prices or missing features. The new system is often better. The switch still goes badly when data arrives incomplete, open jobs are lost, agreements stop renewing, technicians are not trained, and the office spends weeks fixing records instead of booking work.

Office time is the hidden cost. US private employers' total compensation averaged $46.89 per hour worked in June 2026^[1], and dispatchers outside police, fire and ambulance services earned a median of $50,340 a year^[2]. Every hour your dispatcher spends re-entering data or calling customers to confirm appointments that disappeared is an hour not spent booking. A careful plan is cheaper than a fast one.

A switch timeline

Inventory the data you must move

• Customers, with all phone numbers, emails, billing contacts and contact preferences, including do-not-contact flags.
• Service locations, with access notes, gate codes and property details.
• Equipment per location: type, brand, model, serial number, install date, warranty end.
• Maintenance agreements: start date, renewal date, visits used and remaining, price and payment method.
• Open jobs and appointments, including estimates awaiting approval.
• Open invoices and receivables, with payments received and balances due.
• Job history: at least dates, work done, technician, invoice totals and notes.
• Price book items, forms, checklists and templates.
• Attachments: photos, signed estimates, inspection reports and documents.
• Recurring schedules for cleaning, pest or lawn customers.

Ask your current vendor for a complete export early, before you announce you are leaving. Some systems export customers and jobs easily but make attachments, agreements or recurring schedules difficult. Knowing that early changes the plan. If call recordings or transcripts are part of the record, check how they will be stored and who may access them; recording laws differ by state and consent obligations still apply^[3].

Map, clean and test

1. 01

   Clean before you move

   Merge duplicates, standardize job types and lead sources, and fill missing fields. Migrating messy data moves the mess; see cleaning up customer records.

2. 02

   Write a field map

   A spreadsheet listing every old field, the new field it goes to, and what happens to values that do not match. Decide what to leave behind.

3. 03

   Import a test set

   Start with a few hundred customers from different types: homeowners, landlords, commercial, agreement members.

4. 04

   Check counts and samples

   Compare totals (customers, locations, equipment, open invoices) and check twenty records by hand, field by field.

5. 05

   Run a full test import

   Repeat with all data, then have office staff try a normal day's work in the test account.

6. 06

   Fix and repeat

   Most companies need at least two full test imports before the data is right.

Cutover day

Pick a slow period for your trade: not the first heat wave for HVAC, not spring for lawn care, not storm season for roofing. Choose a cutover date at the start of a week, so problems surface while the office is fully staffed.

Write the cutover plan as a checklist with a name and a time against every step, and walk through it with everyone involved a few days ahead. Decide in advance who can call off the switch and on what grounds, such as open receivables that do not match or a failed import of appointments. A delayed go-live costs a few days; a broken one can cost weeks.

1. Stop creating new records in the old system at a set time the evening before.
2. Run the final export and import; check counts against the last test.
3. Confirm every open appointment for the next two weeks appears correctly, with the right technician and time.
4. Confirm open receivables match, to the cent, before sending any new invoices.
5. Switch phone integrations, payment links, online booking and review requests to the new system.
6. Tell customers only what affects them, such as a new payment link or portal, and when.

Run in parallel, briefly

A full parallel run, entering every job in both systems, doubles the office's work and rarely lasts. A targeted parallel check works better: for the first two to four weeks, keep the old system read-only and compare a daily sample of jobs, invoices and agreement visits. Each morning, the project owner reviews yesterday's issues, fixes data and notes patterns.

Example: a fictional pest control company with 2,800 recurring customers migrates in early winter. In the first week of parallel checks it finds that 140 recurring services imported on the wrong frequency because one old frequency code had no match. Because the old system is still readable, the office corrects them in an afternoon, before any customer misses a visit.

Train by role, not by feature

Keep sessions short and practical, on the device each person will use. Most technicians already carry smartphones; 91% of US adults own one^[4]. Give each role a one-page cheat sheet, name an in-house champion per team, and schedule a follow-up session two weeks after go-live, when people know what they do not know. See getting techs to use the mobile app for field-specific advice.

Integrations and the things outside the system

The field service system rarely works alone. Accounting, payment processing, the phone system, call tracking, online booking widgets, review requests, email marketing and supplier accounts may all connect to it. Each connection is a small migration of its own, and each one breaks quietly if forgotten: a booking widget that still writes to the old system, a review request that stops sending, invoices that no longer reach accounting.

• List every connection to the old system, who set it up and what it sends where.
• Decide for each one: reconnect to the new system, replace, or retire.
• Test each reconnected integration with a real transaction before go-live.
• Update every link customers use: website booking, payment links, portal links in email signatures and on invoices.
• Cancel the old subscription only after the final export is checked and stored, and note the date your access ends.

Accounting deserves its own check. Agree with your bookkeeper how open invoices from the old system will be collected and recorded, so revenue is not counted twice and payments are not lost between systems.

Adoption numbers to watch

Most small businesses intend to keep adding technology platforms^[5], but a platform only helps if people use it. In the first month, look at adoption by person rather than averages: who closes jobs in the app the same day, who still calls the office to have things entered, which dispatcher still keeps a paper list. Coach individuals rather than retraining everyone.

After go-live

• Track a handful of health checks daily for the first month: jobs created, jobs closed with complete records, invoices sent same day, payments applied.
• Keep a single issue list with owner and status; review it daily, then weekly.
• Rebuild your monthly reports in the new system and compare the first month with the old system's numbers.
• Check integrations with accounting weekly until they are stable.
• Decide how long to keep the old system read-only, then export and archive what you must keep.

Plan for the change to take a few months to settle, and treat this switch as the start of a habit: a clean data model and trained people make the next tool much easier to add. Privacy duties travel with the data too; if state privacy laws apply to your business, record where personal information is now stored^[6].