Migrate from Housecall Pro to Zoho CRM

HCP Customer stores name, email, phone, address, company, lead_source, and tags in one flat record. FlitStack AI splits this: contact details (first name, last name, email, phone) land in Zoho Contact; company name and address components populate Zoho Account. The HCP Customer ID is stored as Source_System_ID__c on both records for cross-reference during delta runs.

HCP Jobs carry status, type, scheduled datetime, total price, technician assignment, customer reference, and line items. Zoho Deals hold stage, amount, closing date, owner, and contact/account lookups. FlitStack AI maps the HCP job status to a Zoho Deal Stage via a value-mapping table. The HCP scheduled datetime becomes the Deal's Expected Close Date. Job ID preserved as Source_System_ID__c on the Deal record.

HCP Property Profiles track equipment at a customer address: item type, display name, make, model, serial number, install date, and notes. Zoho CRM has no native equipment module — FlitStack AI creates a custom Equipment module and links each record to the Account via a lookup relationship. Equipment fields (make, model, serial number, install date) are created as custom fields in Zoho before migration runs.

HCP Price Book separates Services from Materials. Zoho Products is a single module with no native service/material distinction. FlitStack AI adds a custom pick-list field (Product_Type__c) with values 'Service' and 'Material' to the Products module so the HCP distinction is preserved. Unit price from HCP maps to Product's Standard Price; service name maps to Product Name.

HCP Employees store name, email, phone, role, certifications, and skills. Zoho Users are authenticated CRM users with roles and profiles. FlitStack AI matches HCP employee email addresses to existing Zoho users by email lookup. Unmatched employees are flagged for team creation in Zoho before migration. User records own migrated Deals and Tasks in Zoho.

HCP job statuses are configurable per HCP instance (common values: scheduled, in_progress, completed, cancelled). Zoho Deal Stages are pick-list values scoped to a Blueprint pipeline. FlitStack AI extracts the HCP job status values from the source data, maps each to a corresponding Zoho StageName value, and applies the mapping in the migration field-level diff before the full run commits.

HCP and Zoho both have a Lead object. FlitStack AI maps HCP lead fields directly to Zoho Lead fields: first name, last name, email, phone, lead source, notes. HCP Lead Source maps to Zoho Lead Source. The HCP lead ID is stored as Source_System_ID__c for traceability. HCP leads that have converted in HCP (i.e., have a linked job) are flagged before migration to route to Zoho Contacts instead.

HCP Job Types categorize work (e.g., HVAC repair, plumbing installation, electrical inspection). Zoho Deals have no native job-type field. FlitStack AI creates a custom pick-list field (Job_Type__c) on the Deal module before migration and populates it from HCP job type values. The pick-list values are seeded from HCP's distinct job type values found in the source export.

HCP generates invoices linked to jobs with line items, tax, and payment status. Zoho CRM has no native invoicing module — Zoho Books handles that separately. FlitStack AI migrates the invoice number, amount, and status as custom fields (HCP_Invoice_Number__c, HCP_Invoice_Amount__c, HCP_Invoice_Status__c) on the linked Deal for financial audit reference. The recommendation to connect Zoho Books post-migration is included in the migration plan.

HCP Customers and Jobs carry tags for segmentation (e.g., 'VIP', 'commercial', 'maintenance contract'). Zoho CRM has no native tag object equivalent. FlitStack AI migrates HCP tags as a comma-separated text string in a custom field (HCP_Tags__c) on both Contact and Deal. Users can re-create these as Zoho Tags post-migration if desired.

HCP stores addresses on Customer records with type (billing, service). Zoho Account holds one address set; Contact holds another. FlitStack AI maps the HCP primary service address to Account Address fields and the billing address to Account Billing Address fields. Service zones (geographic routing areas) from HCP are preserved as a custom text field (Service_Zone__c) on Account for reference.

HCP Lead Sources define where a customer originated (e.g., Google Ads, referral, door knock). Zoho Lead Source is a pick-list field on the Lead module. FlitStack AI maps HCP lead source values directly to Zoho Lead Source. If HCP uses custom lead source values not in Zoho's default list, those are added to the pick-list during schema setup before migration.