Migrate from ServiceTitan to Pipedrive

ServiceTitan Customer maps to both a Pipedrive Person (primary contact fields: name, email, phone) and an Organization (company name, domain, industry). When a Customer has multiple Service Locations, the Organization record holds the primary address and additional locations are stored as address custom fields on the Organization.

Each ServiceTitan Service Location for a Customer maps to a set of Organization address fields. When a Customer has multiple locations, those secondary locations are preserved as structured custom fields on the Organization (e.g., Location2_Address__c, Location2_City__c) rather than separate Organization records, to avoid inflating Pipedrive's organization count.

ServiceTitan Jobs that represent billable work map to Pipedrive Deals with pipeline stage derived from Job status (Estimate → Open, Scheduled → Won/negotiation, Completed → Won). Dispatch status, assigned technician, and job type migrate as custom fields on the Deal. Non-billable jobs (internal maintenance) map to Pipedrive Activities instead.

ServiceTitan Employees with a role of 'Technician' or 'Office Staff' map to Pipedrive User accounts. Resolution is by email match — the Employee's email address must exactly match a Pipedrive user email for the OwnerId to resolve correctly on migrated Deals and Persons.

ServiceTitan Estimates map to Pipedrive Deals in an early pipeline stage. The estimate total amount maps to Deal value, and the estimate status (Sent, Accepted, Declined) maps to the corresponding Pipedrive stage. Original estimate date is preserved as a custom field.

ServiceTitan Equipment records linked to a Service Location have no native Pipedrive equivalent. We map equipment make, model, serial number, and install date as custom fields on the associated Organization record. Multiple equipment items per location are stored as repeatable custom fields or a serialized JSON field on the Organization.

ServiceTitan Service Agreement records (recurring maintenance contracts tied to a customer or location) map to custom fields on the Organization record in Pipedrive — agreement type, start/end dates, coverage scope, and monthly/annual value are preserved as structured custom fields since Pipedrive lacks a native contract object.

ServiceTitan Invoice records map to Deal custom fields capturing invoice number, invoice date, total amount, balance due, and payment status. Invoice line items can be stored as a custom text field on the Deal. Paid invoices update the Deal stage to 'Won'; outstanding balances are flagged in a custom status field.

ServiceTitan custom fields on any object are recreated as Pipedrive custom fields on the equivalent target object before migration. The field name, type, and pick-list values are matched. Pipedrive generates a 40-character hash key for each custom field — those keys are used in the bulk import payload.

ServiceTitan Job notes map to Pipedrive Activity records with type 'Note' attached to the corresponding Deal. File attachments on Jobs (photos, diagrams) are downloaded and re-uploaded as Pipedrive file attachments on the Deal or Person record. File size limits (25MB per file in Pipedrive) are enforced during re-upload.

ServiceTitan lead records map directly to Pipedrive Leads using field-level mapping. HubSpot-style lifecycle stages do not exist in ServiceTitan, so this mapping is straightforward — source title, company, phone, email, and status map directly to Pipedrive Lead fields without requiring any transformation logic or value mapping.

ServiceTitan activities (logged calls, emails, meeting notes) attached to Jobs or Customers map to Pipedrive Activities linked to the corresponding Person or Deal. Original timestamps and assigned employee (resolved to Pipedrive User by email) are preserved on each Activity record.