Skip to content
Get a quote

Adobe Campaign to Salesforce migration

We migrate Recipients, Delivery logs, Campaign metadata, and Custom schemas from Adobe Campaign into Salesforce with the nms:recipient to Contact/Lead object model resolved upfront, FFDA dual-database records reconciled before export, and every Adobe Campaign Standard versus Classic schema difference handled before cutover.

Short answer

FlitStack AI migrates contacts, leads, campaign members, campaigns and campaign + campaignmembers from Adobe Campaign to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 5-8 weeks.

By

Source Adobe Campaign
DestinationSalesforce
ContactLeadCampaign MemberCampaignCampaign + CampaignMember
Mapped field by field · sample run · one-click rollback

What moves from Adobe Campaign to Salesforce?

Moving from Adobe Campaign to Salesforce is a structural data migration with significant platform model differences.

Read the full summary

Adobe Campaign uses an XML-schema-based data model centered on nms:recipient as the primary profile table with delivery logs split across local and cloud databases in v8's FFDA architecture. Salesforce uses a relational object model with Contacts, Leads, Accounts, and Opportunities. We extract Recipients via workflow-based data exports (bypassing the 100,000-row list ceiling), reconcile BroadLog records from both FFDA databases, and map the split Adobe Campaign recipient to a Contact with opt-in status preserved in a custom field. Delivery templates, campaign metadata, and custom schemas migrate as structured objects. Seed addresses, internal testing workflows, and Adobe-specific dynamic content blocks do not migrate; we deliver a written inventory for admin reconstruction. We do not migrate automations, CRM connectors, or IMS technical operator configurations as code.

1:1

Recipient (nms:recipient) → Contact

Adobe Campaign nms:recipient is the primary profile table.

How it maps

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.

1:1

Recipient → Lead

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.

How it maps

We define the routing rule during scoping based on subscription status and campaign engagement history.

1:1

Delivery logs (BroadLog) → Campaign Member (CampaignMember)

BroadLog records track every message sent across email, SMS, and push channels.

How it maps

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.

1:1

Campaign (nms:campaign) → Campaign

Adobe Campaign Campaign metadata (labels, start and end dates, type, status, budget) maps to Salesforce Campaign.

How it maps

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.

configuration

Program (Standard and v8) → Campaign (folder hierarchy)

Adobe Campaign Programs are hierarchical containers for Campaigns in Standard and v8.

How it maps

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.

1:N split

Service (opt-in subscriptions) → Campaign + CampaignMember

Adobe Campaign Services represent opt-in subscription lists (e.g., weekly newsletter, product updates).

How it maps

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.

What moves13 objects
Adobe CampaignSalesforce
  • RecipientContact1:1
  • RecipientLead1:1
  • Delivery logsCampaign Member1:1
  • CampaignCampaign1:1
  • ProgramCampaigntransformed
  • ServiceCampaignsplit

+ 7 more in the mapping below

How Adobe Campaign and Salesforce differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

DimensionAdobe CampaignSalesforce
Data modelXML-schema-based with nms:recipient as profile table; custom schemas via nms:ext: namespaceRelational object model with Contacts, Leads, Accounts, Opportunities, and custom objects __c
Multi-channelNative email, SMS, push, direct mail, WhatsApp orchestration in one platformCRM core; multi-channel via Marketing Cloud add-on products (Email Studio, Mobile Connect, WhatsApp Business)
Pricing modelPer 1,000 Active Profiles with channel add-ons; quote-based, commonly six to seven figures annuallyPer-user licensing from $25/User/Month (Essentials) to $330/User/Month (Unlimited); predictable at scale
Edition complexityThree active editions (Classic v7, Standard, v8) with incompatible schemas between eachSingle Sales Cloud edition family with tiered feature gates; no cross-edition schema incompatibility
Export mechanismList export capped at 100,000 rows; larger sets require workflow-based data extraction via Load file activityREST API, Bulk API 2.0, and Data Loader with documented rate limits and batch sizes
Data architecture v8FFDA dual-database: local PostgreSQL for real-time UI, cloud database for campaign executionSingle org database with standard object relationships; no dual-database split
Authentication v8.5+Adobe IMS mandatory for API integrations; legacy technical operators must migrate to server-to-server accountsOAuth 2.0 and Connected App model with no mandatory legacy migration path

Adobe Campaign to Salesforce field mapping

The 30 most-used fields of 35 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.

Field mapping5 shown
Adobe CampaignSalesforce
  1. @emailRecipient EmailContact
  2. @firstNameRecipient FirstNameContact
  3. @lastNameRecipient LastNameContact
  4. @phoneRecipient PhoneContact
  5. @mobilePhoneRecipient MobilePhoneContact
Adobe Campaign fieldSalesforce fieldMappingNote
Recipient.@emailContact.EmaildirectLowercase and trim. Used as primary dedupe key. Salesforce enforces 80 character limit.
Recipient.@firstNameContact.FirstNamedirectSalesforce enforces 40 character limit; truncate with audit note.
Recipient.@lastNameContact.LastNamedirectRequired field. Salesforce enforces 80 character limit.
Recipient.@phoneContact.PhonedirectPhone format follows the destination org's phone formatting setting.
Recipient.@mobilePhoneContact.MobilePhonedirectSame format rule as Phone.
Recipient.@titleContact.TitledirectSalesforce limit 128 characters.
Recipient.@birthDateContact.BirthdatedirectBoth fields are date; pass through in ISO format.
Recipient.location/@address1Contact.MailingStreetdirectAdobe Campaign location element maps to Salesforce mailing address.
Recipient.location/@cityContact.MailingCitydirect
Recipient.location/@regionCodeContact.MailingStatedirectValidate against Salesforce State and Country picklists if enabled.
Recipient.location/@postalCodeContact.MailingPostalCodedirect
Recipient.location/@countryCodeContact.MailingCountrytransformISO 3166-1 alpha-2 country code maps to Salesforce country name; validate against picklist if enabled.
Recipient.@formatPreferenceContact.ac_original_format__ctransformAdobe Campaign format preference (html, text, none) preserved in custom field; Salesforce Contact has no native format equivalent.
Recipient.@optInContact.HasOptedOutOfEmailtransformAdobe Campaign opt-in is inverted: opt-in true becomes HasOptedOutOfEmail false.
Recipient.@optOutContact.HasOptedOutOfEmaildirectAdobe Campaign opt-out flag maps directly to HasOptedOutOfEmail.
Recipient.@creationDateContact.CreatedDatedirectRequires audit field write permission on the destination org. Without it, we set ac_original_create_date__c.
Recipient.@lastModifiedContact.LastModifiedDatedirectSame audit field permission applies.
Recipient.@ownerId (technical operator)Contact.OwnerIdlookupResolved via technical operator to Salesforce User mapping by email or by provisioning matching Users in the destination org.
BroadLog.@broadLogIdCampaignMember.IddirectBroadLog primary key preserved as CampaignMember ID.
BroadLog.@statusCampaignMember.StatustransformAdobe Campaign broadLog status (delivered, sent, softBounce, hardBounce, excluded) maps to Salesforce CampaignMember Status values configured during scoping.
BroadLog.@contactIdCampaignMember.ContactIdlookupResolved via Recipient-to-Contact mapping by email as dedupe key.
BroadLog.@campaignIdCampaignMember.CampaignIdlookupResolved via Campaign-to-Campaign mapping by campaign label.
BroadLog.@logDateCampaignMember.ac_send_date__cdirectOriginal send date preserved in custom field. Salesforce CampaignMember has no native send date.
BroadLog.@errorReasonCampaignMember.ac_bounce_reason__cdirectBounce or exclusion reason preserved in custom field.
Campaign.@internalNameCampaign.NamedirectSalesforce Campaign Name limit 255 characters.
Campaign.@startDateCampaign.StartDatedirectISO date format.
Campaign.@endDateCampaign.EndDatedirectISO date format.
Campaign.@budgetCampaign.BudgetedCostdirectCurrency field; confirm currency alignment with the destination org's default currency.
Campaign.@statusCampaign.Statustransform
Campaign.@typeCampaign.TypetransformAdobe Campaign type enumeration (email, SMS, push, direct mail) maps to Salesforce Campaign Type picklist values.

What to watch for in a Adobe Campaign to Salesforce migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

FFDA dual-database splits BroadLog across two export endpoints

Adobe Campaign v8 writes BroadLog records to both a local PostgreSQL database (for real-time UI queries) and a cloud database (for campaign execution and reporting).

How we handle it

There is no single API endpoint that returns the complete, reconciled BroadLog set. We query both databases independently, cross-reference records by broadLogId, and deduplicate before loading to Salesforce CampaignMember. Migrations that query only one database end up with incomplete delivery history. This gotcha is specific to the Adobe Campaign v8 edition and does not apply to Classic v7 or Standard exports.

high

List export ceiling of 100,000 rows blocks direct extraction

Adobe Campaign Standard's list export feature caps output at 100,000 rows via the Nms_ExportListLimit option.

How we handle it

Any recipient export larger than this must use workflow-based data extraction with Load file and Transfer file activities. We configure chunked workflow exports with date-range filters or segment filters to handle unlimited volumes, combine the resulting files, and produce a single consolidated import set for Salesforce. This ceiling applies to Standard; Classic v7 deployments on-premise can use direct database queries to bypass it.

high

Dynamic content blocks and personalisation tokens do not survive cross-platform export

Adobe Campaign delivery templates contain personalisation tokens, dynamic content blocks, and queryDef expressions that reference Adobe Campaign-specific schema fields and operator syntax.

How we handle it

These do not translate to Salesforce Email Templates or Marketing Cloud Content Builder. We identify every template with dynamic content during the pre-migration audit, document its logic, and recommend a rebuild approach (Visualforce email template, Marketing Cloud AMPscript, or Flow-triggered email). Templates with only static content and standard personalisation tokens (e.g., first name) migrate directly.

medium

IMS mandatory authentication in v8.5+ breaks legacy API integrations

Adobe Campaign v8.5 and later require Adobe Identity Management System (IMS) for all API integrations.

How we handle it

Legacy technical operators created before this change must be migrated to server-to-server technical accounts via the Adobe Developer Console. We include IMS account migration in the v8 migration scope, verify API connectivity using the new credentials, and confirm that data extraction workflows authenticate correctly before declaring cutover complete. This gotcha is specific to v8.5+ and does not apply to v8.0 through v8.4.

medium

Enumerations in schema XML require explicit value mapping

Adobe Campaign schema enumerations (e.g., deliveryStatus, gender, subscriptionStatus) store internal integer or string values that differ from their display labels.

How we handle it

When migrating to Salesforce picklists, we must map both the display label and the internal value, not just the label text. If the destination Salesforce org uses a different picklist structure (e.g., global value set versus local picklist), the mapping must be explicitly rekeyed. We produce a complete enumeration value-mapping table during scoping and validate it against a test import before production migration.

How the migration runs

  1. Discovery and edition audit

    We audit the source Adobe Campaign instance across edition (Classic v7, Standard, or v8), recipient volume, active profile count, custom schema inventory, delivery log history depth, active workflows, and technical operator configuration.

    What this step covers

    We identify whether v8 FFDA dual-database extraction is required and whether IMS migration is in scope for v8.5+. The discovery output is a written migration scope, an enumeration value-mapping table template, and a Salesforce edition recommendation based on recipient volume and campaign complexity.

  2. Recipient export via workflow-based extraction

    We configure Adobe Campaign workflow exports using the Load file and Transfer file activities, chunking the export by date range or segment to bypass the 100,000-row list ceiling.

    What this step covers

    For v8 instances, we query both the local and cloud FFDA databases, cross-reference records by broadLogId, and produce a single reconciled recipient set. We run the export into a staging SFTP location, validate row counts against the in-platform count, and flag any recipients that should be classified as suppressed or inactive to avoid unintended Active Profile billing increments at the destination.

  3. Schema design and Salesforce sandbox migration

    We design the destination schema in Salesforce: custom objects for any Adobe Campaign custom schemas, custom fields on Contact and Campaign for Adobe Campaign-specific attributes (format preference, subscription date, bounce reason), Campaign Record Types for different delivery channel types, and picklist values configured from the enumeration value-mapping table.

    What this step covers

    Schema is deployed to a Salesforce Full Copy Sandbox first for validation with production-like data volume. The customer's marketing ops lead reconciles 25-50 recipient records and delivery log samples before production migration begins.

  4. Delivery log and tracking log export

    We export BroadLog records (message send history) and NmsTrackingLog records (open, click, bounce events) from Adobe Campaign.

    What this step covers

    For v8, this requires querying both FFDA databases and reconciling by broadLogId. We chunk the export by campaign date range, produce a per-campaign CSV set, and map each row to Salesforce CampaignMember records with custom engagement fields. Aggregate computed metrics (open rates, click rates) are not imported because they depend on the source platform's calculation engine; we import raw events instead and the destination reports recalculate them.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Salesforce Campaign records first (from Adobe Campaign Programs and standalone Campaigns), then Salesforce Contact records (from Recipients with opt-in status resolved), then Salesforce CampaignMember records (from BroadLog linked to migrated Contacts and Campaigns), then custom object records (from Adobe Campaign custom schemas with lookup relationships resolved), and finally tracking log custom fields (linked to CampaignMember).

    What this step covers

    Each phase emits a row-count reconciliation report before the next phase begins. We freeze Adobe Campaign writes during the cutover window and run a final delta migration of any records modified during the migration window.

  6. Delivery template inventory and workflow handoff

    We deliver a written inventory of every Adobe Campaign delivery template with a classification: migratable (static content, standard personalisation), rebuildable (dynamic content requiring Marketing Cloud AMPscript or Visualforce), or deprecated (references discontinued Adobe-specific features).

    What this step covers

    We also deliver the Workflow inventory document listing every active targeting and campaign workflow with its trigger, conditions, actions, and recommended Salesforce Flow equivalent. We support a one-week hypercare window for reconciliation issues. We do not rebuild Adobe Campaign workflows as Salesforce Flow inside the migration scope; that is a separate engagement.

Adobe Campaign Salesforce
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · SalesforceRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

5-8 weeksTypical, smaller accounts
12-20 weeksLarge or heavily customised accounts

A quote scales with recipient volume, custom schema complexity, delivery log history depth, and the number of Adobe Campaign editions in scope. Adobe Campaign subscription costs and Salesforce subscription costs remain the customer's recurring spend and sit outside the migration fee. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Adobe Campaign to Salesforce →

Why teams move from Adobe Campaign to Salesforce

  • Adobe Campaign's per-active-profile billing creates cost surprises as contact lists grow beyond initial contract estimates. Unlike Salesforce's per-user model, every imported record increments the Active Profile count regardless of engagement status. Teams migrating to Salesforce gain a predictable per-seat cost structure that scales more favorably for large prospect databases without triggering overage invoices.
  • Three active Adobe Campaign editions (Classic v7, Standard, and v8) with incompatible schema structures force teams into expensive version-locked migrations whenever they upgrade or consolidate. Salesforce's single edition family with tiered feature gates means no schema-breaking upgrades within a tier, reducing the risk of custom schema failures after platform changes.
  • Adobe Campaign's analytics and reporting lag behind enterprise expectations, particularly for multi-touch attribution and cross-channel performance analysis. Salesforce's reporting engine, especially with Salesforce Analytics (Einstein Analytics) or native Salesforce CRM Analytics, provides more flexible pipeline and campaign attribution reporting without requiring a separate business intelligence tool.
  • The v8 FFDA dual-database architecture complicates data extraction for any migration because BroadLog records split between local and cloud databases with no single export endpoint. Salesforce's single org database with documented Bulk API 2.0 means migration tooling can query, chunk, and load without reconciling two separate database writes on every record.
  • Adobe Campaign's API documentation gaps and version-specific restrictions make integrations brittle without specialist developer support. Salesforce's REST and Bulk APIs are extensively documented with public rate limits, SDKs in multiple languages, and a mature AppExchange ecosystem that reduces custom integration work for common CRM use cases.

Questions, answered

Adobe Campaign to Salesforce migration questions

How long does an Adobe Campaign to Salesforce migration take?

Most migrations land between five and eight weeks for accounts under 50,000 Recipients, one Adobe Campaign edition, and straightforward delivery log history. Migrations with v8 FFDA dual-database reconciliation, multiple custom schemas, large BroadLog histories (over 2 million records), or cross-edition scope (Standard plus Classic) move to twelve to twenty weeks because of the dual-database export complexity, custom schema extraction work, and schema validation in a Full Copy Sandbox.

Do Adobe Campaign Workflows and automations migrate to Salesforce?

No. Adobe Campaign targeting workflows, campaign workflows, and technical workflows use a different execution model from Salesforce Flow. Dynamic content blocks and queryDef expressions frequently break across Adobe Campaign editions and do not have a direct Salesforce equivalent. We do not migrate workflows as code. We deliver a written inventory of every active workflow with its trigger, conditions, actions, and a recommended Salesforce Flow rebuild approach. The customer's admin or a Salesforce partner rebuilds them post-migration.

Can we migrate Adobe Campaign delivery templates to Salesforce Email Templates?

Templates with static content and standard personalisation tokens (e.g., first name, email) migrate to Salesforce Email Templates directly. Templates with dynamic content blocks, conditional logic, Adobe Campaign-specific schema references, or advanced personalisation do not migrate as code. We document each template's logic and recommend a rebuild approach using Marketing Cloud Content Builder, AMPscript, Visualforce email templates, or Flow-triggered emails. The rebuild is not included in the migration scope.

Do we lose delivery log and tracking history during migration?

No. We export the complete BroadLog record set and NmsTrackingLog events from Adobe Campaign. For v8, this requires querying both FFDA databases and reconciling by broadLogId before loading to Salesforce CampaignMember. Open, click, and bounce events preserve as custom fields on CampaignMember. Aggregate open and click rates are recalculated at the destination from the raw event data we import.

How does Adobe Campaign v8 FFDA dual-database architecture affect the migration?

Adobe Campaign v8 writes profile data and delivery logs to two separate databases: a local PostgreSQL database for real-time UI interactions and a cloud database for campaign execution and reporting. There is no single API endpoint that returns the complete record set. We query both databases independently, cross-reference records by primary key, deduplicate, and produce a single consolidated export file. This step adds time and complexity to v8 migrations compared to Classic v7 or Standard, which use a single database.

Does Adobe Campaign IMS authentication migration affect the migration timeline?

Yes, for Adobe Campaign v8.5 and later. The mandatory IMS authentication transition requires migrating legacy technical operators to server-to-server technical accounts via the Adobe Developer Console. This must be completed before we can authenticate to the Adobe Campaign API for data extraction. We include IMS account migration in the v8.5+ migration scope and verify API connectivity using the new credentials before proceeding with data extraction. This typically adds one to two weeks to the overall timeline.

Can FlitStack AI also migrate Adobe Campaign Standard to Marketing Cloud Email Studio?

Yes. For customers who want to keep marketing execution within the Salesforce ecosystem, we offer Adobe Campaign Standard to Salesforce Marketing Cloud Email Studio migration as a parallel or subsequent scope. Marketing Cloud Email Studio uses a different content model (Content Builder versus Classic Content) and a different subscriber data model (Data Extension versus Contact). We migrate subscribers to Data Extensions, content to Content Builder, and document any AMPscript or API-based personalisation that requires rebuild. Journey Builder automations are documented but not migrated as code.

Get a quote

Moving from Adobe Campaign to Salesforce?

Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.

Get a quote