Migrate from Honcho CRM to Odoo CRM

Honcho Lead records export with name, email, phone, lead source, status, and custom fields. We map these to Odoo CRM Lead using the standard name, contact_name, email_from, phone, source_id, and stage_id fields. Any Honcho lead scoring or custom rating fields map to custom Char or Float fields on Odoo's crm.lead model. Lead assignment to an Owner resolves by email match against Odoo.res.users.

Honcho Company records map to Odoo res.partner with company_type = 'company'. The Honcho company name maps to partner name; domain or website maps to website field. Partner is created before any Contact import so the Contact record can reference the parent partner_id. We preserve Honcho's Company ID as an external reference field for relationship audit.

Honcho Contact records map to Odoo res.partner with company_type = 'person' and a parent_id link to the mapped Company Partner. Email, phone, mobile, title, and function fields migrate directly. Custom fields on contacts in Honcho map to custom columns on res.partner, which we pre-create before import. Contact-Company linking uses Honcho's exported Company ID to resolve the parent_id lookup at migration time.

Honcho Deals map to Odoo CRM Opportunity (crm.lead with type = 'opportunity'). The deal name maps to opportunity name; deal value maps to expected_revenue; stage maps to stage_id via stage name lookup against the destination pipeline. Partner_id resolves to the mapped Company Partner; contact_id resolves to the mapped Contact. Lost reason and close date map to Odoo's lost_reason and date_closed fields.

Honcho exposes a visual pipeline with named stages in a fixed order. We extract all stage names and their sequence order from the Honcho pipeline export and create matching crm.stage records in Odoo's pipeline. Stage probability percentages migrate from Honcho to Odoo's probability field per stage. If Honcho stages have custom colors or labels, we note them for Odoo Studio configuration post-migration.

Honcho Deal Timelines track each action taken toward closing a deal — a proprietary format that does not map to any Odoo standard object. We flatten every timeline entry into a mail.activity record with activity_type_id (mapped to the closest Odoo activity type: Call, Meeting, Task, or Email), note the original timeline description in the activity's note field, set the scheduled_date from the timeline timestamp, and link it to the migrated Opportunity (crm.lead) via res_id and res_model_id. Users should verify that the resulting activity timeline meets their expectations after migration.

Honcho supports custom fields on Contacts and Companies. We detect all custom field definitions during scoping, capture their data types, and pre-create matching custom columns on the corresponding Odoo model (res.partner or crm.lead) before any data loads. Field types are preserved: text fields map to Char or Text, number fields to Float or Integer, date fields to Date. Selection fields map to Odoo Selection fields with matching key-value pairs.

Honcho User records (name, email, role) are exported and matched to Odoo res.users by email address. Any Honcho Owner referenced on a Deal, Contact, or Company record is resolved against the mapped user list. If a Honcho owner has no matching Odoo user, we flag the record in the reconciliation report and assign it to a placeholder owner until the customer provisions the user in Odoo. Role titles (Admin, Manager, Rep) do not automatically map to Odoo access rights groups; these require manual group assignment post-provision.

Honcho's QuickBooks sync stores integration settings and linked invoice references locally and does not include them in exports. We flag any Deal or Contact record with a QuickBooks association during scoping and include a note in the migration artifact. The customer reconciles invoice data directly in QuickBooks post-migration and manually re-links any required Deal-to-Invoice associations in Odoo Accounting if using the Odoo QuickBooks connector.

Honcho does not maintain a standalone activity log — engagement history lives in the Deal Timeline. We sequence all timeline entries chronologically and land them as Odoo mail.activity records attached to the corresponding Opportunity (crm.lead). Email, call, meeting, and task subtypes are inferred from the timeline action description. If Honcho exported standalone notes attached to Deals or Contacts, these land as Odoo Note (mail.message) records with note subtypes.

Honcho does not have a dedicated product catalog, but if the customer used Deals with product references in custom fields, we migrate those as Odoo product.template records. Standard price, cost, and product type (service vs consumable) fields are set based on the data in the export. If no product data exists in Honcho, this mapping step is skipped.

Honcho's Report Builder generates CSV exports that serve as the migration source. We schedule export downloads during scoping, parse all CSV files, and produce a data dictionary mapping each Honcho column header to the corresponding Odoo field or custom column. The parsed dataset is held in a staging environment before loading and reconciled against record counts before production import begins.