Migrate from Rule to Odoo CRM

Rule Contacts with lifecycle stages of subscriber, lead, or marketing qualified lead map to Odoo CRM Lead. Lifecycle stages of sales qualified lead, opportunity, or customer map to Odoo CRM Contact tied to a Partner (res.partner). We compute the split at migration time using Rule's lifecycle_stage property, and preserve the original stage in a custom Char field on both Lead and Contact for audit and reporting. Odoo's Lead-to-Opportunity convert action creates a Contact and optionally an Opportunity from a Lead; we document which Rule lifecycle stages map to that conversion path.

Rule Company records map to Odoo res.partner records of type 'company'. The company domain becomes the partner's website field and serves as the dedupe key during import. Odoo uses a single res.partner table for both individuals and organizations (with a parent_id link for company-child relationships), so we flag any Rule Company-Contact hierarchy for manual review of the correct Odoo partner tree structure before import.

Rule Deal records map to Odoo CRM Opportunity (crm.lead with type='opportunity'). The Rule dealstage property maps to Odoo's stage_id on crm.lead, and the pipeline assignment maps to an Odoo Sales Team (crm.team) that we configure before migration. Closed-Lost and Closed-Won dates from Rule custom fields migrate as Odoo closed_date fields on the Opportunity.

Each Rule deal pipeline becomes an Odoo CRM Sales Team with its own stage sequence (crm.stage records). Stage probability percentages migrate from Rule to the probability field on each crm.lead. We configure the stage sequence in Odoo via XML data or directly through the CRM settings before Opportunity records are imported.

Rule tags on contacts and companies migrate to Odoo CRM tags. Odoo stores tags as ir.model.data records linked to crm.lead Telegram. We preserve the original tag names and create matching tag records in Odoo before the contact and opportunity import so that tags are available as filters in the CRM pipeline view.

Rule custom fields on contacts (dropdown, date, numeric, text, or multi-select types) require pre-creation in Odoo via Odoo Studio or Python data migration scripts before data import. Multi-select fields in Rule map to Odoo many2many or char fields depending on whether Odoo supports a native multi-select implementation. We create the destination fields during schema design and validate the field types match before importing any records.

Rule email open, click, bounce, and unsubscribe events migrate to Odoo CRM Note records or Task records attached to the corresponding Lead, Contact, or Opportunity. The event type and timestamp are encoded in the Note body or Task description so that engagement history is available in the activity timeline. Odoo CRM does not have a native multi-channel engagement log, so we consolidate events into Notes annotated with the source channel for auditability.

Rule SMS and RCS engagement events migrate to Odoo CRM Note records attached to the corresponding Lead or Contact. Each Note records the channel (SMS or RCS), the original Rule event type (sent, delivered, failed), and the timestamp. We append the engagement event data to the Note body so it is visible in Odoo's activity timeline without requiring a native multichannel module.

Rule social media engagement events migrate to Odoo CRM Note records. Each Note is annotated with the social channel, event type, and original timestamp. Odoo CRM does not natively support social channel integration, so we treat social engagement history as historical Notes that provide an audit trail even if the channel activity is not ongoing in Odoo.

Rule automation workflows contain trigger conditions, time delays, and channel actions that do not transfer as executable code to Odoo. We export every active Rule workflow definition including its trigger type (event-based, date-based, tag-based), conditions, action sequence, and linked contacts or segments. We deliver this as a written Odoo automation rule specification document that the customer's Odoo admin uses to recreate the logic in Odoo's CRM automation rules (Automation > Automation Rules). Workflows referencing deleted or archived Rule contacts are flagged as orphaned triggers in this document.

Rule dynamic segments (filter-based lists) are exported as filter logic rather than record snapshots. We document each segment's filter conditions and recommend whether to recreate it in Odoo as a static CRM list (manually maintained) or as an Odoo dynamic filter using the same field criteria. If the customer uses Odoo Marketing, we map segments to mailing.contact segments where the platform supports it.

Rule suppression lists (unsubscribed, bounced, blocked contacts) migrate as Odoo mailing.contact records with opt_out=True or as partner records with a custom opt-out field depending on whether the Odoo instance includes the Odoo Marketing app. For Odoo CRM without Marketing, we set a custom Boolean field is_suppressed__c on res.partner to prevent the contact from being included in any future mailing or campaign.

Rule user accounts (name, email, role) map to Odoo res.users records. We resolve Rule owner assignments on contacts and deals by email match against the destination Odoo instance's user list. Users without a matching Odoo account go to a reconciliation queue for the customer's admin to provision. Active/inactive status in Rule does not automatically determine Odoo user state; the admin confirms before we proceed with owner assignment.

File attachments linked to Rule contacts or campaigns are exported via Rule's file API, downloaded locally, and re-uploaded to Odoo as ir.attachment records linked to the corresponding Lead, Contact, or Opportunity using the Odoo JSON-RPC API. Original filenames and MIME types are preserved.

Rule campaigns (grouping related automations and tracking aggregate performance) migrate as CRM campaigns in Odoo if the Odoo instance includes the CRM app with campaign tracking, or as a tagged group of Opportunities if the instance is CRM-only. Campaign metadata (name, start date, linked contact count) is preserved; historical engagement analytics are not replayable in Odoo and are delivered as a written summary for the customer's records.