Migrate from Plezi to Odoo CRM

Plezi Contacts map to Odoo CRM Lead. Standard properties (name, email, phone, company) migrate directly. The Plezi lifecycle_stage and behavioral scoring profile do not have native Odoo CRM equivalents; we preserve both in custom Lead fields lifecycle_stage__c and scoring_profile__c as structured JSON so the customer's admin can act on the data in Odoo Studio. Company association in Plezi maps to a Lead company_name string, with a separate Company record created in Odoo CRM if the contact is linked to a Plezi Company with enrichment data.

Plezi Company records map to Odoo CRM Company. Company name, domain, industry, size, and any custom enrichment properties migrate to the Odoo Company fields and custom fields. The Odoo Company is created before the associated Contact or Lead import so that the relational reference is satisfied at insert time. Where Plezi Company enrichment data includes third-party sourced fields, we store the source attribution in a custom field enrichment_source__c.

Plezi Campaigns map to Odoo CRM Campaign. Campaign name, type, start date, end date, budget, and channel metadata migrate to the corresponding Odoo Campaign fields. Campaign cost data from Plezi migrates to Odoo's crm_campaign.planned_cost field. If the campaign has associated contacts, we create Campaign Influence or Sales Team membership records in Odoo to preserve the relationship.

Odoo CRM does not include a native landing page builder; landing pages require the Odoo Website module or a third-party tool. We export the Plezi landing page title, URL slug, and form reference during the audit phase. We document every page's structure, form field configuration, and any embedded third-party content (webinar iframes, live chat scripts, custom JavaScript widgets) for the customer's admin to rebuild manually. Embedded third-party widgets are flagged individually because they cannot be extracted and will not appear in the Plezi export. This is pair-specific because it affects the migration completeness for marketing teams that rely on Plezi landing pages as a primary lead-capture channel.

Plezi Forms capture leads and feed them into Smart Campaigns. We export form field names, required flags, and the target pipeline stage assignment. Custom field types are mapped to the closest Odoo equivalent (text, integer, date, email). The form itself does not migrate because Odoo CRM has no native form builder; we document the full form configuration for rebuild in Odoo Survey (for standalone lead qualification forms) or Odoo Website contact forms. The target Smart Campaign stage assignment is documented as a manual step in Odoo lead creation.

Plezi Smart Campaigns store trigger-action logic in a platform-specific format that cannot be exported as runnable automation. We reconstruct each Smart Campaign's intent by exporting the campaign trigger events, conditional rules, and action sequence as a written inventory document. The document includes trigger type (form submission, email open, page visit, score change), all condition branches, and the full action sequence. Odoo Studio automation (server actions, automated activities, mail templates) is the equivalent rebuild target. The customer's admin or an Odoo consultant uses the inventory document to reproduce Smart Campaign logic in Odoo Studio. This is the highest-severity pair gotcha because the automation intent is not automatically portable.

Plezi Workflows manage multi-step nurture sequences with step references to Contacts or Companies. We export the step sequence and associated content blocks as a written document. Dynamic content personalization steps are flagged individually because they cannot be automatically reproduced in Odoo Studio without manual mapping of the personalization variables. Odoo Studio's mail templates and automated activities cover most nurture sequence use cases.

Emails and content blocks used inside Plezi Smart Campaigns and Workflows are exportable as HTML and text variants. We import the HTML body and subject line as Odoo CRM email templates via the mail.template model. Inline images may require re-hosting in the Odoo media library; we flag any image references that point to external URLs for manual re-uploading. Email template variables (%customer_name%, %company_name%, etc.) are documented with their Plezi equivalents for the admin to remap in Odoo's qweb template syntax.

Plezi user accounts include name, email, and role. We export user records and attempt to map roles to Odoo's permission groups (Sales / Administrator / Custom). Plezi-specific role names that have no direct Odoo equivalent are flagged for manual review during the Odoo user provisioning phase. Owner references on Contacts, Companies, and Campaigns are resolved by email match against the Odoo User table. Any Plezi owner without a matching Odoo User is held in a reconciliation queue until the customer's admin provisions the account.

Plezi Contact and Company tags migrate to Odoo CRM Tags. Tags are a native field type in Odoo CRM Lead and Contact models. We export all tag names and their associated record references, then import them into Odoo where they attach to the corresponding Lead or Contact records. Tags used for segmentation in Plezi Smart Campaigns are documented in the automation inventory so the customer can reproduce segmentation in Odoo using the Tag field and Odoo Studio domain filters.

Plezi behavioral scoring profiles are structured data attached to each Contact. Odoo CRM has no native scoring engine. We store the full scoring profile as a custom JSON field scoring_profile__c on the Odoo Lead model, preserving all behavioral signals (page views, email opens, form submissions, engagement scores) for the customer's admin or RevOps team to act on through Odoo Studio or a third-party scoring tool integrated with Odoo.

If Plezi carries product records linked to Campaigns or scoring profiles, these map to Odoo Product variants. We resolve the product schema against any existing Odoo Inventory or Purchase module to avoid conflicts if the Odoo ERP is already live. Product names, SKUs, and pricing data migrate directly. Product images and descriptions are stored as Odoo product template attachments.