Migrate from Adobe Campaign to Twenty CRM

Adobe Campaign Recipient records map to Twenty CRM Person records. Core fields (firstName, lastName, email, phone, address) migrate directly. Extended fields from custom schema extensions land as custom properties on Person. The recipient's subscription status to Services maps to a custom boolean field subscribed__c or to the Person's workspace membership depending on the customer's preference.

Adobe Campaign stores delivery address in the nms:address linked table or as address fields on nms:recipient. We extract the postal address fields (street, city, state/province, postalCode, country) and map them to Twenty's address fields on Person. If the address exists as a separate address table record, we perform a LEFT JOIN on recipientId to attach the correct address to each Person.

Adobe Campaign does not have a native Company object equivalent to a CRM Account. If the customer has extended nms:recipient with an organization field or uses a linked organization schema, we extract the distinct organization values and create Company records in Twenty CRM. The organization field on each Recipient is then linked via a lookup to the corresponding Company. If no organization data exists, we derive Companies from the email domain as a fallback.

Adobe Campaign Campaign records (labels, type, start and end dates, budget, status) map to Twenty CRM Opportunity records with a custom field campaign_type__c set to 'Marketing Campaign'. A single Adobe Campaign can generate multiple Opportunities if it contains distinct revenue-aligned programs. Campaign metadata (label, type, dates) migrates as Opportunity fields; internal Adobe Campaign workflow orchestration does not migrate.

Adobe Campaign Delivery records (email sends, SMS, push notifications) map to Twenty CRM Activity records with a type field set to 'Delivery' and a custom status field carrying the Adobe Campaign deliveryStatus value. The broadlog count (number of recipients targeted) migrates as a custom field broadlog_count__c. Delivery routing parameters do not migrate because Twenty CRM has no sending infrastructure.

BroadLog records track every message sent per recipient per delivery. We map each BroadLog entry to an Activity record on the corresponding Person, with deliveryLabel as the activity subject and status mapping to the activity result. BroadLog records are extracted from the cloud database in v8 FFDA environments. We preserve the send timestamp and the internal Adobe Campaign contact date for campaign attribution.

NmsTrackingLog records store open, click, and bounce events with timestamps and URLs. We map click events to Activity records with the target URL stored in a custom url__c field, and open events to Activity records with a type 'EmailOpened'. Bounce records map to a custom bounced__c boolean flag on the corresponding Activity. We preserve the original timestamp for chronological accuracy on the Person's timeline.

Adobe Campaign Services (opt-in subscription lists) do not have a direct Twenty CRM equivalent. We map each Service to a custom field on Person (e.g., newsletter_subscribed__c) with the subscriptionDate carried as a date value. If the customer has multiple Services, each becomes a separate custom boolean or date field on Person. Double-opt-in confirmation flags map as a secondary field.

Adobe Campaign Programs are hierarchical containers for Campaigns in Standard and v8 editions. Program names and types migrate as custom fields on the related Campaign-Opportunity records. Folder and folder-permission structure does not migrate; we recommend a post-migration folder organization strategy using Twenty's workspace or custom field scoping.

Extended schemas (nms:ext: prefix or custom namespaces) represent fields added beyond the standard nms:recipient structure. We inspect the schema XML to derive the underlying field names and data types, then create equivalent custom fields in Twenty CRM before migration. Relationship fields from custom schemas that link to other tables require additional lookup field creation and must be resolved before Person import.

Seed addresses are internal testing records for proofing and do not migrate. They are instance-specific and tied to the Adobe Campaign sending infrastructure. We recommend rebuilding proofing workflows in Twenty CRM or a dedicated email testing tool post-migration.