Migrate from ServiceTitan to HubSpot

ServiceTitan Customer maps directly to HubSpot Contact. The primary phone, email, name, and address fields transfer as standard Contact properties. Secondary contact records attached to a Customer become additional HubSpot Contact records linked to the same primary Company in HubSpot.

ServiceTitan Location (the physical service site with address) maps to HubSpot Company. Multi-location customers generate multiple Company records with a custom Location_ID__c field and optional parent-company linkage. ServiceTitan location-type tags (residential, commercial) map to a custom Company property in HubSpot.

ServiceTitan Job maps to HubSpot Deal. Job status (Created, Dispatched, In Progress, Completed, Invoiced) maps to HubSpot Deal stage. The Job total revenue maps to Deal amount, technician assignment maps to a custom Owner_ Technician__c property, and job_type maps to a custom Job_Type__c property on the Deal.

ServiceTitan Estimates become HubSpot Deals in 'Proposal' or pre-dispatch stages. Estimate line items with description and price are stored as Deal property text (multi-line) or as a custom line-item object. Converting an Estimate to a Job in ServiceTitan maps to advancing the HubSpot Deal to a won/active stage.

ServiceTitan Invoice records preserve financial history but HubSpot has no native invoice object. Invoice total, status (Paid, Outstanding, Overdue), and invoice date are stored as custom properties on the associated Deal: Invoice_Total__c, Invoice_Status__c, Invoice_Date__c. Full invoice line items require a custom Invoice_Line_Item__c object.

ServiceTitan Equipment (serialized HVAC units, water heaters, appliances) has no native HubSpot equivalent. We create an Equipment custom object with properties for Asset_Tag__c, Make__c, Model__c, Serial_Number__c, Install_Date__c, Warranty_Expiration__c, and a lookup to the HubSpot Company representing the Location where the equipment is installed.

ServiceTitan Memberships (preventive maintenance tiers like Gold, Silver, Bronze) require a custom Membership object in HubSpot with Tier__c, Renewal_Date__c, Covered_Locations__c, Monthly_Price__c, and Active__c flag. The membership links to the primary Contact and to the Company records representing the covered service locations.

ServiceTitan Technicians are operational users who perform jobs. HubSpot's User model is for CRM licensees. We match ServiceTitan technicians by email to HubSpot Users — if a technician does not have a HubSpot seat, their name and ID are stored as a Technician_Name__c property on the Job/Deal record for historical reference.

ServiceTitan Business Units segment operations by trade or brand. HubSpot has no business-unit object — we store the Business Unit name as a custom Contact and Deal property (Business_Unit__c) and recommend using HubSpot's Teams feature to segment reporting by business unit if needed.

ServiceTitan Calls, Appointments, and Internal Notes map to HubSpot Call, Meeting, and Note activities respectively. Original timestamps, technician owner, and the parent record (Job or Location) association are preserved on each HubSpot activity, maintaining full operational history for reporting purposes.

ServiceTitan custom fields added to any object are enumerated during discovery. Each custom field is created in HubSpot with a matching data type (text, number, date, pick-list) and mapped during the migration run. Pick-list custom fields require value-by-value mapping against HubSpot pick-list options.

ServiceTitan payment records (method, amount applied, balance) have no HubSpot equivalent. We store payment status and amount paid as custom properties on the Deal and flag fully paid vs. outstanding invoices. Detailed payment history requires a custom Payment_Record__c object in HubSpot.