Migrate from Service Autopilot to HubSpot

Service Autopilot Clients map directly to HubSpot Contacts. Name, email, phone, address, and create date migrate as standard Contact properties. Unresolved or incomplete client records that lack an email address may require a HubSpot Lead record or a placeholder Contact depending on HubSpot's duplicate-detection settings.

Service Autopilot Leads that are not yet converted to Clients map to HubSpot Leads. First name, last name, phone, email, lead status, and source information migrate as standard HubSpot Lead properties. We resolve HubSpot users by email match for owner assignment.

Service Autopilot Commercial Accounts map to HubSpot Companies. Company name, billing address, service address, and industry classification migrate as standard Company properties. When a Commercial Account has multiple associated Service Locations, the primary address maps to the Company address and additional locations are stored as a custom property or custom object.

Service Autopilot Service Locations represent specific properties where jobs are performed. HubSpot has no native service-location object. We create a HubSpot custom object (Service_Location__c) with fields for address, property type, measurements, client association, and GPS coordinates. Each Service Location links to a Contact or Company record by email or company domain match.

Service Autopilot Estimates represent job proposals with line items, pricing, and status. Estimates map to HubSpot Deals where deal name references the Estimate ID, amount maps to Deal amount, and a custom field (Estimate_Status__c) preserves the original estimate status (Draft, Sent, Accepted, Declined). Line items are stored as custom properties or a JSON field on the Deal.

Service Autopilot Jobs are the core operational records tracking scheduled work. HubSpot has no native job or work-order object. We create a Job_History__c custom object to preserve job ID, date, assigned crew, service performed, job status, and total invoice amount. Each Job record links to the Contact (client) and the Service_Location__c custom object.

Service Autopilot Services and Service Packages define the deliverable work items with pricing. These map to HubSpot Products with name, price, and description. Products are then associated with Deals that originated from Estimates so deal line items reflect the original service configuration.

Service Autopilot Invoices track billing, payments received, and outstanding balances. HubSpot does not include native invoicing. We create an Invoice_History__c custom object preserving invoice ID, date, total amount, amount paid, balance due, and payment method. Invoice associations link to the Contact and the Job_History__c record that generated the charge.

Service Autopilot Automations and Sequences run on job triggers, client lifecycle events, and scheduling conditions. HubSpot workflows run on CRM records only and cannot replicate field-service trigger logic. We export the automation definitions as a structured reference document your HubSpot admin can use to rebuild equivalent workflows using HubSpot's workflow builder and sequences tools.

Service Autopilot custom fields on any object map to HubSpot custom properties on the corresponding object or custom object fields on a custom object. Field type is preserved (text, number, date, pick-list, checkbox). Pick-list values are mapped value-by-value. Any Service Autopilot custom field marked as 'Required' is flagged for HubSpot admin to set as Required on the destination field.

Service Autopilot file attachments on Jobs or Service Locations (photos, signed documents, property diagrams) are downloaded and re-uploaded to HubSpot Files, associated with the corresponding Contact, Company, or custom object record. File size limits in HubSpot apply (25MB per file); larger files are linked by URL reference.

Service Autopilot Team Members and Employees who are assigned to jobs map to HubSpot Users by email address. Non-email team members (field crews without HubSpot logins) are preserved as text values in the job assignment field on the Job_History__c custom object rather than as HubSpot Users, since HubSpot requires a licensed user for every record owner.