Migrate from Adobe Campaign to Odoo CRM

Adobe Campaign Recipients map to Odoo CRM Contacts. The nms:recipient standard fields (email, format preference, address, opt-out status) map to Odoo Contact fields directly. We inspect any schema extensions on nms:recipient and pre-create matching custom fields in Odoo Studio before migration. Recipients that are suppressions or hard bounces land as Contacts with opt_out=True to preserve suppression state at the destination.

Adobe Campaign Recipients without any sales-cycle engagement (no linked Opportunity, no reply, no click) split to Odoo Lead rather than Contact. We evaluate the broadlog records and engagement history to classify each Recipient: active campaign participants with click or reply history land as Contact; cold list profiles with no engagement land as Lead. The original Adobe Campaign profile data migrates in full on both paths.

Adobe Campaign Recipients optionally carry a company link via the @company field or an FDA-linked Account table. We resolve this to an Odoo CRM Contact with a linked Odoo Account (res.partner with customer=True). If the source has an FDA-linked external company table, we extract it separately and create the Odoo Account records first so that the Contact-Account relationship is satisfied at insert time.

Adobe Campaign campaign metadata (label, type, start date, end date, status) maps to Odoo CRM Campaign. Campaign identifier @internalName is preserved in a custom field ac_campaign_id__c for reference and audit. Campaign folders and programs map to the CRM Campaign's parent structure if the destination Odoo instance uses campaign hierarchies.

If the destination Odoo instance includes the Marketing Automation app, Adobe Campaign campaigns migrate as Odoo Marketing Campaigns with the same name and date range. Campaign targeting criteria (queryDef expressions) do not migrate as logic but are documented as a written list of segmentation rules for the admin to rebuild in Odoo's visual campaign builder.

Adobe Campaign BroadLog records (every sent message across email, SMS, push) are too granular for Odoo's activity model. We aggregate per-contact per-campaign: the most recent send date, total sends, total bounces, total opens (if tracking data is present), and total clicks. This summary migrates as an internal note on the Contact record in Odoo, tagged with the Adobe Campaign campaign name and date range. Individual broadlog rows do not import into Odoo because Odoo has no equivalent multi-channel delivery-log object.

Click-through URLs and timestamped tracking events are aggregated by contact and campaign and appended as structured notes on the Odoo Contact or Lead. The aggregated open rate, click rate, and bounce status per campaign are stored as custom fields on the contact. Aggregate campaign-level metrics are stored on the CRM Campaign record. Individual tracking log rows are not imported row-by-row.

Adobe Campaign Services (opt-in lists) map to Odoo Contact opt-in status. Subscription date migrates as a custom field subscription_date__c. Double-opt-in confirmation flags map to a subscription_confirmed__c boolean. The subscription list name is preserved in a custom field original_service_name__c so the admin can recreate the service as an Odoo mailing list or contact list post-migration.

Custom tables created via schema extension in the nms:ext: namespace or via FDA-linked external schemas require pre-migration XML inspection. We parse the schema XML to derive the underlying SQL table and field types, then generate equivalent Odoo Studio custom fields on the Contact or Lead model before import. Schema relationships (foreign keys, link fields) map to Odoo many2one or one2many fields where supported; circular or complex relationships are documented as custom-field limitations.

Adobe Campaign enumerations defined in schema XML (deliveryStatus, gender, etc.) may have different internal string values than Odoo's selection field options. We build a value-mapping table keyed by enumeration name and map source values to the nearest Odoo selection equivalents. Any unmapped values land in a custom text field with the original value preserved for admin review.

Seed addresses are internal proofing records specific to Adobe Campaign's delivery infrastructure. They do not migrate. We recommend rebuilding proof and seed testing directly in Odoo Marketing Automation's test-send feature.

Adobe Campaign delivery exclusion groups (control populations) are stored as queryDef expressions. We extract the exclusion criteria as a written segmentation specification and deliver it to the customer's admin for recreation as an Odoo Marketing Automation audience filter or CRM campaign exclusion list.