Migrate from Adobe Campaign to Salesforce Sales Cloud

Adobe Campaign nms:recipient is the primary profile table. Standard fields (email, format preference, address) map directly to Salesforce Contact fields. Custom fields added via schema extension land as custom properties or mapped to custom Contact fields. We set a custom field ac_original_email_format__c to preserve the Adobe Campaign format preference (HTML, text, or none) because Salesforce Contact has no native format equivalent.

Recipients designated as unconverted or marketing-only in Adobe Campaign may map to Salesforce Lead instead of Contact depending on the customer's buyer journey model. We define the routing rule during scoping based on subscription status and campaign engagement history.

BroadLog records track every message sent across email, SMS, and push channels. We map them to Salesforce CampaignMember records linked to the migrated Campaign, preserving send date, status (sent, bounced, delivered), and error reason. Aggregate open and click tracking logs map separately to CampaignMember custom fields because Salesforce CampaignMember has no native engagement score fields.

Adobe Campaign Campaign metadata (labels, start and end dates, type, status, budget) maps to Salesforce Campaign. We preserve campaign owner from Adobe Campaign as the Salesforce Campaign OwnerId resolved via User email lookup. Parent-child campaign hierarchy maps to Salesforce Campaign hierarchy natively.

Adobe Campaign Programs are hierarchical containers for Campaigns in Standard and v8. Folder structure and program labels migrate as Salesforce Campaign records with a Program__c custom field to preserve hierarchy depth. Program-specific permissions do not migrate and must be reconfigured in Salesforce at the destination.

Adobe Campaign Services represent opt-in subscription lists (e.g., weekly newsletter, product updates). Each Service maps to a Salesforce Campaign. The subscription relationship between Recipient and Service maps to CampaignMember with Status = Sent and a custom field ac_subscription_date__c carrying the original subscription timestamp.

Adobe Campaign delivery templates (email, SMS, push) contain routing parameters, content blocks, and personalisation tokens. We assess each template for migration: email templates with simple personalisation map to Salesforce Email Templates; templates with dynamic content blocks, conditional logic, or advanced personalisation are documented for rebuild in Marketing Cloud Content Builder or a custom object with Visualforce/Aura rendering.

Adobe Campaign custom tables created via nms:ext: namespace or FDA-linked external schemas require custom extraction logic. We inspect the schema XML to derive the underlying SQL table structure, then map to Salesforce custom objects with equivalent field types. Lookup relationships between custom schemas map to Salesforce lookup or master-detail relationships on the custom object.

Tracking logs (open, click, bounce events) are stored in NmsTrackingLog. We preserve click-through URLs and timestamped events as CampaignMember custom fields (ac_first_click_date__c, ac_last_click_url__c, ac_bounce_date__c). Aggregate open and click rates are recalculated at the destination; we do not import computed metrics that depend on the source platform's calculation engine.

Control groups in Adobe Campaign exclude populations from delivery targeting. We extract the exclusion criteria and reapply them as a Salesforce Campaign static group or a CampaignMember records with a control group flag. The rebuild approach is documented for the customer's admin to implement in Salesforce Flow or a list view.

Adobe Campaign enumerations defined in schema XML (e.g., deliveryStatus, gender, subscriptionStatus) may have different internal values in Salesforce. We maintain a value-mapping table keyed by enumeration name and map to Salesforce picklist values during import. Values without a Salesforce picklist match route to a custom picklist field with the original enumeration values preserved.

Adobe Campaign targeting workflows, campaign workflows, and technical workflows can be exported as XML packages. Dynamic content blocks and queryDef expressions frequently break across editions and do not migrate. We deliver a written inventory of every active workflow with its trigger, conditions, actions, and recommended Salesforce Flow equivalent. The customer's admin or a Salesforce partner rebuilds them post-migration.

Seed addresses are Adobe Campaign internal testing records used for proofing. They are instance-specific and not designed for cross-platform portability. We do not migrate seed addresses and recommend rebuilding proof lists in Salesforce using the customer's test contact set or Salesforce's built-in test sending capability.