Migrate from HighLevel to Odoo CRM

HighLevel Contacts with lifecycle stages below sales qualified lead map to Odoo CRM Lead. Contacts at sales qualified lead, customer, or evangelist lifecycle stages map to Odoo CRM Contact. The split rule is defined during scoping using HighLevel's lifecyclestage property, and the original lifecycle stage value is stored in a custom field on both the Odoo Lead and Contact record for audit continuity. Odoo CRM requires the Contact's commercial partner to be set (Company field), so we resolve the parent Company lookup before inserting Contacts.

HighLevel Companies map to Odoo CRM Commercial Partners (which in Odoo are Contact records with the Company checkbox enabled). The Company domain name populates the Website field and serves as the dedupe key during import. We create the Commercial Partner record before any Contact import so that the Commercial Partner lookup is satisfied at the moment of Contact insert. HighLevel's company phone, address, and industry fields map to Odoo Contact standard fields.

HighLevel Opportunities map to Odoo CRM Opportunities. The HighLevel pipeline name maps to Odoo's Pipeline name, and the HighLevel stage name maps to Odoo Stage within that Pipeline. We pre-create the Odoo Pipeline and Stages before migration so that the stage reference is valid on every Opportunity record during import. Closed-won and closed-lost amounts, expected close dates, and probability percentages migrate directly to the corresponding Odoo Opportunity fields.

Each HighLevel Pipeline becomes an Odoo CRM Pipeline with Stages inside it. Stage sequence order, name, and probability percentage migrate from HighLevel to Odoo. Odoo's stage configuration is managed through the CRM Pipeline settings or via Studio; we configure the pipeline structure during the schema design step before any Opportunity records are imported.

HighLevel Tags applied to Contacts migrate to Odoo CRM Tags. Tags are stored as many2many relationship records in Odoo linking back to the Contact (or Lead). We export the full tag list per contact and create the corresponding Tag records in Odoo before inserting the relationship links. HighLevel tag names with spaces are normalized to Odoo's tag format (slug-style or exact-match depending on the customer's preference).

HighLevel Custom Objects migrate to Odoo CRM custom models created via Odoo Studio or Python module. We introspect the HighLevel custom object's field schema during discovery, map data types (text to char, number to float or integer, date to date, checkbox to boolean, dropdown to selection field), and pre-create the destination model in Odoo before importing any records. Custom object relationships to standard objects (Contact, Company, Opportunity) migrate as many2one fields in Odoo with parent lookup resolution at migration time.

HighLevel Tasks linked to Contacts migrate to Odoo CRM Tasks (in the odoo_crm module these are often managed through the mail.activity model or the project.task model depending on the customer's Odoo configuration). We map task name, due date, assigned user (resolved via email match), and completion status. The original HighLevel task assignment is preserved via a custom field if the Odoo user resolution produces a different result.

HighLevel Users and Owners are resolved by email match against the Odoo destination User list. Any HighLevel Owner without a matching Odoo User is held in a reconciliation queue for the customer's admin to provision before the Opportunity and Task import phases proceed. Active and inactive status in HighLevel maps to the active flag in Odoo.

HighLevel Forms and Landing Pages are content artifacts with no direct Odoo equivalent in the CRM module. We export the form field structure (field names, field types, required flags) and page URL as a documented reference. Odoo Website or Odoo Sign handles form replacement; the customer's web team or an Odoo implementation partner rebuilds the form based on our documentation.

HighLevel Appointments map to Odoo Calendar Events. We extract appointment date, time, duration, contact association, and status. Calendar configuration (booking link, availability rules) does not migrate; we document the current HighLevel scheduling settings and provide a manual setup guide for Odoo Calendar or the Odoo Appointments module.

HighLevel Campaigns (email and SMS broadcast groupings) map to Odoo CRM Campaigns. Campaign name, description, and associated contact count migrate. Campaign performance metrics (open rates, click rates, delivery status) do not transfer because these are calculated from provider-level analytics not stored in HighLevel's record model.

Attachments linked to Contacts or Opportunities in HighLevel migrate to Odoo Attachments (ir.attachment records) linked via the res_model and res_id fields to the corresponding Contact, Company, or Opportunity record. Files exceeding 25MB are flagged during scoping for chunked migration with retry logic. We validate file integrity (checksum) after migration to confirm no data loss.