Migrate from XMPie to Odoo CRM

XMPie automation logic has no CRM equivalent in Odoo

XMPie workflows and personalization rules are tied to campaign logic, audience filtering, and InDesign data-binding expressions — not to lead management. There is no meaningful Odoo CRM object to map them to. Attempting a literal translation produces broken automation rules that reference fields that do not exist in Odoo. We export XMPie workflow definitions as a JSON rebuild reference so your Odoo admin can reconstruct the intent using ir.actions.server and mail.activity records. We do not claim or attempt to preserve the automation logic itself.

Odoo External API requires Enterprise or Custom plan for external access

Odoo's xmlrpc API is available without additional cost on self-hosted Community instances. However, Odoo Online (cloud) restricts external API access to Enterprise and Custom plan customers. If your Odoo instance is on a Standard plan, you must upgrade or use database-level direct writes via the PostgreSQL connection. We verify the API availability during the discovery phase and adjust the migration method accordingly — using xmlrpc on Enterprise/Custom or direct SQL inserts on Community.

Recipient records lack a native lead-score or pipeline-stage attribute

XMPie does not have a deal-stage or lead-status field. Every recipient record lands in Odoo as a crm.lead with stage 'New' by default. If your team previously ranked recipients manually in XMPie (e.g., via a tier field or score field), that ranking must be mapped to a custom field and the Odoo lead score recalculated using Odoo's built-in AI scoring or a manual assignment rule. We cannot infer pipeline stage from XMPie data alone — that decision requires a business rule from your team.

Audience segment rules require manual rebuild as Odoo filters or domains

XMPie audience segments define recipient subsets using field-value conditions. These are expression-based rules (e.g., 'state equals CA AND last_purchase_date > 2024-01-01') with no native Odoo equivalent. Odoo segments are based on contact domains applied against the crm.lead model. We export the segment definition as structured JSON and flag it for your admin to rebuild as an Odoo domain filter or a saved filter on crm.lead. The exported JSON captures field names, operators, and values so your admin can reconstruct each segment's logic within Odoo's domain editor without losing business context.

Print assets and variable-data documents do not transfer as usable CRM attachments

Print assets and variable-data documents do not transfer as usable CRM attachments. XMPie stores PDF proofs, print-ready documents, and variable-data output files linked to recipients or campaigns. Odoo ir.attachment handles document storage but cannot interpret XMPie's proprietary document layouts or merge those assets into a functional CRM workflow. We re-upload referenced files as Odoo attachments with a plain-text note field pointing back to the original XMPie asset reference. The asset itself remains in XMPie or must be re-generated from source templates. For future reference.