Migrate from Handyman to Odoo CRM

Handyman customer records map to Odoo res.partner. The partner is created with type 'contact' for individuals and type 'company' for business accounts, matching Odoo's address-book model. Parent-company relationships in Handyman translate to Odoo partner hierarchies via parent_id on res.partner, and any Handyman customer subgroups become Partner.child_ids in Odoo to preserve organizational groupings.

Handyman customers with paid invoices require both a res.partner record and corresponding account.move records in Odoo. We create the partner first, then link each invoice to it via partner_id on account.move. Invoice line items map to account.move.line with proper account_id selection based on Handyman's service category.

Handyman job records map to Odoo crm.lead in opportunity mode. The job name becomes crm.lead.name, job status maps to crm.lead.stage_id (Odoo pipeline stage), and the estimated or actual revenue maps to crm.lead.planned_revenue. We preserve the original job number as x_handyman_job_ref for traceability.

Handyman job-to-technician assignments transform into Odoo mail.activity records attached to the corresponding crm.lead, with activity type set to 'Assignment', deadline aligned to the job scheduled date, and user_id pointing to the resolved Odoo res.users record. Email-matching resolves Handyman technician IDs to Odoo user accounts, ensuring every job assignment traces to a valid Odoo user and appears in their activity dashboard.

Handyman job notes and service-log entries migrate as mail.message records on the corresponding crm.lead in Odoo. Each message preserves the original timestamp, author (mapped by email), and body text. Odoo's chatter interface surfaces these as a chronological service history on each opportunity.

Handyman contact records with site addresses map to res.partner with street, city, state, zip, and country fields populated. When Handyman stores both a billing and service address, we create two res.partner records linked via type 'invoice' and 'other' on the same parent company partner.

Handyman custom properties attached to job records require pre-created Odoo custom fields before migration. We inspect all Handyman custom property names and types, create matching x_* fields on crm.lead via Odoo's Settings > Technical > Models UI or XML-RPC write, then populate them during the data load. Selection-type Handyman properties become Odoo selection fields with value_mapping.

Handyman custom properties on customer records migrate to Odoo res.partner custom fields using the same pre-creation workflow as job custom properties. Fields are created on res.partner model, typed as char, integer, float, date, or selection matching Handyman's data type for each property.

Handyman quotes or estimates map to Odoo sale.order in state 'draft'. Order lines are created from Handyman line items with product_id linked to the matching Odoo product.product or created as a product.template with type 'service'. The sale.order is linked to the corresponding crm.lead via opp_id if the quote originated from a lead.

Handyman invoices map to Odoo account.move with type 'out_invoice'. Partner_id references the corresponding res.partner. Invoice lines populate account.move.line with account_id resolved from Handyman's service category mapping. State is set to 'posted' for paid invoices, 'draft' for open ones. Payment records map to account.payment linked via payment_reference.

Handyman technician and user records resolve to Odoo res.users by email matching. If an exact email match exists in Odoo, we link the Handyman record to that user. For unmatched technicians, we flag them for pre-provisioning before migration or assign their records to a fallback Odoo user to prevent orphaning job assignments.

Handyman job photos and attachments re-upload to Odoo as ir.attachment records linked to the target crm.lead via res_model='crm.lead' and res_id=<lead_id>. File binary content is stored in Odoo's filestore path. Size limits per Odoo configuration apply; we chunk large batches to avoid timeouts during the import run.