Migrate your ServiceTitan data

Customers are the top-level record in ServiceTitan's data model. We map Customer Name, contact details, phone numbers, email addresses, and the Notes field 1:1. ServiceTitan validates email format but does not deduplicate across the platform automatically — we flag potential duplicate customers during import scoping.

Service Locations are address-driven child records under Customers, required for job booking and technician routing. Each location stores coordinates used by Map 2.0, Optimize Technician Route, and Technician Arrival Tracking. We migrate location addresses 1:1 but require longitude/latitude coordinates to be validated or manually entered after import since address verification can fail for non-standard addresses.

Jobs are the core operational record linking a Customer, Service Location, Technician, and Line Items. We map Job status, dates, assigned technician, and job-level custom fields. Historical completed jobs transfer as closed records; open jobs land as their equivalent open status in the destination system.

Invoices are tied to Jobs and carry line-item details, payment status, and QuickBooks Desktop mapping metadata. We preserve invoice number, date, total, and balance. Payment history requires mapping against the destination's accounting module since ServiceTitan's payment ledger has platform-specific fields like check/bounced-check tracking.

Estimates are authored in the Proposal Builder and carry pricing, materials, and service details. We map the estimate value, associated customer and location, and acceptance status. Custom pricing matrices in the source estimate may require reapplication in the destination pricebook post-migration.

The Dispatch Board stores real-time scheduling state and visual drag-and-drop job assignments that are inherently destination-specific. We do not migrate Dispatch Board state. We map technician capacity configurations and pipeline stages to the destination system's scheduling module instead.

ServiceTitan Pricebooks define materials, labor rates, and service packages. The Pricebook import has documented error-handling procedures in ServiceTitan's own knowledge base. We migrate Pricebook Items with their pricing, but we flag that category structure differences between source and destination systems often require manual reorganization after import.

Service Agreements are recurring service contracts attached to a Customer or Service Location, governing automatically scheduled work. We map the agreement terms, frequency, associated location, and linked Job template. Acceptance and activation status transfers as-is.

Payments in ServiceTitan are linked to Invoices and carry payment method, amount, date, and reconciliation status. We map payment records 1:1 for historical accuracy but note that check-specific fields (such as bounced-check flags) only map if the destination platform supports them natively.

ServiceTitan allows custom fields on Customer records, Service Location records, and Jobs. Custom fields appear in Search and can be included in reports. We migrate all custom field values and preserve their object association. However, the custom field schema itself must be recreated in the destination system — we provide a schema export alongside the data migration.

Technicians are stored as Employee records with scheduling, capacity, and route-optimization attributes. We map the technician name, contact details, working shifts, and capacity configuration. Employee-specific custom fields and certifications transfer as standard custom fields.