Migrate from Interactive to Odoo CRM

Interactive contacts map to Odoo crm.lead records. Odoo's crm.lead serves as both Lead and Opportunity depending on its mode flag. Standard fields (name, email, phone, job_title) transfer directly. Quiz-collected fields that distinguish between Lead and Opportunity mode become custom fields in Odoo.

Interactive contacts also create res.partner records in Odoo (type=contact) to support address storage, partner-specific fields, and company linkage. Odoo links crm.lead records to res.partner via partner_id, enabling the partner-level address and commercial data to appear on the lead form. This dual-record approach ensures that both contact-specific details and company-level information are accessible from the lead record.

Interactive company records map to res.partner with partner_short_name for display and industry categorization. The partner_is_company flag is set to True to distinguish company records from individual contacts. Contacts without a primary company link to a default 'Unassigned' partner record or stay as standalone contacts, preserving the original data structure without forcing artificial relationships.

Interactive deals map to crm.lead records in Odoo with type=opportunity (kanban_state determines open/won/lost). Each Interactive deal pipeline becomes a named stage within Odoo's pipeline, with stage probability and category re-applied based on Odoo's stage configuration. This transformation preserves the original deal progression logic while adapting it to Odoo's kanban-based workflow system.

Interactive quiz identifiers and lead-source data migrate as custom Char fields on crm.lead (e.g., x_quiz_id, x_lead_source). These preserve attribution context that Odoo's native source_id cannot capture if the quiz is not an Odoo-listed channel. This ensures complete tracking of where each lead originated, maintaining marketing analytics continuity.

Interactive's numeric lead_score migrates as a custom Float field x_lead_score on crm.lead. Odoo's native lead_scoring_ids relation is not overwritten — the quiz-based score is preserved separately for reference alongside any Odoo-native scoring created post-migration. This dual-scoring approach maintains historical lead qualification data while allowing new scoring models to be implemented.

Interactive tag values map to Odoo crm.lead.tag_ids through tag name matching. Tags that do not exist in Odoo are created during migration to preserve categorization. Tags with no Interactive equivalent in the destination are left blank, not auto-assigned, ensuring no incorrect categorization occurs during the transfer.

Interactive email engagement records migrate as Odoo mail.activity (activity_type=email, subject from quiz follow-up or notification, body preserving the original message). The parent_res_model and parent_res_id link the activity back to the crm.lead record, maintaining the complete activity history for each lead.

Interactive logged calls and meetings migrate as Odoo mail.activity records with activity_type set to 'call' or 'call' respectively, and subject preserving the call or meeting title. Duration migrates as a Float (hours) in Odoo's duration field. This preserves the full communication history for each contact and deal.

Interactive notes migrate as Odoo mail.message records on the crm.lead, with message_type=comment. Attachments are re-uploaded to Odoo's ir.attachment model and linked via the attachment_ids relation on mail.message, ensuring all documentation and files are preserved and accessible within the lead record.

Interactive owner IDs resolve by email match against Odoo res.users records. Matched users are assigned as the crm.lead user_id. Unmatched owners are flagged before migration; the team either invites them to Odoo first or assigns their records to a designated fallback user.

Interactive stores quiz-answer fields and custom contact properties as custom fields. Each property maps to an Odoo crm.lead custom field — Char for text values, Selection for pick-list values, Float or Integer for numeric responses. The migration plan enumerates every custom property and assigns the appropriate Odoo field type before data loads.