How to switch field service software without downtime: a week-by-week plan
A vendor-neutral plan for moving your contracting business to new field service software. A six-week timeline, a data checklist covering customers, open work, agreements, price book, photos, cards, phone numbers and web forms, a go-live week plan, crew training and the first 30 days.
By The Revcore team
Reviewed by Hayden Mitchell, founder
Updated 12 min read
Quick answer
How do you switch field service software?
Pick a cutover date outside your busy season, export everything from the old system, clean and import it, then rebuild your price book, automations, payments and web forms. From cutover day, start all new work in the new system and let open jobs finish in the old one. Cancel only after one job runs end to end.
Most contractors stay on software they have outgrown for one reason: switching sounds risky. The fear is losing years of customer history, dropping a job in the middle of a busy week, or watching the crew stall while everyone learns a new app. Those risks are real, but they are planning problems. Done in the right order, a move costs a few weeks of two subscriptions. Staying on the wrong tool costs you retyping and missed follow-ups every day.
This guide is vendor-neutral. It works whether you are leaving a spreadsheet, a quoting app, or a full platform. If you are leaving ServiceTitan or Jobber specifically, our guide to leaving ServiceTitan or Jobber covers their contract terms and export steps. Use this one for the plan, that one for the vendor details.
Before you start: three decisions
Make these three calls before anyone exports a file.
- Your cancel date. Find your renewal date, notice period and whether you prepaid. Your whole timeline works backward from this date.
- Your cutover date. The day new leads, estimates and jobs start living in the new system. Avoid your peak: an HVAC shop skips the first heat wave, a roofer skips the weeks after a hail storm, a remodeler avoids the week three big jobs start. A Tuesday is better than a Monday.
- Your owner for the switch. One person, usually the office manager or operations lead, owns the checklist and has the authority to make small calls without a meeting. Give them protected hours each week.
The week-by-week plan
This is an illustrative example for a $2M to $30M shop with a few crews, a couple of sales reps and an office. A smaller shop moving off a spreadsheet can compress it into three weeks. A shop with hundreds of service agreements and a large price book should stretch it.
| Week | Office and owner | Sales and field | Done when |
|---|---|---|---|
| Week 1: plan and export | Confirm dates. Export everything on the checklist below. List every automation, integration and web form. | Ask reps and crew leads what they use daily. | Exports are saved and row counts match. |
| Week 2: clean and import | Clean, import customers and history, spot-check 20 records. | Crew leads list open jobs to finish in the old system. | Any past customer shows the right address and history. |
| Week 3: rebuild setup | Rebuild the price book as catalogs and estimate templates. Set up payments, invoicing and service agreements. | One rep builds three real estimates in the new system. | A rep can produce a correct estimate without asking the office. |
| Week 4: automations and training | Rebuild follow-ups, reminders and review requests. Test each on your own phone. Start any phone number port. | Train office first, then reps, then crews, each in their own short session. | Everyone has done their daily task once in the new system. |
| Week 5: go-live | Cutover day. Repoint web forms and lead sources. Freeze new records in the old system. | New jobs run in the new system. Open jobs finish in the old one. | One job has gone from lead to payment in the new system. |
| Week 6 and after: overlap and cancel | Close out old invoices, reconcile payouts, take a final export, cancel in writing. | Crews stop opening the old app. | The old system has no open work and your final export is saved. |
The data checklist
Export everything while you still have full admin access. A warranty claim on a roof you replaced four years ago, with no job history, costs far more than a spreadsheet in a shared folder.
| Data | How it usually moves | What to check |
|---|---|---|
| Customers and contacts | Spreadsheet export, then import | Row count matches, phone numbers are formatted the same way, service address and billing address did not swap, duplicates merged. |
| Open jobs and estimates | Finish open jobs in the old system; re-enter open estimates you still want to close | Every open estimate has an owner and a follow-up date in the new system. Nothing sold is sitting unscheduled. |
| Job history and invoices | Spreadsheet or report export, imported as history | Past jobs attach to the right customer. Open balances match your accounting system. |
| Service agreements | Export the list, then rebuild each agreement with its renewal date and visit schedule | Every renewal date and next visit is on the calendar. No maintenance customer is skipped. |
| Price book | Rarely imports cleanly; plan to rebuild | Every item your techs and reps actually sell is there with the right price, cost and description. |
| Photos and files | Downloaded job by job or in bulk; spreadsheets do not include them | Signed contracts, change orders and before and after photos for recent and warrantied jobs are saved. |
| Payment methods | Saved cards usually do not transfer between processors | Customers on recurring billing know they will be asked to enter a card again. |
| Phone numbers | Ported, or replaced with a new number | The number on your trucks, website and listings still rings and texts somewhere a person reads. |
| Website forms | Repointed on cutover day | A test lead from every form, booking link and lead source lands in the new system. |
Clean before you import
Every system collects junk: the same homeowner entered three times, test records from the day someone set the old tool up. Import junk and your reps start the new system distrusting it. Spend an afternoon in the spreadsheet merging duplicates and fixing phone formats, then import a small batch, check it, and import the rest.
Service agreements and payment methods
These two are where recurring revenue quietly leaks during a switch. An HVAC shop with, say, 800 maintenance members cannot afford a quarter of them missing a visit because nobody imported the renewal date column. Rebuild each agreement with its renewal date, price and visit schedule, then compare counts. Our service agreement template is a useful reference for what each one should record.
Saved cards are harder. Card numbers are held by the payment processor, not your software, so they do not export to a spreadsheet. Some processors will move card data to another processor through a formal, PCI-compliant request, but many field service tools do not offer this. Plan for recurring customers to enter a card again, and tell them before a charge fails, not after.
Phone numbers and website forms
If customers call or text a number that lives inside your current software, the number is part of the move. The FCC says you can generally keep your number when you change providers in the same area, that simple ports are processed in one business day, and that you should not end service with the old company before starting with the new one (FCC guide to porting). Ask both vendors how numbers inside their software are handled.
Website forms are the most common thing people forget. Cancel the old tool while your contact form still posts to it and new leads land nowhere, often for days before anyone notices. List every form and lead source and repoint each on cutover day.
Go-live week, day by day
By go-live week, setup is done and everyone has logged in. This week is about moving the front doors and proving one job works.
Day before: freeze and announce
Tell the office, reps and crews the rule in one sentence: anything created from tomorrow goes in the new system. Take one last export of new customers and estimates added since week one.
Cutover morning: switch the front doors
Repoint website forms, booking links and lead sources. Submit a test lead from each one and confirm it arrives with the right name, phone and address.
Cutover day: first live estimate
Have your strongest rep build and present the first real estimate in the new system, with the office watching for anything missing from the price book.
Midweek: first scheduled job
Schedule a sold job and send it to a crew. The crew lead clocks in, adds photos and marks it complete from the phone. Fix anything confusing the same day.
End of week: first payment
Send an invoice from the new system and collect a real payment. Confirm the payout lands in your bank account and your bookkeeper can see where it came from.
Friday: 30-minute review
Owner, office lead, one rep and one crew lead. What broke, what is slow, what is missing. Fix the top three before Monday.
Keep the overlap to two to four weeks, and have the dispatcher check both calendars every morning so no crew is double booked.
Training your crew
Adoption is where switches really fail: three weeks in, crews are back to texting photos to the office. Train by role, keep sessions short, and teach only the screens each person touches daily.
| Role | Learn first | Session length |
|---|---|---|
| Office and dispatch | Lead intake, scheduling, sending on-the-way texts, invoicing, taking a payment | Two or three sessions of about an hour, plus hands-on setup work |
| Sales reps | Building an estimate from the catalog, presenting options, getting the signature and deposit | One hour, then three practice estimates on real jobs |
| Crew leads and techs | Seeing today's jobs, clocking in and out, adding photos and notes, marking complete | Twenty to thirty minutes, on their own phone, at the shop |
- Train on their own phone. Install the app during the session, not after.
- Use real jobs. A roofing crew learns faster adding photos to next Tuesday's tear-off than clicking through a demo account.
- Pick one champion per crew. The crew lead who picks it up first becomes the person others ask, which saves the office a dozen calls.
- Retire the old habits on a date. Tell everyone the group text for job photos ends on a specific day. If both ways keep working, people keep using the old way.
What to do in the first 30 days
The first month decides whether the new system becomes how you work or an expensive second place to type things.
| When | What to do |
|---|---|
| Days 1 to 7 | Daily 10-minute check with the office lead. Confirm every lead landed. Fix price book gaps as reps hit them. |
| Days 8 to 14 | Close out open jobs and invoices in the old system. Reconcile payments from both processors. Confirm every service agreement visit for the month is scheduled. |
| Days 15 to 21 | Turn on the follow-ups you tested: estimate reminders, review requests, agreement renewals. Retire the old spreadsheets and group texts. |
| Days 22 to 30 | Take a final export from the old system and cancel it in writing. Hold a 30-day review: what is still done outside the system, and why? |
At the 30-day review, look at plain numbers: leads in, estimates out, follow-ups sent, days to get paid. If a workflow still lives outside the system, find out why. Usually it is a missing catalog item or a step that takes one tap too many.
Who actually does the migration work
Pin every vendor down on this before you sign. "We have an import tool" is not the same as "our team moves your data with you." Ask these questions in the demo:
- Who does the import: your team, their team, or a paid partner? Is it included or billed separately?
- Which data types import directly, and which have to be rebuilt by hand?
- How do phone numbers and texting move, and how long does a port take on their side?
- Can you run a trial with your own data before you commit?
For Revcore, setup and migration help is included on paid plans, and on the Scale plan Revcore imports your QuickBooks Online customers and invoices, so you are not retyping your customer list. A 14-day free trial with no credit card lets you set everything up in parallel before you cancel anything. For the wider buying process, see our contractor software buyer's checklist.
Frequently asked questions
How long does it take to switch field service software?
For most contractors with a few crews and an office, plan four to eight weeks from the first export to cancelling the old system. That covers exporting and cleaning data, importing, rebuilding the price book and automations, training, go-live and a two to four week overlap. A small shop moving off spreadsheets can often do it in three weeks.
Will I lose my customer history when I switch?
Not if you export it yourself before you cancel. Customers, jobs, estimates and invoices usually export to spreadsheets and can be imported as history. Photos and signed documents are usually separate downloads, so save them for recent and warrantied jobs. Keep your final exports in a shared folder even after the switch.
Should I move jobs that are already in progress?
No. Let jobs that started in the old system finish there, including their invoices and payments. Start every new lead, estimate and job in the new system from your cutover date. Moving work mid-flight is how jobs get dropped or double billed, and the short overlap costs far less than one lost job.
When is the best time of year to switch?
In your slowest stretch. For HVAC that is usually spring or fall between heating and cooling peaks. Roofers and exterior contractors often switch in late fall or winter. Plumbers and electricians have steadier demand, so they pick a month without big projects starting. Whatever the trade, avoid cutover right after a storm or during a promotion.
How do I get my crew to actually use the new software?
Train by role, on their own phones, using real jobs. Crews only need to see their jobs, clock in and out, add photos and mark work complete. Pick one champion per crew, answer common questions once in writing, and set a date when the old group texts and paper forms stop.
Further reading: the FCC's guide to keeping your phone number explains porting rules. If you are still deciding whether to move, the signs you have outgrown your software is a useful gut check, and what contractor software really costs covers the budget. For vendor-specific steps, see leaving ServiceTitan or Jobber.
Written by the Revcore team. Reviewed by Hayden Mitchell, founder of Revcore Pro, who closed $3.5M of home improvement door to door and helped scale a contractor from $1M to $10M.
