Migrate from OptifiNow to Odoo CRM

OptifiNow's Lead Management module maps directly to Odoo's crm.lead object. We preserve lead source, assignment rules, and custom status fields as crm.lead fields. Odoo's lead stage field (stage_id) maps from OptifiNow's lead status. Custom OptifiNow lead routing rules that cannot be represented as Odoo stage transitions are documented as Odoo automated action requirements for the customer's admin to configure post-migration.

OptifiNow Contacts map to Odoo res.partner with address type set to 'contact'. Standard fields (name, email, phone, mobile) migrate directly. Activity history (calls, emails, meetings) links to the partner record via mail.message with model='res.partner' and res_id pointing to the partner ID. OptifiNow's tag associations map to Odoo tags (mail.thread.ids) using a many2many relationship.

OptifiNow Account records map to Odoo res.partner with partner_type='company'. The company hierarchy (parent account linking) migrates as parent_id on res.partner. Each Account's associated Contacts migrate as child res.partner records linked to the same parent company, preserving the OptifiNow account-to-contact relationship structure in Odoo's partner address book model.

OptifiNow Opportunities map to Odoo crm.lead records that have been moved through the lead2opportunity conversion wizard. The opportunity value, probability, and expected close date migrate as planned_revenue, probability, and date_deadline on crm.lead. Pipeline stage names from OptifiNow map to Odoo stage_ids within a specific Odoo sales team (crm.team). We configure Odoo stages to match OptifiNow stage labels during the schema setup phase before any data loads.

Each OptifiNow pipeline maps to an Odoo crm.team with its own crm.stage sequence. Stage names, probabilities, and is_won/is_closed flags configure in Odoo before migration. OptifiNow's custom pipeline fields (probability overrides, stage-specific custom data) require Odoo custom fields created via Odoo Studio or a custom module. We document the complete stage mapping in the migration workbook during the discovery phase.

OptifiNow custom objects (tenant-specific API objects enumerated during discovery) map to Odoo custom models. We create the destination custom model in Odoo with the same field types using Odoo Studio or a custom module (Python, XML data). Lookup relationships between custom objects and standard objects (Contact, Account, Opportunity) migrate as many2one fields pointing to the standard model's database ID. Custom object records import after the standard objects they reference, and we resolve foreign keys at migration time.

OptifiNow call logs migrate to Odoo mail.message records linked to the target res.partner or crm.lead via model and res_id. Call duration, disposition, and any recording URL store in custom mail.message fields. Activity timestamps preserve the original OptifiNow engagement date. Odoo's crm.phonecall model (if installed) can alternatively receive call data as crm.phonecall records for teams using Odoo's native phone module.

OptifiNow email engagement records migrate to Odoo mail.message with body containing the email content, email_from and email_to stored as message fields, and date matching the original timestamp. Emails linked to specific OptifiNow contacts or accounts resolve to the corresponding res.partner in Odoo. Thread history on a res.partner or crm.lead displays as Odoo's native chatter.

OptifiNow meeting records migrate to Odoo calendar.event with start, stop, name, and location preserved. Attendee records from OptifiNow meeting participants create calendar.attendee records linked to the event and to the corresponding res.partner invitees in Odoo. Recurring meeting patterns in OptifiNow are documented as Odoo recurring event configurations for the admin to rebuild.

OptifiNow task engagements migrate to Odoo project.task records within the CRM project's task list. Task status, priority, due date, and assigned user (resolved via email match to Odoo res.users) preserve. Tasks linked to specific OptifiNow opportunities or accounts map to tasks with a project_id pointing to the CRM project and a related_model/res_id pointing to the crm.lead or res.partner.

OptifiNow notes migrate as Odoo mail.message records with subtype='note' so they appear in the chatter thread but are visually distinguished from communications. Note body preserves formatting. Notes linked to multiple OptifiNow records (e.g., shared notes across an opportunity and its contacts) split into separate Odoo note records per target, with a comment noting the original multi-link in the migration summary.

OptifiNow Owner records (sales reps, administrators) map to Odoo res.users by email address match. Territory assignments and role-based pipeline routing from OptifiNow are documented for Odoo crm.team membership configuration. Any OptifiNow owner without a matching Odoo user goes to a reconciliation queue for the customer's admin to provision before record import resumes.

OptifiNow user records (including role and territory assignments) map to Odoo res.users. We extract OptifiNow user GUIDs, names, emails, and active status. Odoo res.users are provisioned by the customer's admin before migration; we resolve by email match and flag any OptifiNow user not yet in Odoo for provisioning.

OptifiNow email sequences and marketing automation triggers do not export as executable logic. We extract sequence templates as plain-text documentation (trigger conditions, delay values, action steps) and deliver this as a written rebuild guide for Odoo automated actions or a third-party email marketing tool. Odoo's email marketing is available as a separate app (Mass Mailing) but is not part of the CRM migration scope.