Migrate from OptiPub to Odoo CRM

OptiPub Subscriber records map to Odoo Contact (res.partner) records. Email address becomes the partner's email field, name maps to partner_name, and engagement history (open rates, click rates, last activity date) migrates to custom fields on the Contact record. Subscriber lifecycle status from OptiPub (active, churned, re-engaged) maps to a custom field optipub_lifecycle_stage on the Contact. We preserve custom subscriber properties as custom fields on res.partner.

Subscribers who have not yet converted to a known contact relationship map to Odoo Lead records. We use OptiPub's subscriber engagement score and subscription type to determine the split: low-engagement new subscribers map to crm.lead; high-engagement or paying subscribers map to Contact. The customer defines the threshold during scoping, and we apply it as a transform during migration.

OptiPub Segments are dynamic or static subscriber groupings. We map segment membership to Odoo Tags on the Contact or Lead record via the many2many_tags field. For Segments with complex membership criteria that cannot be expressed as tags, we create a custom many2many field optipub_segments on res.partner that stores the original segment name. Dynamic segment membership requires re-evaluation in Odoo through Server Actions or filters rather than real-time recalculation.

OptiPub Campaigns (email campaigns with subject lines, content, and scheduling) map to Odoo Project records for historical tracking, with each campaign creating a Project record and each A/B test variant becoming a Task within that project. Campaign send history, open rates, and click rates migrate to custom fields on the Task record. We do not recreate campaigns for re-sending; this is historical data migration only.

OptiPub Automation Rules with publisher-specific triggers (paid publication triggers, partner funnel steps) map to Odoo Action Rules and Server Actions, but the trigger logic requires manual redesign. We map the rule structure (trigger condition, delays, actions) and document the recommended Odoo equivalent during migration. The customer's admin rebuilds automation logic post-migration because Odoo's event-driven model differs from OptiPub's publisher-specific conditional branching.

OptiPub email templates migrate as attachments to a dedicated document directory in Odoo. Template metadata (name, usage history, last modified date) migrates to a custom model or custom fields on the attachment record. HTML templates retain their full markup; the customer repurposes them in Odoo's email composer or external email tools post-migration.

OptiPub Partner records (affiliate and partner management with domain monitoring and partner-level stats) map to Odoo Account records tagged with a custom partner_type field set to 'affiliate' or 'partner'. Partner-level revenue attribution maps to custom fields on the Account record. Domain monitoring and partner-specific metrics that have no Odoo equivalent are preserved as custom fields for the customer's admin to map to Odoo's reporting tools.

OptiPub embedded videos (Wistia, YouTube) store as URL references on the source Campaign or Template record. We preserve the video URL and any play statistics as custom fields on the migrated record. Video hosting connections require re-authentication at the destination; video playback within emails is not natively supported in Odoo CRM and requires a third-party app or re-linking the video host account.

OptiPub campaign send history (send timestamps, recipient counts, bounce rates) maps to a custom model we create in Odoo during migration. This preserves the sending performance data as structured records linked to the Campaign Project record rather than scattered across multiple field updates.

OptiPub's custom subscriber properties (beyond the standard fields) map to custom fields on the Odoo res.partner model. We create each custom field with the appropriate field type (char, selection, boolean, integer, float, date) based on the source data type. Field labels and help text are preserved from the OptiPub metadata. Custom fields with selection-type values require a manual migration of the picklist values to Odoo selection options.

OptiPub engagement data (open events, click events) migrates to Odoo Mail Message records linked to the Contact or Lead record. Each engagement event becomes a mail.message with a custom optipub_event_type field indicating 'open' or 'click', and a custom optipub_timestamp field preserving the original engagement timestamp. This preserves the engagement timeline but does not replicate OptiPub's real-time engagement tracking.

OptiPub's subscriber opt-out status maps to the standard Odoo Contact opt-out field (property_mail_unsubscribed on res.partner). We also preserve the opt-out timestamp and source (manual, list-unsubscribe, bounce) in custom fields optipub_unsubscribed_date and optipub_unsubscribed_source for compliance and re-engagement analysis.