Changing field service software feels bigger than it is—until you start moving data. Customers, open jobs, recurring visits, and invoice history are the nervous system of your business. Migrate the wrong things first (or skip cleanup) and y
Changing field service software feels bigger than it is—until you start moving data. Customers, open jobs, recurring visits, and invoice history are the nervous system of your business. Migrate the wrong things first (or skip cleanup) and you will spend months fixing records instead of running routes.
This guide is a practical migration map for teams leaving Jobber, ServiceTitan, Housecall Pro, Workiz, or a spreadsheet-and-calendar stack. It focuses on what to move, in what order, and what you can safely leave behind—without inventing horror stories or miracle timelines.
Why migrations fail (and how to avoid it)
Most painful cutovers share the same patterns:
- Exporting everything "just in case," then drowning in duplicate and junk records
- Going live before techs know where tomorrow's jobs live
- Moving open work without addresses, windows, or notes
- Forgetting recurring service agreements until customers call asking where the tech is
- Running dual systems for too long with no single source of truth
A better approach: migrate the operating core first, clean as you go, then bring historical depth in phases.
The migration priority stack
1. Customers and properties (non-negotiable)
Start here. Everything else hangs off the customer record.
Bring over:
- Customer / company name
- Primary phone and email
- Service address(es) and billing address if different
- Gate codes, pet notes, access instructions
- Tags or service type preferences (pool, lawn, HVAC, etc.)
- Active vs. inactive status
Clean before you import: merge obvious duplicates, fix blank phones, standardize address formatting, and archive customers you have not served in years (unless you need them for warranty or marketing later).
2. Open and upcoming jobs
Your week cannot slip. Migrate:
- Scheduled jobs for the next 2–4 weeks (minimum)
- Assigned tech / crew if known
- Appointment windows
- Job type and short scope
- Quoted amount or rate if already agreed
- Critical notes (parts ordered, warranty, HOA rules)
If your old system export is messy, rebuild the next two weeks manually in the new tool from a printed or exported calendar. Accuracy beats a broken bulk import for near-term work.
3. Recurring services and agreements
Route businesses live or die on recurrence. If weekly pool cleans, biweekly lawn visits, or maintenance plans do not come over cleanly, your board goes empty overnight.
Capture for each agreement:
- Customer and property
- Frequency and preferred day / window
- Service package or line items
- Price and billing cadence
- Next visit date
- Special instructions
Even if you recreate agreements by hand for your top accounts first, do it before cutover day.
4. Quotes in flight
Anything still awaiting approval should move—or be re-sent from the new system with the same pricing. Lost quotes are quiet revenue leaks during a switch.
5. Unpaid invoices and credits
Cash does not care that you changed software. Bring:
- Open invoice balances
- Invoice numbers (or a clear cross-reference)
- Due dates
- Customer linkage
- Credit memos / deposits on account
Historical paid invoices can wait for a phase-two import if time is tight—unless your bookkeeper needs them inside the FSM for customer statements.
6. Job / service history (phase two is OK)
Techs love history on-site: prior repairs, chemical logs, equipment models, callback notes. Ideal to have on day one; acceptable to layer in during weeks 2–4 if cutover pressure is high.
Prioritize history for:
- High-value accounts
- Warranty-heavy work (HVAC, equipment)
- Pool chemistry and equipment records
- Anything with open issues or unfinished punch lists
7. Price lists, templates, and services catalog
Standard services, packages, and templates save quoting time. Migrate or rebuild your top 20 services before worrying about rarely used SKUs.
8. What you can often leave behind (at first)
- Old marketing lists with no phones
- Years of completed jobs with no notes
- Unused custom fields
- Abandoned leads from three seasons ago
- Duplicate "test" customers from training
Archive exports for compliance and taxes; do not pollute the new CRM with them on day one.
Competitor-agnostic export checklist
Regardless of whether you are leaving Jobber or another platform, gather:
| Data set | Preferred format | Owner |
|---|---|---|
| Customers / clients | CSV | Office lead |
| Properties / locations | CSV | Office lead |
| Upcoming schedule | CSV or PDF print | Dispatcher |
| Recurring / memberships | CSV or manual list | Owner |
| Open invoices | CSV + totals reconcile | Bookkeeper |
| Service list / rates | Spreadsheet | Owner |
| Equipment / pool assets | CSV if available | Ops |
Always keep a dated archive of the original exports. If something imports wrong, you need the source file—not a fuzzy memory.
A clean cutover plan (two weeks)
Week −2: Decide and freeze scope
- Pick go-live date (mid-week is often gentler than Monday)
- Name a migration owner (one person, not "the whole office")
- List must-have data for week one of live ops
- Tell the team: new jobs after date X are entered only in the new system
Week −1: Import, map, verify
- Import customers; spot-check 20 random records
- Load recurring work and next week's schedule
- Rebuild user accounts / tech access
- Run a shadow day: office uses new system while old system remains read-only backup
- Train techs on "where is my day?" and how to close a job
Go-live week
- Morning huddle from the new calendar only
- Old system: view-only for history lookups
- End-of-day: reconcile completed jobs and invoices created
- Capture a "bug / missing data" list daily; fix in batches
Week +1 to +3: Deepen history
- Import or paste critical job history
- Attach equipment / dosing records where relevant
- Turn on SMS reminders and customer portal once the core is stable
- Turn off old-system login access when the team stops needing it
People and process matter more than the CSV
Software switches fail socially as often as technically:
- Techs need a simple phone or portal path to see jobs and notes
- Office needs a rule: no scheduling in texts after go-live
- Customers usually need zero fanfare—unless invoice branding or pay links change, in which case send a short heads-up
- Bookkeeper needs to know where invoices and payments will live going forward
Budget training time. A two-hour walkthrough beats three weeks of "I still use the old app."
How CrewField approaches imports
CrewField is designed for field teams that need customers, jobs, quotes, invoices, calendar, and routes in one place—and it supports importing clients and fuller databases from spreadsheets and other field-service tools (including common platforms teams leave behind). The point of a migration is not to recreate every historical click; it is to keep tomorrow's routes, billing, and customer context intact.
If you are planning a switch, review import and ops capabilities on CrewField features and the straightforward unlimited-team pricing so cost is not a per-seat surprise mid-migration.
Migration red flags (pause and fix)
- Upcoming week has jobs without addresses
- Recurring accounts missing next service dates
- Techs cannot log in on a phone they actually carry
- Open invoice totals do not reconcile to your books
- Nobody owns the cutover checklist
Fix those before you celebrate the new login screen.
Bottom line
When switching from Jobber or any FSM, migrate in this order: customers → near-term jobs → recurring agreements → open money → rich history. Clean duplicates early, run a short shadow period, and make the new system the only place schedules change.
Do that, and the software change becomes an operations upgrade—not a month of "where's the Smith job?"
