Migrate from Housecall Pro to HubSpot

Housecall Pro customers map to HubSpot Contacts with name, email, phone, and address. The customer.company field maps to a HubSpot Company record; HubSpot links them via the Contact's primary company association. Multiple phone numbers (mobile, home, work) each map to their HubSpot equivalents.

Housecall Pro jobs are the core operational record — they map directly to HubSpot Deals. The HCP job status (scheduled, in_progress, completed, cancelled) maps to a HubSpot deal stage via a value-mapping table. Deal amount, close date, and description carry over directly. A custom job_type property preserves the HCP Job Type name.

Housecall Pro estimates map to HubSpot Deals with line items representing each estimate line. The estimate total becomes the Deal amount; estimate status (draft, sent, approved, declined) maps to custom deal stage values. Line items carry description, quantity, unit price, and total per row.

Housecall Pro invoices map to HubSpot Deals with the invoice total as the Deal amount. The payment status (paid, partially paid, overdue, void) maps to a custom payment_status property. Tax and discount amounts carry as separate custom properties since HubSpot Deals have no native tax/discount fields. Note that HubSpot Deals are not formatted invoices — your team rebuilds invoice presentation in HubSpot or a connected tool.

Housecall Pro Property Profiles (item type, make, model, serial number, install date, notes) have no native HubSpot equivalent. FlitStack creates an Equipment custom object in HubSpot with fields for each data point, linked to the Customer Contact record via a lookup relationship. Multi-item properties per address generate multiple Equipment records.

Housecall Pro employees (name, phone, email, role) map to HubSpot Contacts with an 'Employee' role property. If employees need HubSpot seat access, your admin creates HubSpot Users manually after migration — FlitStack preserves the email and name for matching. Housecall Pro certifications and documents are stored as file attachments on the Contact record.

Housecall Pro leads map 1:1 to HubSpot Leads, preserving all standard fields including first name, last name, email, phone, address, lead source, and notes. The HCP lead status and assigned employee carry over as properties on the HubSpot Lead record. If you have existing HubSpot leads that may overlap with HCP lead emails, FlitStack flags potential duplicates before insertion so your team can review and resolve.

Housecall Pro Job Types (e.g., 'HVAC Repair', 'Plumbing Inspection') categorize work orders but have no HubSpot native equivalent. FlitStack maps each unique Job Type to a custom pick-list property (HCP_Job_Type__c) on the Deal object. If there are more than 200 unique Job Types, they may be stored as a custom object instead to stay within HubSpot's pick-list value limits.

Housecall Pro price book services (name, description, default price) have no HubSpot equivalent. Services map as a custom Price_Book_Service object; standard service prices can be referenced as Deal line-item templates in HubSpot. Recurring service agreements become Deals with a custom subscription_type property.

Housecall Pro tags are flat labels on customers and jobs. They migrate as comma-separated text in a HubSpot custom property (e.g., Tags__c) on the Contact or Deal. HubSpot's native tag association model does not apply to Deals — text storage preserves the label without requiring HubSpot's Contact list-tag structure.

Housecall Pro notes and file attachments on customers, jobs, and invoices migrate to HubSpot Notes on the corresponding Contact or Deal record. File attachments re-upload to HubSpot Files and attach to the record. Inline images in notes are extracted and re-hosted as file attachments.

Housecall Pro's internal customer UUID is stored as a custom property (HCP_Customer_ID__c) on the HubSpot Contact for traceability, deduplication, and delta-run matching. The HCP job ID is stored as HCP_Job_ID__c on the corresponding Deal. These IDs enable FlitStack to match records across migration runs and detect any records modified in Housecall Pro during the cutover window.

HubSpot Deals have no native scheduling field. FlitStack stores the Housecall Pro scheduled start and end times as custom datetime properties (Job_Scheduled_Start__c and Job_Scheduled_End__c) on the Deal. Original start/end timestamps preserve the service appointment window for reporting, pipeline visibility, and dispatch coordination after migration.

Housecall Pro lead_source on customer and lead records maps directly to HubSpot's hs_lead_status or a custom lead_source property on Contact and Lead. If the HCP lead source value has no HubSpot match, it stores as-is in the custom property. This preserves your original attribution data for campaign analysis and reporting in HubSpot.

Housecall Pro routes and service zones (geographic dispatch groupings) map to a custom text property (Route__c) on the Deal. HubSpot has no native dispatch or zone model; the property is available for segmentation, filtering, and reporting in HubSpot's built-in tools. Route data supports territory-based pipeline analysis after migration.