Many field service software vendors say data migration is included, and that often means something narrower than you’d assume. “Included” usually covers a spreadsheet import of customers and a few other lists, in the vendor’s template, with your data uploaded as you hand it over. Moving job history, equipment records, attachments and messy data is a different service, and it’s often quoted separately.
This guide is for office and operations managers at commercial trade contractors who are switching systems. It explains the three levels of migration service, shows how one vendor draws those lines in its own contract, and gives you a checklist for scoping the move before you sign. We build Forz, so we say what our included import covers and where it stops.
The three levels of migration service
Vendors use different names, but the work falls into three levels.
| Level | Who does the work | What usually moves | What it usually costs |
|---|---|---|---|
| Self-serve import | You fill the vendor’s templates and upload them | Customers and simple lists such as items or price lines | Usually included in the subscription |
| Assisted import | You fill the templates; the vendor’s team uploads them | More record types (contacts, locations, jobs, assets), loaded as provided | Varies by vendor; ask whether it’s included |
| Paid migration | The vendor’s team maps your old system’s export into the new one | Records from a known source system, mapped field by field | Quoted per project, sometimes under its own contract |
Two things decide which level you need: how many record types you want to move, and how clean they are. A shop moving 600 customers from a tidy spreadsheet can live on self-serve. A shop moving eight years of jobs, equipment and inspection history from another FSM tool is buying a project.
One vendor’s lines, in writing: FieldPulse
FieldPulse publishes its service scope in a Customer Success Agreement, which makes it a useful example of how the three levels look on paper (as of October 22, 2026).
- Self-serve: self-service imports come with the base subscription, but the only self-import options in the web app are the Customer Import Sheet and the Line Item Import Sheet. FieldPulse offers documentation and limited troubleshooting, and doesn’t reformat, clean or reorganize your data.
- Support-assisted: other templates, including contact, location, job, pricebook, custom field and asset sheets, go to FieldPulse support, which uploads the data as provided, with no cleanup or restructuring.
- Paid migration: moving data from a legacy platform is “a paid service.” Before it starts, FieldPulse sends a Data Migration contract that sets out how fields will map and any costs. The agreement lists customer records, locations and jobs as generally supported, says files, attachments and images are generally not supported, and puts data review before go-live on the customer. Even on the paid service, the agreement says FieldPulse migrates data “as-is” and doesn’t reformat, clean or de-duplicate it.
FieldPulse doesn’t publish a price for the migration service. Our FieldPulse pricing guide covers its onboarding format and contract terms in full.
None of this is unusual. It’s just written down, which is what you want from every vendor on your shortlist.
What “free migration” usually leaves out
When a quote says migration is included, check these five gaps.
- History. Closed jobs, past invoices and old inspection results are often out of scope, or only in scope on the paid level. Decide whether you need them in the new system or only need to keep them somewhere you can find them.
- Attachments. Photos, signed work orders, PDFs of inspection reports and customer documents rarely move with a spreadsheet import. If your compliance records live as files, plan where they’ll be kept.
- Cleanup. Many vendors import what you give them. Duplicate customers, addresses that won’t map, and techs entered three different ways all come across as they are.
- Mapping. Your old system’s “Site,” “Location” and “Service Address” may need to land in one field. Someone has to decide that. On the self-serve level, that someone is you.
- Re-runs. If the first import is wrong, ask whether a second attempt is included or billed again.
Scope it before you sign: a data inventory
List every data set before the demo turns into a quote. Then decide what moves and at which level.
| Data set | Typical source | Move or archive? | Level it usually needs |
|---|---|---|---|
| Customers and billing contacts | Old FSM, accounting system | Move | Self-serve |
| Sites and service addresses | Old FSM, spreadsheets | Move | Self-serve or assisted |
| On-site contacts | Old FSM, techs’ phones | Move | Assisted |
| Open jobs and scheduled visits | Old FSM | Move | Assisted |
| Service agreements and recurring schedules | Old FSM, spreadsheets | Move (often rebuilt) | Assisted or manual setup |
| Equipment and assets | Old FSM, inspection binders | Move if you inspect or maintain it | Assisted or paid |
| Price list and items | Accounting system, price book | Move | Self-serve |
| Closed jobs and invoices | Old FSM, accounting system | Usually archive | Paid, if moved |
| Attachments and reports | Old FSM, shared drives | Archive, link if needed | Rarely supported |
For what to clean in each data set and when, see the data preparation checklist in our implementation plan.
If your accounting system syncs with the new software, customers and items may come across through the sync rather than an import. Pick one system as the source of truth for customers before you import anything, or you’ll create duplicates on the first sync.
Field-mapping checklist
Whichever level you buy, someone maps old fields to new ones. Use this list to make sure it’s done before the import, not after.
- One customer, one record. Merge duplicates in the source first. Decide how parent companies and their sites relate.
- Address format. Street, city, state and ZIP in separate columns. Fix addresses that won’t geocode, or routing and maps will be wrong from day one.
- IDs you’ll keep. Carry over the old customer or site number in a reference field so staff can search by it.
- Status values. Translate the old system’s job statuses to the new list. Don’t import ten old statuses you no longer use.
- Equipment fields. Make, model, serial number, location in the building, and install date, one row per unit.
- Custom fields. List each one, decide whether it’s still needed, and create it in the new system before the import.
- Tax and price fields. Match item names and tax settings to your accounting system.
- Dates. Agree on one date format. A day-month swap on next service dates causes missed visits.
- Test file. Import 20 to 50 real records first and check them on screen and on a tech’s phone.
The order of work
We won’t put a duration on this, because it depends on your data and on the vendor. Ask each vendor for a target date in writing, based on your files. The order of work is the same everywhere.
- Export everything from the old system and save a full copy you’ll never edit.
- Clean and map the data sets you’re moving, using the checklist above.
- Run a test import and have the office and one tech check it.
- Fix the source files, not the imported records, and re-run if needed.
- Freeze changes in the old system, run the final import, and spot-check counts (customers, sites, open jobs) against the export.
- Set the old system to read-only so nobody keeps a second schedule.
Our implementation plan covers configuration, training by role and go-live checks around these steps.
Questions to get answered in writing
- Which record types are included at no extra cost, and on which level (self-serve, assisted, paid)?
- Which source systems does the vendor support for paid migration?
- Is the migration price fixed or estimated, and what changes it?
- Does the scope include closed jobs, invoices, equipment and attachments?
- Who cleans and de-duplicates the data?
- How many test imports and re-runs are included?
- Who signs off that the data is right, and what happens to errors found after go-live?
Migration is one of several lines that can sit outside the subscription. Our hidden fees guide covers the others, and our guide to field service software pricing models explains how the subscription itself is counted.
Where Forz fits, and where it doesn’t
Free standard data import covers one standard import of your customers, contacts, sites, and active jobs using the templates we provide. Larger or custom imports (for example, complex historical data or non-standard formats) can be quoted separately. Our team will tell you upfront which path fits your data. Every new Forz customer also gets guided onboarding: we’ll configure the platform for your workflows and train your office staff and field techs, included in your plan at no extra charge (Forz pricing).
Forz costs $50 per user per month billed annually, or $60 month-to-month, with a 10-user minimum. On annual billing you can add users anytime, and removing users lowers the bill at renewal. For larger teams, Forz offers volume discounts through sales.
Forz isn’t the simplest choice if:
- You need years of closed jobs and attachments moved. That’s outside the standard import, so expect a separate quote.
- You have fewer than 10 people. You’d pay the 10-user minimum, though new customers under 10 people with up to $1M in revenue can apply for the Small Business Program.
If you’re comparing Forz with FieldPulse, see Forz vs FieldPulse or our FieldPulse alternative page. For a wider shortlist, see our field service software roundup.
FAQ
Is data migration free when you switch field service software?
Usually part of it is. Many vendors include a self-serve import of basic lists such as customers and items. Moving job history, equipment, attachments or data from another FSM system is often a paid service with its own scope. Ask which record types are included and at which level.
What data should I move to new field service software?
Move what your team uses every week: customers, sites, contacts, open jobs, service agreements, equipment you maintain and your price list. Archive closed history and attachments in a place you can search, unless you need them in the new system for compliance reports.