Migrate from Housecall Pro to Odoo CRM

Housecall Pro customers map directly to Odoo res.partner records. The customer record carries the primary address, email, phone numbers, company name, and tags. In Odoo, res.partner serves as both contact and company record — customers without a company name land as individual partners with partner_type='contact'. We preserve the original Housecall Pro customer ID in a custom field for delta-run de-duplication.

Housecall Pro jobs map to Odoo crm.lead (opportunity) records. Each job links to its customer (res.partner) via partner_id. The job type becomes the Odoo pipeline stage — each distinct Housecall Pro job_type value gets a corresponding crm.stage in Odoo so the pipeline reflects your actual service categories. Job completion status translates to Odoo's won/lost stage logic.

Housecall Pro estimates translate to Odoo sale.order records in draft or sent state. Each estimate line item becomes a sale.order.line referencing a product.product record. The estimate total, tax handling, and validity date map to Odoo's amount_total, tax_totals JSON, and validity_date fields. Accepted estimates become confirmed sale orders; rejected ones stay in draft.

Job invoices migrate as Odoo account.move records in the 'out_invoice' type. Odoo requires the Accounting module to be installed for this object. Invoice lines map to account.move.line with product_id references. Payment status (paid, open, cancelled) maps to Odoo's payment_state field. Historical invoice records serve as billing history; they do not generate follow-up actions.

Housecall Pro employees map to Odoo res.users records. Owner/technician assignment on jobs resolves via email matching against Odoo user logins. Unmatched technicians are flagged as a pre-migration action — you either invite them to Odoo or assign their records to a fallback user before the migration run.

Housecall Pro price book services migrate as Odoo product.product records with type='service'. Unit price, description, and service category map to list_price, description_sale, and categ_id. Materials tracked in the price book become product.product records with type='product' and inventory tracking enabled. Each product receives a custom field linking it to the original Housecall Pro price book item ID.

Housecall Pro property profiles store equipment per customer address: item type, make, model, serial number, install date. Since Odoo has no native equipment module in CRM alone, we offer two options: (a) custom fields on res.partner (Equipment_Type__c, Equipment_Make__c, Equipment_Model__c) for simple equipment records, or (b) product.product records linked via a many2one field on res.partner for detailed serial-number-level tracking. Your Odoo admin selects the approach before migration.

Housecall Pro job appointments with scheduled start and end times translate to Odoo calendar.event records. Each event links to the crm.lead (job) and the assigned res.users (technician). The original appointment start and stop timestamps are preserved in the event's start and stop fields. Odoo calendar events are visible in Odoo's native calendar view and sync with external calendars if configured.

Housecall Pro tags applied to customers and jobs migrate as Odoo tags. Customer tags map to res.partner category_id records (stored in res.partner.category). Job tags map to crm.tag records attached to crm.lead via tag_ids. Tag names are preserved exactly — no transformation applied.

Housecall Pro lead_source values migrate to the Odoo crm.lead source_id field. Odoo stores lead sources in utm.source records (part of Odoo's marketing tracking module). If the UTM module is not installed, the source value falls back to a free-text char field on crm.lead. All original source names are preserved as selection values.