Migrate from Insightly Marketing to Odoo CRM

Insightly Contact maps to Odoo CRM Lead. We populate the Lead's partner_name (company name) with the parent Organization's name, contact_name with the person's full name, email from CONTACT_FIELD_EMAIL, and phone from CONTACT_FIELD_PHONE. The original Insightly lifecycle stage migrates to a custom Char field x_insightly_lifecycle_stage for audit. Contact ownership (insightly_owner_id) maps to Odoo user_id on Lead. Tags on Contact migrate to Odoo tag_ids via Odoo's Tags app, or to a custom Char field if the customer prefers a single-select reference.

Insightly Organization maps directly to Odoo res.partner with is_company=True. The ORGANIZATION_NAME field becomes partner_name, WEBSITE becomes website, INDUSTRY maps to industry_id if the customer has configured Odoo's industry taxonomy. Billing address and shipping address from Organization locations become Odoo's address fields (street, street2, city, state_id, zip, country_id). Organization CUSTOM_FIELD values map to custom Char, Integer, or Selection fields on Partner.

Insightly Contacts attached to an Organization migrate as Odoo Partner contact records under the Organization's Partner. The parent Organization becomes the Partner (is_company=True), and each Contact becomes a Partner record with parent_id pointing to the Organization Partner and contact_type=contact. This preserves the Organization-to-Contact hierarchy that Odoo uses for address and communication routing.

Insightly Lead object (separate from Contact) maps 1:1 to Odoo CRM Lead. LEAD_STATUS becomes x_insightly_lead_status on the Lead record. Lead source attribution (LEAD_SOURCE) maps to Odoo's medium_id or a custom field. Any lead-specific custom fields migrate as typed Odoo fields on the Lead.

Insightly Opportunity maps to Odoo CRM Opportunity. OPPORTUNITY_NAME becomes name, EXPECTED_VALUE becomes planned_revenue, PROBABILITY maps to x_probability (Odoo's standard probability is auto-calculated from stage, so we use a custom Float field). CLOSE_DATE becomes date_closed. STAGE_NAME maps to stage_id, but requires mapping against Odoo's existing stage values (New, Qualified, Proposition, Won, Lost) since Odoo uses a single pipeline.

Insightly pipeline stages require mapping to Odoo's stage_id values. If Insightly has multiple pipelines (Plus 5, Professional 15, Enterprise 50), we consolidate all stage names into Odoo's single pipeline stage sequence. Stage probability values from Insightly migrate to custom Float fields on the Opportunity since Odoo's default probability is derived from stage sequence position.

Insightly Project maps to Odoo Project (from the Project app). PROJECT_NAME becomes name, STATUS becomes project_status (on_hold, in_progress, completed). Milestones in Insightly map to Odoo Milestone records linked to the Project. TASK_LIST_NAME values become Odoo task names with their contained tasks migrated as Odoo task records. Project-to-Contact and Project-to-Organization links migrate as Odoo Project.partner_id and task-level partner_id references.

Insightly Tasks map to Odoo Project Task records. TASK_NAME becomes name, DUE_DATE becomes date_deadline, ASSIGNED_TO maps to user_id (resolved via Owner-to-User lookup). STATUS maps to x_insightly_task_status (Odoo task state uses kanban_state and stage_id). Related-to references (Contact, Organization, Opportunity, Project) map to Odoo's task fields: partner_id for contacts, project_id for projects, and opportunity_id for deals.

Insightly Notes migrate to Odoo mail.message records with message_type=notification attached to the relevant CRM record (Lead, Opportunity, Partner). NOTE_BODY in rich text maps to body HTML. NOTE_TITLE becomes the message subject. Created date and author (Owner) preserve using Odoo's message_date and author_id fields. Notes linked to Insightly Projects attach to the corresponding Odoo Project record.

Insightly custom field groups and custom fields map to Odoo ir.model.field records or Studio-created fields on the target model (crm.lead, res.partner, crm.lead, project.project, project.task). Field types map: Insightly TEXT to Char, NUMBER to Float or Integer, DATE to Date, PICKLIST to Selection, CHECKBOX to Boolean, CURRENCY to Monetary. Validation rules on Insightly custom fields require manual review to determine whether Odoo's constrains or SQL constraints are needed.

Insightly Tags on Contacts, Organizations, Opportunities, and Projects migrate to Odoo's utm.tag (available via the Tags app for CRM) as Tag records with their names preserved. The tag application_id links each tag to the CRM application. Alternatively, for tags that represent categorical data (e.g., industry segments, customer tiers), we migrate to a custom Selection or Char field on the Lead or Partner per the customer's preference.

Insightly custom objects (per-instance schemas) require a case-by-case migration design. We evaluate whether the custom object maps to an existing Odoo model (e.g., res.partner extension, crm.lead extension, project.task extension) or requires a new ir.model with custom fields. Odoo's model inheritance via _inherit allows extending standard models without a separate custom table, which is the preferred approach when the custom object relates to Leads, Partners, or Opportunities. Custom object relationships (lookups between custom objects) map to Odoo many2one or many2many fields on the appropriate model.