Migrate from ServiceTitan to Salesforce Sales Cloud

ServiceTitan customers map directly to Salesforce Accounts. 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.

Each customer in ServiceTitan can have multiple named contacts (homeowner, property manager, billing contact). 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.

ServiceTitan service locations are address-specific job destinations attached to a customer. 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.

ServiceTitan jobs map to Salesforce Cases for service-history tracking. 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.

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. 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.

ServiceTitan technicians are platform users with dispatch-board presence. 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.

ServiceTitan maintenance agreements store coverage scope, contract start/end dates, and included service types. Salesforce Contract is the native equivalent but lacks built-in coverage-scope tracking. We create a custom Agreement__c object with fields for Coverage_Scope__c (multi-select pick-list), Recurrence_Frequency__c, and Included_Service_Types__c, linked to Account via AccountId.

ServiceTitan invoices carry line items, tax, payments applied, and balance due. For reporting continuity, we map invoice totals to Opportunity.Amount and invoice line items to OpportunityLineItems (requires Pricebook entry setup). Alternatively, for invoice-level detail, we create a custom Invoice__c object with Invoice_Line_Items__c as a related list — your admin chooses the model before migration.

ServiceTitan payment records (method, amount, date, applied-to invoice) have no Salesforce standard equivalent. We create a custom Payment__c object linked to Account and optionally to the related Invoice__c or Opportunity. Fields include Payment_Method__c, Amount_Paid__c, Payment_Date__c, and Applied_To_Invoice__c lookup. Each Payment__c record can be linked to the corresponding Invoice__c or Opportunity for straightforward reference and reporting.

ServiceTitan custom fields on any object (Customer, Location, Job, Technician) require Salesforce custom fields created before migration. We prefix them with ST_ to indicate source system and match ServiceTitan field types to Salesforce equivalents: text → Text(255), number → Number, date → Date, picklist → Picklist. Custom fields on Job that reference inventory parts map to a custom Inventory_Reference__c text field.

ServiceTitan jobs track parts used with quantity, unit cost, and markup. Salesforce has no native job-parts model. We create a custom Job_Part__c object linked to the Case and to a Product2 record, capturing Part_Name__c, Quantity__c, Unit_Cost__c, and Markup__c. If your team uses CPQ, parts can map to OpportunityLineItems via a pricebook entry.

ServiceTitan file attachments on jobs (photos, signed documents, diagnostic reports) migrate as Salesforce Files attached to the related Case record. File size limits per Salesforce (25MB default) apply — larger files flagged for chunked upload or alternate storage link. This approach preserves file metadata and ensures attachments are accessible within Salesforce's native file viewer.