Migrate from Salesforce Marketing Cloud Account Engagement to Odoo CRM

Account Engagement Prospects map to Odoo Contact (res.partner). Email address is the dedupe key for both platforms. We use a three-pass matching strategy: exact email match, normalised email match (lowercased, stripped of dots in Gmail addresses), then flagged for manual resolution if no match exists. Pardot prospect_id is preserved in a custom field pardot_prospect_id__c for audit trail. Scoring values (total_score, demographic_score, behavioural_score) migrate as integer custom fields; Pardot grade migrates as a text field.

Account Engagement has no native Account object — Prospects are associated to Accounts via the Salesforce CRM sync. We create or match Odoo Company records (res.partner with is_company=True) using the domain extracted from the Prospect email address or the stored company_name field. Company records are imported before Contact records to satisfy the partner_id foreign key. Company Phone, Website, Street, City, State, Country, and zip migrate directly.

Pardot Scoring Categories (named buckets such as behavioural score, demographic score) map to Odoo CRM Tags on the Contact record. We export category definitions and their weight rules as a configuration document. Odoo does not have a native lead scoring engine, so the customer's admin rebuilds scoring logic using Odoo Workflow server actions or a third-party marketing automation tool. Tags preserve the Pardot category labels so that segmentation rules can be recreated manually.

Account Engagement Custom Fields are first-class API objects exported via Pardot v5 API with label, type, and per-record values. We map each custom field to an Odoo custom field on res.partner (for Prospect-level fields) or crm.lead (for Opportunity-level fields). Field types map as follows: text to char, long text to text, number to float or integer, date to date, dropdown to selection, checkbox to boolean. Required fields on Pardot are set as required in Odoo Studio before import begins.

Account Engagement Campaigns track marketing initiative performance and link to Salesforce Campaigns. We export Campaign metadata (name, status, type, start date, budget) and map them to Odoo CRM Tags applied to the Contacts that were members of each campaign. Prospect-level activity data (opens, clicks, form submissions) is preserved as custom fields on the Contact record rather than as campaign membership records, since Odoo CRM does not have a native Campaign Member object equivalent.

Engagement Programs in Account Engagement reference internal Pardot IDs for Prospects, Campaigns, Forms, and Landing Pages. These IDs do not exist in Odoo, making direct migration structurally impossible. We do not migrate Engagement Programs as functional assets. We document the existing program structure during scoping — program name, trigger conditions, step sequence, completion actions, and associated assets — and deliver this as a written automation inventory document for the customer's admin to rebuild in Odoo Workflow or a third-party automation platform such as Mautic, Brevo, or ActiveCampaign.

Automation Rules in Account Engagement are triggered by Prospect actions (form fills, email opens, page visits, score changes) and execute CRM updates, list assignments, and email sends. They reference internal Pardot object IDs and cannot be imported into Odoo. We export a machine-readable inventory of every Automation Rule during scoping (trigger type, filter criteria, actions, and completion actions) and include it in the automation rebuild document. Odoo Workflow triggers (on_create, on_write, on_state_change, server_action) are the native replacement.

Account Engagement Forms capture Prospect data and are tied to Landing Pages and Custom Fields via internal Pardot form IDs. We export form definitions (field labels, types, visibility rules, and thank-you message content) as a structured document. Odoo CRM does not have a native form builder in the standard CRM module; the customer's admin rebuilds forms using Odoo Studio or an external form tool such as Typeform, HubSpot Forms, or Gravity Forms that pushes submissions into Odoo Contacts via API or webhook.

Landing Pages are static web assets hosted within or referencing Account Engagement. We export page HTML content and metadata (page name, URL slug, associated forms, and conversion tracking settings) as a structured reference document. Landing Page URLs are internal to Account Engagement and cannot be redirected to Odoo without a custom domain configuration. The customer's marketing team rebuilds landing pages in their preferred tool (Odoo Website builder, WordPress, or a dedicated landing page platform) using the exported content as a template.

Account Engagement Email Templates contain HTML content, dynamic content blocks, and Pardot merge fields using double-brace syntax (%%first_name%%). We export template HTML and metadata, then rewrite merge field syntax from Pardot %%field_name%% to Odoo Jinja2 {{field_name}} format. Basic single-field substitutions migrate automatically. Dynamic content blocks with conditional branching logic are flagged for manual review and marketer-level rebuild in Odoo email template editor.

Account Engagement Users (Assigned Users / Owners) correspond to Salesforce Users who are responsible for Prospect records. We map Pardot user records to Odoo Users by email address. Account Engagement-only users without a corresponding Salesforce User are matched to Odoo users by email; users without a match go to a reconciliation queue for the customer's admin to provision before record import resumes. Pardot Business Unit assignment maps to Odoo Sales Team.

Account Engagement Static Lists segment Prospects for targeted campaigns. We export list memberships and apply the list name as a Tag on each Contact in Odoo CRM. List-level metadata (name, description, created date) migrates as part of the tag documentation. Static list membership is preserved because tags on res.partner are the Odoo-native segmentation mechanism.

Dynamic Lists in Account Engagement are rule-based queries that generate a live membership list from Prospect criteria. Dynamic lists cannot be migrated as active lists because the rule syntax (field comparisons, operators, logical conditions) is Pardot-specific and has no Odoo equivalent. We export the list definition (criteria fields, operators, values) as part of the segmentation inventory document for the customer's admin to recreate using Odoo custom fields, tags, and domain filters.

Account Engagement Business Units partition Prospect records, Users, and branding within a single instance. The Pardot API operates within a single Business Unit scope — there is no API endpoint to cross-query all BUs simultaneously. We scope each Business Unit as a separate migration project, export its Prospect records independently, and map each BU to a distinct Odoo Sales Team. Business Unit configuration (sender profiles, tracking domains, IP warm-up pools) does not migrate and is documented for manual configuration in the customer's email sending tool.

Tags in Account Engagement are used for Prospect segmentation and are exported via the Pardot v5 API with tag definitions and their assignments per Prospect. Tags merge cleanly into Odoo CRM Tags on res.partner. We export the complete tag taxonomy (tag name, description, associated Prospect count) and apply all tag assignments during the Contact import phase.

Account Engagement Visitor Activities (form fills, email opens, page views, link clicks) and CRM activities (calls, emails, meetings) migrate as Odoo CRM Activities linked to the Contact record. Each activity type maps to an Odoo activity category: calls to Call, emails to Email, meetings to Meeting, and form submissions to Upload Document. Note that Odoo CRM does not have a native visual engagement timeline for marketing interactions; activities land as CRM activity records rather than a Pardot-style engagement history panel.

Account Engagement does not create or manage Opportunities internally — Opportunities live in Salesforce CRM. We export the linked Salesforce Opportunity ID stored on the Prospect record, along with Opportunity name, stage, amount, close date, and owner email. These map to Odoo CRM Leads (crm.lead) in the sales pipeline, with stage mapped to the Odoo CRM pipeline stage configuration. The Pardot opportunity_id is preserved in a custom field for audit purposes.

Account Engagement Custom Objects are available from the Advanced+ tier upward and are exported via the Pardot v5 API. We pre-create a corresponding Odoo custom model (using Odoo Studio or directly via model definition) including all custom fields, field types, and any lookup relationships to res.partner. Custom object records import after parent Contact records to satisfy foreign key constraints. Validation rules defined in Odoo Studio are configured before import begins.