Migrate from Engage Messaging to Odoo CRM

Engage Messaging Contacts with active customer status, purchase history, or account association map to Odoo CRM Contact linked to an Account. Subscribers, trial users, and unconverted prospects map to Odoo Lead. We compute the split using Engage segment membership and custom field flags. Original Engage segment assignments preserve as a custom field engage_segments__c on the Odoo record for audit and segmentation rebuild.

Engage Segments define subscriber criteria lists that map to Odoo CRM Tags applied to Contact and Lead records. We export segment definitions as criteria lists and convert them to Odoo Tags during migration. The customer rebuilds segment logic in Odoo using its native Group and Tag filtering. Segment names with spaces normalize to Odoo's tag format (alphanumeric with underscores).

Engage Tags on Contact records migrate directly to Odoo CRM Tags. Tags are applied at import time using Odoo's mass tagging interface. Multi-value tags on a single Contact migrate as multiple Odoo Tags on the same record.

Engage Messaging Conversation threads map to Odoo CRM project/task activity records. Thread metadata (start time, last activity, message count) preserves in custom fields on the first activity record of the thread. Two-way conversation context is maintained so that inbound and outbound messages alternate as sequential activity entries.

Engage SMS messages migrate as Odoo Mail Message records linked to the parent Contact or Lead. Direction (inbound/outbound), timestamp, and delivery status migrate to custom fields. Odoo stores messages in the chatter thread of the contact or lead record.

MMS messages require independent file handling. We download multimedia attachments (images, audio, video) from Engage Messaging storage separately from the message export, map them to the correct Odoo Contact record, and attach them as Odoo IrAttachment records linked to the Mail Message. File size limits at Odoo (typically 25 MB per attachment via default configuration) may require compression for large video files.

Engage Messaging dedicated and toll-free numbers are locked to the platform and cannot transfer to Odoo CRM or any external system. We export number configuration metadata (number format, type, status) and flag all active numbers in a re-provisioning checklist. The customer coordinates number porting or replacement with an Odoo-compatible SMS gateway (Twilio, MessageBird, or similar) before the cutover window. We verify the replacement number is active and configured in Odoo before final cutover.

Engage Messaging agent and admin users map to Odoo CRM Users. We match by email address. Any Engage owner without a matching Odoo User goes to a reconciliation queue for the customer's Odoo admin to provision. Inactive Engage users map to Odoo Users with the Active flag set to false.

Engage Messaging custom contact properties migrate to Odoo CRM custom fields on the Contact or Lead model. Field type mapping: text to char, number to float or integer, date to date, checkbox to boolean, dropdown to selection. We create the Odoo custom fields via Studio or programmatically before import. Custom field API names follow Odoo's naming convention (x_studio_field_name).

Engage Messaging call logs map to Odoo CRM Task records with the Task Type set to Call. Call duration, disposition, and recording URL preserve in custom fields on the Task. Activity timeline ordering is maintained by setting the Odoo Task create_date to the original Engage call timestamp.

Engage Messaging notes on Contacts migrate to Odoo CRM Note records linked via the Odoo messaging system to the Contact or Lead. Rich text formatting in Engage notes converts to Odoo's internal HTML note format. Notes attached to specific messages link to the corresponding Mail Message record in Odoo.

Engage Messaging tasks assigned to Contacts map to Odoo CRM Task records with the responsible User resolved from the Engage owner mapping. Task status, priority, and due date migrate directly. Task assignment migrates by resolving Engage owner_id to the Odoo User ID via the Owner mapping.

Engage Messaging automated message sequences (triggers, delays, conditional branches) do not export as executable logic. We export sequence structure as a human-readable automation map document listing each sequence name, trigger condition, step order, message content, delay duration, and conditional logic. The customer rebuilds these in Odoo Workflow, Studio Automation, or a third-party sales engagement tool post-migration. This is a documentation-only deliverable inside the migration scope.

Engage Messaging delivery rates, click-through rates, and subscriber growth metrics are computed on-platform and not exposed via API. We recommend capturing screenshots of all Engage Analytics dashboards before the cutover window. Contact-level engagement data (opt-in timestamps, last message date, tag assignments) migrates normally and can be used to reconstruct basic engagement reporting in Odoo CRM's native dashboard.

Engage Messaging Subaccounts are platform-specific organizational units for team separation and permissions. Odoo CRM uses a standard User and Team hierarchy that does not map to Engage subaccount structures. We do not migrate subaccounts. The customer's Odoo admin creates Odoo Teams and assigns Users during post-migration configuration.

Engage Messaging contact opt-in status migrates to Odoo CRM's mailing.mailing_contact_id opt-out mechanism. We set Odoo's opt_out field to true for contacts marked as opted-out in Engage Messaging. Consent timestamps migrate to a custom field consent_date__c for regulatory audit purposes.

If Engage Messaging stores company or organization records linked to Contacts, these map to Odoo CRM Account records. The Account is created before Contact import so that the partner_id or parent_id relationship is satisfied at import time. Account contact information from Engage custom fields migrates to standard Odoo Account fields or custom fields.

Engage Messaging message templates (SMS and MMS body text, variable placeholders) export as a written template inventory document. Odoo CRM does not have a native SMS template object in the base CRM module; the customer rebuilds templates in the SMS gateway (Twilio, MessageBird) or in a third-party Odoo SMS integration app. We document the Engage template structure and variable mapping for recreation.