---
title: "Adobe Campaign to Salesforce Migration | FlitStack AI"
description: "Migrate Adobe Campaign to Salesforce with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/crm/adobe-campaign/to/salesforce-sales-cloud"
---

# 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.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See the field mapping →](https://flitstack.ai/migrations/crm/adobe-campaign/to/salesforce-sales-cloud#field-mapping)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Adobe Campaign ![](https://flitstack.ai/platforms-trim/adobe-campaign.webp)

Destination Salesforce ![](https://flitstack.ai/platforms-trim/salesforce-sales-cloud.webp)

Contact Lead Campaign Member Campaign Campaign + 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 moves 13 objects

Adobe Campaign Salesforce

- Recipient Contact 1:1
- Recipient Lead 1:1
- Delivery logs Campaign Member 1:1
- Campaign Campaign 1:1
- Program Campaign transformed
- Service Campaign split

\+ 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.

| Dimension            | Adobe Campaign                                                                                                 | Salesforce                                                                                                    |
| -------------------- | -------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| Data model           | XML-schema-based with nms:recipient as profile table; custom schemas via nms:ext: namespace                    | Relational object model with Contacts, Leads, Accounts, Opportunities, and custom objects \_\_c               |
| Multi-channel        | Native email, SMS, push, direct mail, WhatsApp orchestration in one platform                                   | CRM core; multi-channel via Marketing Cloud add-on products (Email Studio, Mobile Connect, WhatsApp Business) |
| Pricing model        | Per 1,000 Active Profiles with channel add-ons; quote-based, commonly six to seven figures annually            | Per-user licensing from $25/User/Month (Essentials) to $330/User/Month (Unlimited); predictable at scale      |
| Edition complexity   | Three active editions (Classic v7, Standard, v8) with incompatible schemas between each                        | Single Sales Cloud edition family with tiered feature gates; no cross-edition schema incompatibility          |
| Export mechanism     | List export capped at 100,000 rows; larger sets require workflow-based data extraction via Load file activity  | REST API, Bulk API 2.0, and Data Loader with documented rate limits and batch sizes                           |
| Data architecture v8 | FFDA dual-database: local PostgreSQL for real-time UI, cloud database for campaign execution                   | Single 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 accounts | OAuth 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) ↓](https://flitstack.ai/migrations/crm/adobe-campaign/to/salesforce-sales-cloud.csv) or open it in the [field mapping template](https://flitstack.ai/tools/field-mapping-template).

******Field mapping 5 shown

Adobe Campaign Salesforce

1. `@email` Recipient `Email` Contact
2. `@firstName` Recipient `FirstName` Contact
3. `@lastName` Recipient `LastName` Contact
4. `@phone` Recipient `Phone` Contact
5. `@mobilePhone` Recipient `MobilePhone` Contact

| Adobe Campaign field                      | Salesforce field                     | Mapping   | Note                                                                                                                                                          |
| ----------------------------------------- | ------------------------------------ | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Recipient.@email`                        | `Contact.Email`                      | direct    | Lowercase and trim. Used as primary dedupe key. Salesforce enforces 80 character limit.                                                                       |
| `Recipient.@firstName`                    | `Contact.FirstName`                  | direct    | Salesforce enforces 40 character limit; truncate with audit note.                                                                                             |
| `Recipient.@lastName`                     | `Contact.LastName`                   | direct    | Required field. Salesforce enforces 80 character limit.                                                                                                       |
| `Recipient.@phone`                        | `Contact.Phone`                      | direct    | Phone format follows the destination org's phone formatting setting.                                                                                          |
| `Recipient.@mobilePhone`                  | `Contact.MobilePhone`                | direct    | Same format rule as Phone.                                                                                                                                    |
| `Recipient.@title`                        | `Contact.Title`                      | direct    | Salesforce limit 128 characters.                                                                                                                              |
| `Recipient.@birthDate`                    | `Contact.Birthdate`                  | direct    | Both fields are date; pass through in ISO format.                                                                                                             |
| `Recipient.location/@address1`            | `Contact.MailingStreet`              | direct    | Adobe Campaign location element maps to Salesforce mailing address.                                                                                           |
| `Recipient.location/@city`                | `Contact.MailingCity`                | direct    |                                                                                                                                                               |
| `Recipient.location/@regionCode`          | `Contact.MailingState`               | direct    | Validate against Salesforce State and Country picklists if enabled.                                                                                           |
| `Recipient.location/@postalCode`          | `Contact.MailingPostalCode`          | direct    |                                                                                                                                                               |
| `Recipient.location/@countryCode`         | `Contact.MailingCountry`             | transform | ISO 3166-1 alpha-2 country code maps to Salesforce country name; validate against picklist if enabled.                                                        |
| `Recipient.@formatPreference`             | `Contact.ac_original_format__c`      | transform | Adobe Campaign format preference (html, text, none) preserved in custom field; Salesforce Contact has no native format equivalent.                            |
| `Recipient.@optIn`                        | `Contact.HasOptedOutOfEmail`         | transform | Adobe Campaign opt-in is inverted: opt-in true becomes HasOptedOutOfEmail false.                                                                              |
| `Recipient.@optOut`                       | `Contact.HasOptedOutOfEmail`         | direct    | Adobe Campaign opt-out flag maps directly to HasOptedOutOfEmail.                                                                                              |
| `Recipient.@creationDate`                 | `Contact.CreatedDate`                | direct    | Requires audit field write permission on the destination org. Without it, we set ac\_original\_create\_date\_\_c.                                             |
| `Recipient.@lastModified`                 | `Contact.LastModifiedDate`           | direct    | Same audit field permission applies.                                                                                                                          |
| `Recipient.@ownerId (technical operator)` | `Contact.OwnerId`                    | lookup    | Resolved via technical operator to Salesforce User mapping by email or by provisioning matching Users in the destination org.                                 |
| `BroadLog.@broadLogId`                    | `CampaignMember.Id`                  | direct    | BroadLog primary key preserved as CampaignMember ID.                                                                                                          |
| `BroadLog.@status`                        | `CampaignMember.Status`              | transform | Adobe Campaign broadLog status (delivered, sent, softBounce, hardBounce, excluded) maps to Salesforce CampaignMember Status values configured during scoping. |
| `BroadLog.@contactId`                     | `CampaignMember.ContactId`           | lookup    | Resolved via Recipient-to-Contact mapping by email as dedupe key.                                                                                             |
| `BroadLog.@campaignId`                    | `CampaignMember.CampaignId`          | lookup    | Resolved via Campaign-to-Campaign mapping by campaign label.                                                                                                  |
| `BroadLog.@logDate`                       | `CampaignMember.ac_send_date__c`     | direct    | Original send date preserved in custom field. Salesforce CampaignMember has no native send date.                                                              |
| `BroadLog.@errorReason`                   | `CampaignMember.ac_bounce_reason__c` | direct    | Bounce or exclusion reason preserved in custom field.                                                                                                         |
| `Campaign.@internalName`                  | `Campaign.Name`                      | direct    | Salesforce Campaign Name limit 255 characters.                                                                                                                |
| `Campaign.@startDate`                     | `Campaign.StartDate`                 | direct    | ISO date format.                                                                                                                                              |
| `Campaign.@endDate`                       | `Campaign.EndDate`                   | direct    | ISO date format.                                                                                                                                              |
| `Campaign.@budget`                        | `Campaign.BudgetedCost`              | direct    | Currency field; confirm currency alignment with the destination org's default currency.                                                                       |
| `Campaign.@status`                        | `Campaign.Status`                    | transform |                                                                                                                                                               |
| `Campaign.@type`                          | `Campaign.Type`                      | transform | Adobe 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.

![](https://flitstack.ai/platforms/adobe-campaign.svg) Adobe Campaign ![](https://flitstack.ai/platforms/salesforce-sales-cloud.svg) Salesforce

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Salesforce Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**5-8 weeks** Typical, smaller accounts

**12-20 weeks** Large 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 →](https://flitstack.ai/contact)

## 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.

## Related migrations

[![](https://flitstack.ai/platforms-trim/salesforce-sales-cloud.webp) Migrate to **Salesforce** Every source we move into Salesforce, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/crm/salesforce-sales-cloud)

### [Salesforce implementation](https://flitstack.ai/services/salesforce-implementation)

[Set up Salesforce and migrate into it as one engagement.](https://flitstack.ai/services/salesforce-implementation)

[See the service →](https://flitstack.ai/services/salesforce-implementation) [**Ontraport to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/ontraport/to/salesforce-sales-cloud) [**Vendasta to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/vendasta/to/salesforce-sales-cloud) [**BoomTown to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/boomtown/to/salesforce-sales-cloud) [**BlinQ to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/blinq/to/salesforce-sales-cloud) [**Podio to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/podio/to/salesforce-sales-cloud) [**Mautic to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/mautic/to/salesforce-sales-cloud)

## Sources: official documentation

1. [Custom Field Attributes — Salesforce Help (External ID)](https://help.salesforce.com/s/articleView?id=platform.custom_field_attributes.htm)
2. [Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help](https://help.salesforce.com/s/articleView?id=000380434\&type=1)
3. [Uploading Activity data to Salesforce — Salesforce Stack Exchange](https://salesforce.stackexchange.com/questions/15694/uploading-activity-data-to-salesforce)
4. [Sandboxes — Staging Environments for Customizing and Testing](https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/deploy_sandboxes.pdf)
5. [Case Comment STRING\_TOO\_LONG — Salesforce Stack Exchange](https://salesforce.stackexchange.com/questions/44763/case-comment-error-string-too-long-body-data-value-too-large)
6. [Salesforce Data Migration: 7 Challenges and How to Solve Them — DEV](https://dev.to/prince_6a5fbc059971cef8c8/salesforce-data-migration-7-challenges-and-how-to-solve-them-3bb7)
7. [Salesforce Duplicate Management — Salesforce Stack Exchange](https://salesforce.stackexchange.com/questions/151012/salesforce-duplicate-management-importing-duplicates)

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](https://flitstack.ai/contact)
