Migrate from Odoo CRM to HighLevel

Odoo res.partner records with is_company=False map to GoHighLevel Contact. Standard fields (name, email, phone, street, city, country) migrate directly. Address components split into GoHighLevel's address1, address2, city, state, zip, country fields. partner_id on crm.lead resolves to the Contact lookup at migration time. Odoo partner tags migrate as GoHighLevel Contact tags.

Odoo res.partner records with is_company=True map to GoHighLevel Contact with company_name populated and contact_type set to company. Individual Contact records linked to the company link via the parent_id relationship. This creates a GoHighLevel company-based contact hierarchy matching Odoo's partner structure.

Odoo crm.lead records with type=lead and no linked Opportunity map to GoHighLevel Contact. The Odoo lead name becomes the Contact name; email, phone, and source_id transfer as custom fields or standard fields. Odoo lead stage (new, qualified, lost) maps to a GoHighLevel tag or custom field for segmentation. Unconverted leads remain as Contacts rather than Opportunities in GoHighLevel.

Odoo crm.lead records with type=opportunity map to GoHighLevel Opportunity. The linked Contact (partner_id) resolves to the GoHighLevel Contact created in the prior phase. expected_revenue and probability map to GoHighLevel Opportunity value and stage probability. date_deadline maps to close date. stage_id resolves to the GoHighLevel Pipeline stage name.

Odoo pipeline stages in crm.stage migrate as GoHighLevel Pipeline stages in the order defined in crm.team.stage.rel. Custom stage names are preserved verbatim. Each stage probability maps from Odoo's probability field to GoHighLevel's stage probability percentage. Stages with type=fold (archived) are excluded or set to inactive in GoHighLevel.

Odoo Sales Teams (crm.team) with member_ids and team-specific pipelines require a mapping decision. If the team has a distinct pipeline, we create a separate GoHighLevel Location and assign the team members as users within that location. If the team shares the main pipeline, team membership migrates as a Contact or Opportunity tag for segmentation. The customer selects the strategy during scoping.

Odoo mail.activity records linked to crm.lead migrate as GoHighLevel Tasks attached to the corresponding Contact or Opportunity. activity_type_id maps to a GoHighLevel task category (call, email, meeting, note, other). date_deadline preserves the due date. user_id resolves to the GoHighLevel user by email match. note fields migrate as task description text. High-volume activity exports are chunked by date range to avoid API timeout.

Odoo crm.tag records migrate as GoHighLevel tags applied to both Contact and Opportunity records. Tag names are preserved verbatim. Each crm.lead record's tag_ids many2many relation is resolved during the Contact and Opportunity import so that tags attach at insert time rather than in a separate reconciliation pass.

Odoo custom fields defined via Studio or custom addons on crm.lead are stored as columns in the database. We export field definitions (name, type, selection options) and create equivalent GoHighLevel custom fields under Settings > Custom Fields before data import. Field types map as: selection to dropdown, many2one to contact/opportunity reference, many2many to multi-select, char/text to text. Custom fields on Enterprise-only Odoo modules (Documents, WhatsApp) are flagged and excluded.

Odoo ir.attachment records linked to crm.lead are exported from the filestore and uploaded as GoHighLevel Contact or Opportunity attachments. Large attachment volumes (over 1 GB total) are chunked and sequenced after parent record import to avoid orphaned references. The original filename and mimetype are preserved. Attachments stored outside Odoo's filestore path are flagged for manual review.