Migrate from Housecall Pro to Pipedrive

Housecall Pro customers map directly to Pipedrive People. First name, last name, email, phone, and address fields migrate as direct field-level copies. Customers without an email receive a placeholder email constructed from [email protected] to satisfy Pipedrive's required email format. This ensures every migrated Person record has a valid email address, and the placeholder domain is flagged in your audit log for later cleanup.

Housecall Pro's company name on a customer record maps to a Pipedrive Organization. The Organization is created and linked to the Person record via the Person's Organization relationship. Customers without a company name receive a default Organization named 'Individual — No Company' to satisfy Pipedrive's linking requirements.

Housecall Pro leads that have not yet converted to a jobbed customer route to Pipedrive's Lead inbox. The Lead inherits all dealFields custom fields. Housecall Pro lead sources (Referral, Website, Angi, etc.) map to Pipedrive custom drop-down fields defined before migration.

Each Housecall Pro job becomes a Pipedrive Deal. The job title and description populate the Deal name and notes respectively. Job status values (Scheduled, In Progress, Completed, Cancelled) map to Pipedrive stage values that your admin defines during setup — each status becomes a distinct stage in your Pipedrive pipeline. Job cost and price fields migrate to Deal value (formatted as integer cents or decimal depending on setup).

Job scheduling information — scheduled date, assigned employee, and service type — generates a Pipedrive Activity record linked to the Deal. The activity type (Call for a service visit, Meeting for an estimate) is set based on the job type field from Housecall Pro. Original scheduled time and assigned technician are preserved in the activity description.

Housecall Pro estimates map to Pipedrive Deals with a status of 'Open Estimate' that maps to a designated Pipedrive stage. When an estimate is accepted in Housecall Pro and converted to a job, that Deal stage updates through the delta-pickup run before final migration commit.

Housecall Pro invoices have no native equivalent in Pipedrive's data model. Invoice total, balance due, payment status, and last payment date migrate as custom fields on the Deal. Full invoice line items are written as a formatted Note attached to the Deal, preserving the original pricing breakdown.

Housecall Pro property profiles track equipment type, make, model, serial number, install date, and notes per customer address. These translate to a set of custom fields on the Pipedrive Person record (for customer-level equipment) or Organization record (for property-level equipment). Your Pipedrive admin defines field names and types before migration begins.

Housecall Pro tags on customers and jobs map to Pipedrive Labels. Labels exist independently per entity type in Pipedrive — there are separate Person labels, Organization labels, and Deal labels. FlitStack maps the source tag to the corresponding Pipedrive label bucket based on the entity the tag was attached to in Housecall Pro.

Housecall Pro employees (technicians, dispatchers) resolve to Pipedrive Users by email address match. Unmatched employees are flagged before migration — your team either creates the Pipedrive user first or assigns those job records to a designated fallback owner. Housecall Pro role data (technician vs. admin) migrates as a custom field on the Pipedrive User record for reference.

Housecall Pro file attachments on jobs, customers, and property profiles are downloaded and re-uploaded to Pipedrive Files, linked to the corresponding Deal or Person record. Pipedrive's file size limit is 37.5 MB per file; any attachments exceeding this are noted in the migration audit log for manual handling.

Housecall Pro price book services map to Pipedrive Products. Unit price, description, and service category migrate as Product fields. Products can be linked to Deals via Pipedrive's Deal Products feature, enabling your team to build multi-line estimates and invoices directly within Pipedrive after migration. This linking preserves pricing consistency across both migrated records and any new deals created post-migration.