How to Switch Field Service Software Without Losing History
Your customer history is the real reason you haven't switched yet. Here's how to move it without losing a thing.

You've outgrown the software you started on. The scheduling is clumsy, the invoicing takes too many clicks, and you're paying per user for seats you don't control. But there are six years of customers in there. Every job, every note about which valve is buried behind the shed, every address with a gate code. That history is the reason most owners stay put longer than they should.
Switching field service software without losing your customer history is mostly a decision problem, not a technical one. The export is a Tuesday afternoon. Deciding what deserves to come across, and what should stay behind in the old system, takes longer and matters more.
By the end of this you'll know what to carry over, what to leave, and how long to keep both systems running before you shut the old one off.
Decide what to bring before you touch the export button
Two things are load-bearing: the customer list and the customer history attached to it. Names, addresses, phone numbers, gate codes, which zone controller is in the garage, what you replaced last spring and what it cost. Lose those and you're a new company again. Everything else in your old account is negotiable.
Half-finished quotes nobody followed up on. Leads from three years ago that never answered. Notes that say "call back" with no date. Duplicate customer records where someone typed the same address twice. A data migration is a good excuse to stop carrying that around. You are allowed to leave it behind, and most owners feel better once they do.
Make It Rain is an irrigation company in Fairfield County, Connecticut, with 600-plus customers, a crew, an office assistant, and demand that swings hard with the seasons. They ran on Jobber. When we took the rebuild over on 16 June 2026 as a 13-week project, the first real conversation wasn't about file formats. It was about which records actually earn their seat in the new system.
Do this part this week, before any export. Pull your customer list, sort it by the date of the last completed job, and draw a line. Active customers and their service history come across. Everything past the line sits in a read-only copy of the old data that you keep but don't load.
That one decision shortens the rest of the move more than any technical step.
Ask for a CSV export before you cancel the old account
Cancel first and you may find the door locked behind you. Some platforms keep your account readable for a window after you stop paying, some don't, and a few will only hand you certain record types in certain formats. Find out which kind you're dealing with before the renewal date, not after.
Start with the self-serve export in your account settings and see what it actually gives you. If customers come out clean but job history or invoices don't, or if the only option is a PDF, you need a written request on record.
Send something like this to support:
> Hi, I'm planning a data migration off the platform and need a full export of my account data before I cancel. Please send customers (name, address, phone, email), complete service and job history, and all invoices with line items and payment status, in CSV format. Please confirm how long my account stays accessible after cancellation and whether any of this data cannot be exported. Thanks, [Your name], [account/company name]
Put it in writing so there's a timestamp. Ask for CSV specifically, because that's what imports; a PDF of your invoice list is a filing cabinet, not data.
Then download everything and keep a copy on a drive you control. Do that before you cancel anything.
How long a data migration takes for a shop your size
Plan in months, not weekends. We took on a rebuild for an irrigation company in Fairfield County, CT, with 600-plus customers, seasonal recurring work and an office assistant, all of it running on Jobber. We scoped it as a 13-week project starting 16 June 2026. Those 13 weeks are a few weeks of pulling and sorting data, a build, then a stretch where both systems run side by side. Almost none of it is typing.
If you're smaller, it's shorter. But any data migration onto new field service software still needs room for a full billing cycle to run twice.
First few weeks: pull the service history and decide what stays
Start with the customer list. Export it, open it in a spreadsheet, and sort by last job date. The names at the top are your business. The ones at the bottom haven't called in years, and some of them have a phone number that stopped working two phones ago.
Then pull the service history and read it. Pull a sample, not the whole set. Pick twenty customers and look at what the old system actually stored for each job. You'll usually find three kinds of records: complete ones, ones with a date and nothing else, and duplicates created when someone typed a name twice.
Sort them into keep, clean up, and leave behind. Half-finished records are rarely worth the hours it takes to fix them.
While you're in there, write down how the new system wants the data arranged, because a field service app and a bigger ERP each ask for it a different way. Customer, property, job, invoice. If one customer has three addresses, decide now whether that's three properties or three customers, because the import will ask.
The parallel run — both systems live through one full billing cycle
Cold switches fail on the things nobody remembers. A recurring billing rule that fires on the 1st. A seasonal customer who gets scheduled every April without anyone touching the calendar. Those stay hidden in testing, because nobody thinks about them until the day they're supposed to happen.
So keep the old system running. Do your scheduling in the new one, but leave the old one open and billing as it always has, through at least one complete cycle. If your invoices go out monthly, that's a month. Seasonal work may need longer.
A parallel run means someone compares the two once a week. Did every job on the new calendar exist on the old one? Did the same invoices go out, for the same amounts, to the same people? When the two lists match for a full cycle, you're clear to shut the old one down.
Yes, it's double work for a few weeks. The office manager will feel it most, so tell them up front what you're asking and why.
The alternative is finding out in July that a contract customer hasn't been billed since May.
Check the customer history landed right in the new system
An import that finishes without an error message is not the same as an import that worked. Sit down with both systems open and count.
Start with the customer list. Pull the total from the old system and the total from the new one. For a shop like Make It Rain, with 600-plus customers on the books, those two numbers should match, and if they don't, the gap tells you something: a filter you forgot, inactive records the import skipped, or a file that cut off partway through. Find the missing names before you move on.
Then check the links. A customer record on its own isn't much use. Each one needs to be attached to the right property, the right zone or system, and the right service history. Spot-check twenty accounts by hand: a few big ones, a few small, a few with multiple addresses. Open each and ask whether the jobs listed under it are actually that customer's jobs.
Next, hunt duplicates. Imports create them, especially when a name was spelled two ways in the old system. Sort by last name and by phone number and look for repeats. Merge them now, while nobody is billing against them.
Last, pick three customers with long customer history and read it start to finish in the new system. Read the story: what was installed, what failed, what was fixed. If it makes sense, the data landed. If it reads like gaps, you have more work before a live job goes through it.
Photos and notes your technicians took usually don't import
Most data migration tools move customers, jobs, invoices and maybe quotes. They do not move the photo your tech took of a corroded backflow in 2021, the internal note that says "customer's dog bites," or the line-level labor breakdown under an old invoice. Those live in the old vendor's storage, and there is often no export for them at all.
Don't fight that. Keep the old account open in read-only mode for a stretch after you go live. A season, a year, however long your work cycles. Ask the vendor what the cheapest plan is that still lets you log in and look things up. Then tell the office and the technicians: new work goes in the new system, old photos get looked up in the old one.
For the handful of accounts where the detail really matters, move it by hand. Big installs, warranty work, anything with a history of failures. Download the photos, save them to a folder named for the customer, and attach them to that customer's record in the new system.
The rest can sit in the archive. Service history that nobody has opened in four years does not need to make the trip.
Tell your customers before you flip the switch
Stored cards usually don't come with you. If the old system used one payment processor and the new one uses another, the saved card numbers stay behind, and anybody on recurring billing has to put their card in again. Find out from both vendors whether the tokens can transfer before you plan anything. If the answer is no, you need a week to collect them.
Keep the message short. A text or a plain email is enough: we're moving to a new system, your invoices will come from a different email address and look a little different, here's the link to put your card back on file. Send it to the customers on recurring billing plans first. Everyone else just needs to know the invoice looks different so it doesn't get marked as spam or ignored.
Have the office watch for bounces and replies the same day it goes out. Some customers will call to make sure the link is real. That call is a good sign. It means they read it.
One system beats stitching tools back together after the move
The migration is the easy part to plan. What comes after it is where shops lose time: a texting app that doesn't know which job it's texting about, a scheduling board that lives apart from the invoices, photos sitting in a phone gallery because the field service software had nowhere to put them. Every gap between two tools is a place where something falls through, and the office ends up copying information by hand to hold it together.
We build it so those pieces land in the same place. The text that goes out when a call gets missed, the scheduling and dispatch board, what technicians capture on site, the job documentation, the invoice that follows: one system, one customer record. Nothing to reassemble once the data is in.
Make It Rain is the shape of this at real scale. An irrigation company in Fairfield County, Connecticut, 600-plus customers, seasonal work that comes back every spring, an office assistant running the phone, all of it on Jobber. We took the rebuild over on 16 June 2026 as a 13-week project. The customer list and service history were the load-bearing parts, and the work was as much about deciding what to carry as it was about moving it.
If you're weighing how to switch to new field service software without losing your customer history, start with the question of what's actually worth keeping. Most shops find the answer is smaller than they feared, and the half-finished records from the old system were never going to help anyone anyway.
If you want to talk through what your move would look like, book a New Project Consultation.
Keep Reading
More Practical Reading.
Real articles on business systems, websites and automation.
