A ServiceTitan data migration checklist is the ordered plan you use to move customers, equipment, pricebook, and job history out of your old system and into ServiceTitan without losing or corrupting data. The work breaks into five buckets in a deliberate sequence: customers and locations first, then equipment, then the pricebook, then historical records, and finally validation before go-live. Get the order and the cleanup right and your team trusts the system on day one. Skip the cleanup and you import years of bad data that haunts dispatch, invoicing, and reporting.
What data needs to be migrated to ServiceTitan?
Most contractors are moving five categories of data. Each has its own quirks, so treat them as separate workstreams rather than one giant export.
- Customers and locations: names, addresses, phone numbers, email, and the link between a billing customer and its service locations
- Equipment: installed units tied to the right location, with make, model, serial number, and install date
- Pricebook: services, materials, and equipment with pricing, categories, and the structure that drives Estimates
- History: past jobs, invoices, memberships, and service agreements
- Open items: active memberships, recurring service agreements, and any unpaid balances
How do you clean customer and equipment data before importing?
Migration is the one chance to leave junk behind, so clean before you import, not after.
- Deduplicate customers so one homeowner is not three records, which would split their history and break reporting
- Standardize addresses so locations map cleanly and dispatch can route
- Confirm every service location ties to the correct billing customer
- Attach equipment to the right location, not just the customer, because a property manager may own units at many addresses
- Capture serial numbers and install dates wherever you have them, since this drives warranty tracking and future Memberships and Service Agreements
Decide early how far back you go. Importing every dead lead from a decade ago bloats the database. A common approach is to bring active customers and recent history in full, and archive the rest.
How is the ServiceTitan Pricebook handled in a migration?
The Pricebook is its own project, not a side task. ServiceTitan provides Pricebook import templates, and Pricebook Pro can help you build and maintain a structured, well-organized book. Before import:
- Organize services and materials into clean categories so technicians can find them in the field
- Set pricing, and confirm taxable flags and units of measure
- Map your old service codes to the new structure so historical jobs still make sense
- Link equipment and materials correctly so Estimates pull the right items
A messy pricebook is the most common reason a go-live feels chaotic. Invest here.
How much history should you bring into ServiceTitan?
Bring enough history that technicians and CSRs can serve a customer without leaving the system, but not so much that you import noise. Practical guidance:
- Full detail for active customers and recent invoices
- Equipment and install history, since that is what techs rely on at the door
- Open memberships, service agreements, and balances, which must come over accurately because they affect revenue and renewals
- Summary or archive treatment for very old, closed records
History often imports with less structure than live data, so confirm how it displays on the customer record.
How do you validate a ServiceTitan migration before go-live?
Validation is where you catch problems while they are still cheap to fix. Do a test import into a sandbox first, then verify against the source:
- Reconcile record counts: customers in equals customers out
- Spot-check high-value accounts field by field
- Confirm equipment is attached to the correct location
- Create a test Estimate to prove the Pricebook produces correct pricing
- Verify open balances and active memberships match your old system
- Run a Report or Dashboard to confirm the data is queryable
- Have CSRs and techs look up real customers in the mobile app before launch
The honest takeaway
A ServiceTitan migration succeeds or fails on data discipline, not software. Sequence the work, clean before you import, treat the Pricebook as its own project, and validate against the source before anyone goes live. If you want a second set of eyes on your mapping and validation plan, TradeWeave is a ServiceTitan Certified Provider and can help you scope the migration before it becomes a problem.