Skip to content
Get a quote

ServiceTitan to Salesforce migration

Moving from ServiceTitan to Salesforce Sales Cloud requires translating a field-service-native data model — jobs, service locations, technicians, and maintenance agreements — into Salesforce's Account-Contact-Opportunity structure. FlitStack AI maps every customer, service location, job record, and custom property, preserving original timestamps and owner assignments so your Salesforce reporting reflects the complete service history from day one.

Short answer

FlitStack AI migrates accounts, contacts, account or address fields, cases and case + opportunities from ServiceTitan to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours for under 50,000 records.

By

Source ServiceTitan
DestinationSalesforce
AccountContactAccount or Address fieldsCaseCase + Opportunity
Mapped field by field · sample run · one-click rollback

What moves from ServiceTitan to Salesforce?

ServiceTitan stores everything in a unified field-service object model: customers linked to service locations, jobs tied to those locations, and technicians assigned through a dispatch board.

Read the full summary

Invoicing, payments, and maintenance agreements are native to the platform. Salesforce Sales Cloud uses a traditional CRM object graph — Accounts, Contacts, Leads, and Opportunities — with Cases for service tracking and custom __c objects for anything non-standard. The migration challenge is threefold: converting ServiceTitan's customer-and-location model into Salesforce's Account hierarchy, translating job records into Cases or Opportunities depending on their financial vs. service context, and rebuilding ServiceTitan's dispatch and scheduling model in Salesforce Field Service (a separate product) or via custom objects. FlitStack AI extracts data via the ServiceTitan API, maps each record type to its Salesforce equivalent, handles custom field translation, and delivers a field-level diff before the full run commits. Workflows, automations, and dispatch rules do not migrate — we export definitions for your Salesforce admin to rebuild in Flow or Field Service.

direct

Customer → Account

ServiceTitan customers map directly to Salesforce Accounts.

How it maps

A customer can have multiple service locations — these become either child Account records (for multi-location corporate customers) or Address records attached to the primary Account. Primary contact details migrate as Account.Phone and Account.BillingAddress fields.

direct

Customer Contact → Contact

Each customer in ServiceTitan can have multiple named contacts (homeowner, property manager, billing contact).

How it maps

These map to Salesforce Contact records linked via AccountId to the parent Account. Phone, email, and role fields migrate directly. No contact-role equivalent exists for homeowner vs. property-manager distinction — we preserve this as a custom Role__c pick-list.

transformed

Service Location → Account (child) or Address fields

ServiceTitan service locations are address-specific job destinations attached to a customer.

How it maps

For residential customers, location address fields migrate as Account.BillingAddress. For commercial multi-location customers, each location becomes a child Account with its own address and a ParentId linking to the primary Account — your admin decides the hierarchy rule before migration.

direct

Job (Work Order) → Case

ServiceTitan jobs map to Salesforce Cases for service-history tracking.

How it maps

Case.Status maps from Job.Status (e.g., Scheduled → Open, Completed → Closed). Case.Description carries the job summary. Original job number stored as an external ID field (ST_Job_ID__c) for traceability. Jobs with no invoice component stay as Cases only.

merged

Job (with Invoice) → Case + Opportunity

Jobs that generated an invoice in ServiceTitan require a two-object strategy: the service record lands as a Salesforce Case, and the invoice data (total amount, line items) creates an Opportunity record.

How it maps

The Opportunity links back to the Account and carries the Case number as a custom reference field. Your admin decides whether to consolidate this into a single reporting object post-migration.

transformed

Technician → User or Contact

ServiceTitan technicians are platform users with dispatch-board presence.

How it maps

In Salesforce, CRM users require full Salesforce licenses. For read-only or field-only users, we map technicians to Contact records in a designated Technicians account, preserving name, phone, certifications, and skill tags as custom fields. If you have Field Service Lightning licensing, technicians map to ServiceResource objects instead.

What moves12 objects
ServiceTitanSalesforce
  • CustomerAccount1:1
  • Customer ContactContact1:1
  • Service LocationAccount or Address fieldstransformed
  • JobCase1:1
  • JobCasemerged
  • TechnicianUser or Contacttransformed

+ 6 more in the mapping below

How ServiceTitan and Salesforce differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionServiceTitanSalesforce
Core object modelServiceTitan uses flat customer records linked to service locations and jobs. Customer is a top-level entity; locations and jobs nest under it.Salesforce uses Account as the top-level organization record, with Contacts nested via lookup. Locations map to Address fields or child Account records.
Work order handlingServiceTitan jobs (work orders) are first-class objects with status, type, parts, labor, and invoice data all in one record.Salesforce has no native work-order object. Jobs requiring service tracking map to Cases. Jobs with revenue implications map to Opportunities with Products.
Technician modelServiceTitan technicians are users in the platform with dispatch board assignments, certifications, and availability windows.Salesforce Users are CRM users, not field-resources. Field technician management requires Salesforce Field Service (FSL) licensing or custom ServiceResource objects.
Scheduling and dispatchServiceTitan dispatch board is native — drag-and-drop job scheduling with technician availability and skill matching built in.Salesforce has no native dispatch board. Scheduling requires Field Service Lightning (separate product), custom Flow builds, or third-party apps from the AppExchange.
Maintenance agreementsServiceTitan maintenance agreements store contract terms, coverage scope, and renewal dates as native properties of a customer or location.Salesforce contracts live in the Contract object, but coverage-scope tracking for field service requires a custom Agreement__c object or Asset with entitlement links.
Pricing modelServiceTitan charges $245–$500+ per technician per month with no published price card and long-term contracts.Salesforce Sales Cloud starts at $25/user/month (Starter Suite) to $350/user/month (Unlimited Edition) with published tiers on salesforce.com.

ServiceTitan to Salesforce field mapping

The 30 most-used fields of 47 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.

Field mapping5 shown
ServiceTitanSalesforce
  1. customer_nameCustomer NameAccount
  2. emailCustomer Account.Email__cAccount
  3. phoneCustomer PhoneAccount
  4. customer_typeCustomer TypeAccount
  5. created_dateCustomer Original_Create_Date__cAccount
ServiceTitan fieldSalesforce fieldMappingNote
Customer.customer_nameAccount.Namedirect
Customer.emailAccount.Account.Email__ccustom_field_requiredAccount has no native email field; we create Account.Email__c custom field for contact-level email.
Customer.phoneAccount.Phonedirect
Customer.customer_typeAccount.Typevalue_mappingCustomer type (Residential, Commercial) maps to Account.Type pick-list via value-by-value mapping.
Customer.created_dateAccount.Original_Create_Date__ccustom_field_requiredSalesforce CreatedDate is set at migration time; original ServiceTitan create date preserved as custom datetime field.
Customer.modified_dateAccount.LastModifiedDatedirectLastModifiedDate carries the last modification timestamp from Salesforce insert time.
Customer.custom_idAccount.ST_Customer_ID__ccustom_field_requiredServiceTitan internal ID stored as external ID field for delta-run de-duplication.
Service Location.location_nameAccount.NamedirectLocation name becomes Account Name for child Account records in multi-location setup.
Service Location.address_streetAccount.BillingStreetdirect
Service Location.address_cityAccount.BillingCitydirect
Service Location.address_stateAccount.BillingStatedirect
Service Location.address_zipAccount.BillingPostalCodedirect
Service Location.latitude_longitudeAccount.BillingLatitude / BillingLongitudedirectServiceTitan coordinates map to Salesforce BillingLatitude and BillingLongitude for map-based dispatch in Field Service.
Service Location.parent_customer_idAccount.ParentIdtransformedServiceTitan location's parent customer link maps to Salesforce Parent Account ID for hierarchy.
Service Location.location_custom_fieldAccount.ST_Location_Custom__ccustom_field_requiredAny ServiceTitan custom fields on location become Account custom fields with ST_ prefix.
Contact.first_nameContact.FirstNamedirect
Contact.last_nameContact.LastNamedirect
Contact.emailContact.Emaildirect
Contact.phoneContact.Phonedirect
Contact.mobile_phoneContact.MobilePhonedirect
Contact.roleContact.Role__ccustom_field_requiredServiceTitan contact role (Homeowner, Property Manager, Billing Contact) maps to a custom Role__c pick-list.
Contact.account_idContact.AccountIddirect
Job.job_numberCase.CaseNumberdirect
Job.job_descriptionCase.Descriptiondirect
Job.job_statusCase.Statusvalue_mappingServiceTitan status values (Scheduled, In Progress, Completed, Cancelled) map to Salesforce Case Status values via value-by-value mapping.
Job.job_typeCase.Typevalue_mappingJob type (Repair, Maintenance, Installation, Inspection) maps to Case.Type pick-list.
Job.priorityCase.Priorityvalue_mappingServiceTitan priority maps to Case.Priority pick-list (High, Medium, Low).
Job.scheduled_dateCase.Original_Scheduled_Date__ccustom_field_requiredScheduled date preserved as custom datetime since Case doesn't have a native scheduled-date field.
Job.technician_idCase.OwnerIdtransformedOwner resolved by email match to Salesforce Users. Unmatched technicians flagged before migration for admin resolution.
Job.location_idCase.AccountIddirectServiceTitan location linked to parent Account; Case.AccountId points to that Account.

What to watch for in a ServiceTitan to Salesforce migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

ServiceTitan job model conflates service record and invoice — Salesforce needs both

ServiceTitan stores job and invoice data in a single job record.

How we handle it

Salesforce separates service tracking (Case) from financial records (Opportunity). Migrating a job that generated $4,200 in revenue requires FlitStack to create both a Case and an Opportunity, then link them via a custom reference field. Your admin needs to decide upfront whether Opportunity naming follows invoice-number convention or job-number convention — this affects report continuity. We surface this decision point in the pre-migration mapping plan.

high

ServiceTitan dispatch board has no Salesforce equivalent without Field Service Lightning

ServiceTitan's native drag-and-drop dispatch board — with technician availability windows, skill matching, and real-time route optimization — does not exist in standard Salesforce Sales Cloud.

How we handle it

Salesforce Field Service Lightning (FSL) provides the matching functionality but requires separate licensing and configuration. We map technician availability data into a custom ServiceResource model so the raw data is present for FSL setup. Dispatch workflow logic (e.g., nearest-technician routing rules) must be rebuilt as Flow or Apex triggers — we export the ServiceTitan automation definitions as a reference document.

medium

Multi-location customers require Account hierarchy decisions before migration

ServiceTitan allows a customer to have multiple service locations with no enforced hierarchy.

How we handle it

Salesforce Accounts enforce a parent-child model for multi-location organizations. Before migration, your admin must decide whether each location becomes a child Account (with ParentId pointing to the primary Account) or whether all addresses collapse into the primary Account record with address fields serving as a location list. The choice affects reporting on service history per location and territory-based sharing rules. FlitStack generates both mapping variants in the pre-migration diff so your admin can validate before the full run.

medium

Maintenance agreement renewal dates need Entitlement setup in Salesforce

ServiceTitan maintenance agreements carry renewal logic and coverage scope that are integral to job scheduling and customer communication.

How we handle it

Salesforce's closest native object is Contract, but entitlement-based renewal tracking requires Salesforce Entitlement Management (available in Service Cloud or as a add-on). We create a custom Agreement__c object to preserve agreement terms, but your admin needs to configure whether entitlement records are created per agreement and how they trigger service eligibility checks on Cases. This is a Salesforce-admin task that falls outside pure data migration.

medium

ServiceTitan API rate limits can throttle large exports

ServiceTitan's standard API rate limit is 60 calls per second per application per tenant, with reporting APIs capped at 1 report per minute.

How we handle it

For migrations exceeding 100,000 records, FlitStack throttles extraction to respect this limit and uses bulk export endpoints where available. If your ServiceTitan instance has unusually high concurrent API usage (common in large dispatch teams), extraction may take longer than the typical 48–72 hour window. We run a pre-migration API probe to measure your instance's export throughput and adjust the migration schedule accordingly.

How the migration runs

  1. Inventory ServiceTitan objects and map to Salesforce schema

    FlitStack connects to ServiceTitan via API and inventories all customer, location, job, technician, invoice, and payment records.

    What this step covers

    We generate a mapping plan that assigns each ServiceTitan object to its Salesforce equivalent — identifying which jobs need dual Case+Opportunity creation, which customers require Account hierarchy decisions, and which custom fields need Salesforce __c fields created. Your Salesforce admin reviews and approves the plan before any objects are created in your org.

  2. Create Salesforce custom objects and fields

    Before data loads, FlitStack creates all required Salesforce custom objects (Agreement__c, Payment__c, Job_Part__c) and custom fields (__c suffix) on standard objects (Account, Contact, Case).

    What this step covers

    We apply field-level security defaults and add the ST_ prefix to custom fields for source traceability. This step requires a Salesforce admin to validate field-level security settings per profile before migration runs. We also set up field-level security profiles, assign the appropriate field-level access for each profile, and document the field mapping in the pre-migration diff for admin sign-off.

  3. Resolve technician and owner mappings by email

    ServiceTitan technicians and job owners are matched to Salesforce Users by email address.

    What this step covers

    Unmatched technicians are flagged and held — your team either creates Salesforce User accounts for them before migration or approves a fallback Contact-based mapping. No job record lands in Salesforce without an owner resolved; this prevents orphaned Cases that nobody can see. Additionally, we record the original ServiceTitan technician ID in a custom field on the matched User or Contact record to maintain traceability across systems.

  4. Run a sample migration with field-level diff

    A representative slice of 100–500 records migrates first: a mix of customers, service locations, contacts, jobs (with and without invoices), and maintenance agreements.

    What this step covers

    FlitStack generates a field-level diff showing every source value and its destination equivalent. You verify that job-to-Case mapping preserves status, that invoice totals land correctly in Opportunity.Amount, and that technician assignments resolve correctly. Sample validation typically takes one business day.

  5. Execute full migration with delta-pickup window

    Full migration runs against your Salesforce production org using the mapping plan approved during the sample phase.

    What this step covers

    A delta-pickup window (typically 24–48 hours) runs concurrently — any ServiceTitan records created or modified during the cutover window are captured and applied to Salesforce before go-live. FlitStack generates an audit log of every record inserted, updated, or skipped. One-click rollback reverts the Salesforce org to its pre-migration state if reconciliation reveals data quality issues.

  6. Deliver export of ServiceTitan workflow and dispatch definitions

    FlitStack exports your ServiceTitan automation definitions — dispatch rules, notification triggers, and renewal alerts — as a structured reference document.

    What this step covers

    These definitions do not migrate (no platform translates ServiceTitan's automation logic to Salesforce Flow automatically), but the export gives your Salesforce admin a rebuild checklist organized by object. We do not rebuild automations; that scope requires a separate discovery and configuration engagement.

ServiceTitan Salesforce
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · SalesforceRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

48–72 hours for under 50,000 recordsTypical, smaller accounts
7–12 days for over 500,000 records or heavy custom-object / service-agreement setupsLarge or heavily customised accounts

ServiceTitan-to-Salesforce migrations price depends on three drivers: record volume across jobs, customers, and service locations; custom property count on each object (ServiceTitan supports custom fields on customer, location, job, and technician records); and data-model divergence — particularly whether job records carry invoice data that must split into Salesforce Opportunity Products, and whether maintenance agreements require a custom Agreement__c object with entitlement logic. Teams with five or more custom fields per object, or job records exceeding 50,000, land in the upper pricing band because field-level validation doubles per-record processing time. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for ServiceTitan to Salesforce →

Why teams move from ServiceTitan to Salesforce

  • ServiceTitan's per-technician pricing scales unpredictably as your crew grows — contractors on Reddit report bill shock when adding techs mid-contract. Salesforce's per-user model with published tiers (Starter Suite at $25/user/month) offers better cost predictability at scale, and the AppExchange gives access to field-service add-ons without buying a separate platform.
  • Customer support wait times of 30–60 minutes frustrate ServiceTitan users trying to resolve billing or configuration issues. Multiple review threads on G2 note that success managers are too busy to fix problems — teams feel stranded after onboarding. Salesforce's Premier Success Plan and extensive admin community offer more accessible support pathways.
  • ServiceTitan is purpose-built for HVAC, plumbing, and electrical contractors — which is also its limitation. Contractors running mixed-service businesses or wanting CRM capabilities beyond field dispatch report that the platform resists adaptation to non-trade workflows. Salesforce's generic CRM model accepts any data schema, and its Sales Cloud + Field Service bundle covers both sales and field operations.
  • Implementation fees in the tens of thousands and difficult exit processes make ServiceTitan costly to leave. Contractors who negotiated contracts mid-growth report aggressive renewal tactics and opaque extension terms. Teams already evaluating Salesforce cite the ability to own their own data model and export cleanly as a primary driver.

Questions, answered

ServiceTitan to Salesforce migration questions

How long does a ServiceTitan to Salesforce Sales Cloud migration take?

Most ServiceTitan-to-Salesforce migrations complete in 48–72 hours of clock time for under 50,000 records. Larger setups with 500,000+ records, complex Account hierarchies, or jobs that require Case+Opportunity dual creation extend to 7–12 days. Pre-migration object mapping and Salesforce custom-field creation add 3–5 business days of planning and configuration before data moves, ensuring all custom objects and fields are ready for the load.

Will my ServiceTitan dispatch rules and scheduling automations migrate to Salesforce Flow?

No. FlitStack AI migrates data and schema only — dispatch board logic, technician routing rules, job-triggered notifications, and renewal alert automations do not move. They have to be rebuilt in Salesforce Flow or (if you have Field Service Lightning) in FSL's scheduling features. We export your ServiceTitan automation definitions as a structured reference document your Salesforce admin can use as a rebuild checklist. Automations are out of scope for the data migration engagement.

What does a ServiceTitan job become in Salesforce?

ServiceTitan jobs map to Salesforce Cases for service-history tracking. Jobs that generated an invoice in ServiceTitan require a two-object approach: the service record lands as a Case, and the invoice total creates an Opportunity linked to the same Account. We preserve the original ServiceTitan job number as an external ID field (ST_Job_ID__c) on the Case so you can cross-reference records after cutover.

Can I migrate ServiceTitan custom fields to Salesforce?

Yes. ServiceTitan custom fields on customers, service locations, jobs, and technicians migrate to Salesforce custom fields (__c suffix) on the corresponding object. We match ServiceTitan field types to Salesforce equivalents: text fields become Text(255), numbers become Number, pick-lists become Picklist. Custom fields are prefixed with ST_ in Salesforce to indicate their source system and are flagged in the mapping plan before migration runs.

What happens to ServiceTitan maintenance agreements in Salesforce?

ServiceTitan maintenance agreements (with coverage scope, start/end dates, and renewal terms) map to a custom Agreement__c object linked to Account. Salesforce's native Contract object lacks coverage-scope tracking, so a custom object with fields for Coverage_Scope__c (multi-select pick-list), Recurrence_Frequency__c, and Included_Service_Types__c preserves the full agreement context. Your admin then configures entitlement records if entitlement-based service eligibility is required. The custom object also stores renewal reminders and customer-specific pricing tiers, enabling reporting on contract health. After migration, your admin can set up entitlement processes to enforce service eligibility based on the agreement status.

Does the migration affect my ServiceTitan account during cutover?

FlitStack AI uses scoped read access on ServiceTitan — your dispatch team keeps scheduling jobs and your CSRs keep booking appointments during the migration. A delta-pickup window (24–48 hours) captures any records created or modified after the initial extraction point, so Salesforce reflects ServiceTitan's final state at go-live. No writes occur to your ServiceTitan instance during the migration. The migration runs in read-only mode, ensuring your live system remains operational while the delta window captures any late entries before final synchronization.

How do multi-location customers map in Salesforce after migration?

ServiceTitan allows one customer to have multiple service locations without enforcing a hierarchy. Salesforce enforces an Account parent-child model. Before migration, your admin chooses the hierarchy rule: each ServiceTitan location becomes a child Account with ParentId pointing to the primary Account, OR all addresses collapse into the primary Account record. FlitStack generates both mapping variants in the sample migration diff so you can validate the reporting impact before the full run.

What happens to invoice and payment data from ServiceTitan?

ServiceTitan invoices and payments have no direct Salesforce standard equivalent. We create a custom Invoice__c object and Payment__c object linked to Account and Opportunity. Invoice totals map to Opportunity.Amount for revenue reporting continuity. Payment records preserve method, date, and applied amount. If your team uses Salesforce CPQ, invoice line items can alternatively map to OpportunityLineItems via a pricebook — your admin selects the model before migration runs.

Get a quote

Moving from ServiceTitan to Salesforce?

Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.

Get a quote