Migrate from Optimiser CRM to Odoo CRM

Optimiser Contact records map to Odoo res.partner. Standard fields (name, email, phone, street, city, country) migrate directly. Custom fields on Contact are enumerated during scoping and created as custom res.partner.fields before import. Partner addresses migrate as res.partner.address records. We use email as the dedupe key during import and preserve the original Optimiser contact ID in a custom field optim_id for reconciliation.

Optimiser Company records map to Odoo res.partner with the is_company flag set to True. Company name maps to name; domain or website maps to website. Custom properties on Company become custom res.partner.fields. Individual Contact records reference their parent Company partner via the parent_id field on res.partner. We resolve parent_id after both Company and Contact batches are loaded.

Optimiser Deals map to Odoo crm.opportunity. Deal name becomes opportunity name, deal value maps to planned_amount, expected close date maps to date_deadline, and owner maps to user_id via email resolution. Pipeline stage names are mapped via a stage-mapping table created during scoping. Lost and Won stage dispositions map to Odoo's stage probability and kanban colour coding. Deals without a matching Owner are assigned to a default Odoo user pending admin review.

Optimiser Lead records (where present as a separate object from Contact) map to Odoo crm.lead. Lead status maps to crm.lead.stage_id; lead score maps to a custom priority field. Odoo's crm.lead is the pre-conversion record; it becomes a crm.opportunity when the Convert action is triggered. If the customer prefers Leads to import directly as Opportunities, we set the stage to the customer's first pipeline stage and populate partner_id at import time.

Each Optimiser pipeline stage is mapped to an Odoo crm.stage record within the customer's Odoo pipeline. Stage probability percentages from Optimiser migrate to the probability field on crm.stage. Stage sequence order is preserved. We configure the kanban view to match the Optimiser pipeline layout. Any Optimiser stage with zero records is flagged as an empty stage that can be archived after migration.

Optimiser product records map to Odoo product.product. Product name, SKU, unit price, and cost map directly. If Optimiser products have category assignments, we create the corresponding product.category records in Odoo first. The product.product records are required before any Deal or Opportunity line items referencing products are imported.

Optimiser call engagement records map to Odoo crm.phonecall. Call duration, disposition, and timestamp migrate to the corresponding phonecall fields. The related Contact or Deal reference resolves to crm.lead or crm.opportunity via the optim_id mapping. crm.phonecall must be installed separately as part of the Odoo CRM module configuration.

Optimiser email engagement records map to Odoo mail.message with model set to crm.lead or crm.opportunity and res_id set to the migrated record ID. Email subject, body, sender, and recipient migrate. mail.message is linked via mail.activity records for timeline display. Attachments are stored as ir.attachment records and linked via the relation field.

Optimiser meeting records map to Odoo calendar.event. Start datetime, end datetime, location, and meeting title migrate. Attendees are resolved as crm.lead or crm.opportunity records via the optim_id mapping. Calendar event records are created after Leads and Opportunities are loaded so that partner_id references are satisfied.

Optimiser notes attached to Contacts or Deals migrate to Odoo mail.message with subtype set to comment. The body content, author, and timestamp are preserved. Notes linked to Deals inherit the crm.opportunity model and res_id reference from the parent Opportunity mapping.

Optimiser Owner records (name, email, role) map to Odoo res.users by email address match. We extract all distinct owner_ids referenced on Contact, Company, Deal, and Engagement records, then resolve against the destination Odoo res.users table. Owners without a matching Odoo user are held in a reconciliation queue for the customer's admin to provision before record import resumes.

Optimiser tags applied to Contacts or Deals export as label values. We create matching crm.tag records in Odoo and apply them to the corresponding crm.lead or crm.opportunity via the tag_ids many2many relationship. Tag names are preserved exactly. If a tag name in Optimiser matches an existing Odoo tag, we reuse the existing record rather than creating a duplicate.

Document attachments referenced by URL or stored in Optimiser's file store are downloaded locally, re-uploaded to Odoo's ir.attachment table, and linked to the correct parent record (res.partner, crm.lead, or crm.opportunity) via the res_model and res_id fields. Binary attachments migrate with original filename and MIME type preserved.

Optimiser custom objects (instances with non-standard modules or object types beyond standard CRM) migrate to Odoo custom models created via the Odoo ORM. We create the ir.model definition, add all custom fields via res.fields, configure access rights for the relevant res.users group, and import data via XML-RPC. Custom model naming follows Odoo's naming conventions and is validated against the ORM before migration begins.

Workflows, assignment rules, and triggered sequences built in Optimiser are stored in the platform's proprietary logic layer and are not accessible via export. We do not migrate automations as code. We document every active automation identified during scoping in a written checklist with its trigger conditions, actions, and recommended Odoo Action Rules or Automated Action equivalent. The customer's admin rebuilds these in Odoo Studio post-migration.