Migrate from Housecall Pro to Nutshell

Housecall Pro Customer records (with first_name, last_name, email, phone numbers, addresses) map to Nutshell Person records. The customer.company field maps to a Nutshell Company record, created first so the Person record can link via a Company reference. Multi-address customers have their service address mapped as primary; billing address stored as a custom field on the Person.

Housecall Pro Customers that have not yet had a completed job can be routed to Nutshell Lead records based on lead_source value or job status. Customers with at least one completed job map to Person records in Nutshell's primary CRM model. The split is configurable — your team chooses the status threshold.

Housecall Pro Job records map to Nutshell Opportunities. Job name becomes the Opportunity name, job status (Scheduled, In Progress, Completed) maps to a Nutshell pipeline stage, and the job's scheduled date becomes the Opportunity close date. The customer link is preserved via the Person/Company association already established.

Housecall Pro Job Types (HVAC, Plumbing, Electrical, etc.) map to Nutshell pipeline categories. If Housecall Pro uses multiple pipelines or service categories, each becomes a separate Nutshell pipeline with stages aligned to job status progression. We configure pipeline stages before migration so field-to-stage mapping is ready.

Housecall Pro Property Profile equipment records (item type, make, model, serial number, install date) map to custom fields on the linked Nutshell Company record. Each equipment item becomes a separate custom field or is serialized into a custom Equipment_History__c text field. Nutshell's custom field creation is handled before migration runs.

Housecall Pro invoices have no direct Nutshell equivalent — Nutshell has no native invoicing module. We create a custom object 'HCP_Invoice__c' in Nutshell to preserve invoice number, amount, status, date, and linked customer reference. The data migrates for historical reference; Nutshell-side invoice rebuilding is handled separately.

Housecall Pro Estimate records map directly to Nutshell Opportunities. Estimate total amount becomes Opportunity amount, and the estimate status (Draft, Sent, Accepted, Declined) maps to a custom Opportunity stage or a custom field (Estimate_Status__c). Linked line items are preserved as notes or a custom field for reference.

Housecall Pro Price Book items (service name, cost, markup tier, unit of measure, taxable flag) have no Nutshell equivalent. We migrate the price book as a custom object 'HCP_PriceBook__c' for reference documentation. Nutshell users rebuild the price structure using their preferred quoting approach.

Housecall Pro Employee records map to Nutshell users by email resolution. The technician assigned to each job becomes the Opportunity owner in Nutshell. Unmatched employees are flagged before migration; your team either creates Nutshell users for them or reassigns their records to a fallback owner.

Housecall Pro tags on customers and jobs migrate to Nutshell tags on the corresponding Person, Company, or Opportunity record. Tags are preserved as-is. Nutshell tags are a flat namespace — nested Housecall Pro tag hierarchies are flattened into hyphenated strings.

Housecall Pro lead_source values (Google, Referral, Yelp, etc.) migrate to a custom field Lead_Source__c on Nutshell Person and Lead records. The source attribution is preserved for Nutshell's reporting and campaign tracking.

Housecall Pro file attachments on jobs, estimates, and invoices are downloaded and re-uploaded to Nutshell as file attachments on the corresponding Opportunity or Person record. Nutshell's API imposes file size limits per attachment; we verify file sizes before migration and flag any that exceed Nutshell's constraints. Inline images and PDFs attached to Housecall Pro records are preserved when possible, with original filenames and metadata retained where the API supports it. Your team can review the attachment inventory during the sample migration phase.

Housecall Pro Route records (service zone assignments for technicians) have no Nutshell CRM equivalent. Route names and zone assignments are preserved as a custom text field on the Nutshell User record for reference. Service zone management is a Housecall Pro scheduling feature that requires a separate tool in Nutshell's ecosystem — we export the route taxonomy in a structured format your team can use to configure territory management in a third-party scheduling or routing tool integrated with Nutshell.