Migrate from Smarketing Cloud to Salesforce Sales Cloud

Smarketing Cloud Contacts map directly to Salesforce Contacts. Standard fields (FirstName, LastName, Email, Phone, Title) migrate as-is. Smarketing Cloud custom Contact properties require a discovery audit before migration because the platform's property model is built incrementally per account with no public schema reference. We create matching custom fields in Salesforce (with the correct field type: text, number, date, picklist, checkbox) before import. Any Smarketing Cloud lifecycle or status labels are preserved in a custom field smarketing_original_status__c rather than forced into Salesforce's standard Status picklist.

Smarketing Cloud Company records map to Salesforce Account. The Company Name becomes Account Name; website domain becomes the Website field and serves as the dedupe key during import. We export Company and Contact together to preserve the linkage table; Account must be created before Contact import so that AccountId is resolved at insert time. Parent-company hierarchy in Smarketing Cloud maps to Salesforce's Parent Account lookup if configured.

Smarketing Cloud Pipelines map to Salesforce Opportunity Record Types, each paired with a corresponding Sales Process that defines the allowed Stage values. We export the full stage sequence and stage order from Smarketing Cloud, then configure Salesforce Stage values (StageName, Probability, IsClosed, IsWon) before migration. Stage names are remapped through an explicit value-mapping table agreed with the customer during scoping.

Smarketing Cloud Campaigns map to Salesforce Campaign. Campaign Name, Type, Status, StartDate, and EndDate migrate directly. Campaign membership (which Contact was enrolled in which Campaign and when) migrates to Salesforce CampaignMember with the original enrollment timestamp preserved. Campaign member statuses are mapped through a value table because Smarketing Cloud's status labels (Subscribed, Active, Enrolled) differ from Salesforce's default CampaignMember Status values.

Smarketing Cloud Activity logs (call, email, meeting, note) linked to Contacts and Companies map to Salesforce Task, Event, and EmailMessage records. Call activities become Task with TaskSubtype=Call; meeting activities become Event with StartDateTime and EndDateTime; email activities become EmailMessage (body) linked to a Task (timeline entry). We resolve the parent Contact and Account by email match and ID lookup before insert. Historical timestamps are preserved by setting ActivityDate to the original Smarketing Cloud activity date.

Smarketing Cloud tags applied to Contacts and Companies migrate to a Salesforce custom field (smarketing_tags__c) as a semicolon-delimited text string or as a multi-select picklist if the tag set is bounded. We agree on the tag strategy during scoping: text format is simpler but less filterable; multi-select picklist enables list views but requires a defined value set. Tags used for segmentation in Smarketing Cloud are documented separately as filter criteria for Salesforce Reports and List Views.

Static Smarketing Cloud Lists map to Salesforce Campaigns with Type=Manual or Type=Advertisement/List. We export the full list membership (Contact ID and list assignment) and create Salesforce CampaignMember records linking each Contact to the Campaign. The list name becomes the Campaign Name. Dynamic segments (query-based) are documented as filter criteria for Salesforce Reports and List Views rather than exported as static record sets; rebuilding them as Salesforce Report Filters or Lightning List Views is an admin task post-migration.

Smarketing Cloud supports custom object creation with user-defined schemas. We export the custom object schema (field names, types, relationships) and all record data. Salesforce custom objects (with __c suffix per Salesforce convention) must be pre-created in the destination org before data import. We create the destination schema first, including all custom fields, lookup relationships to standard objects (Contact, Account, Opportunity), and any validation rules, before any custom object data is loaded. Sequencing matters: if a custom object has a lookup to Account, Account must be imported first.

Smarketing Cloud User records export with name, email, role, and team assignment. We match by email against the Salesforce destination org's User table. Any Smarketing Cloud user without a matching Salesforce User goes to a reconciliation queue; the customer's Salesforce admin provisions missing users before record migration resumes. Role and team assignments from Smarketing Cloud map to Salesforce Permission Sets and Public Groups, which we document in the handoff inventory.

File attachments linked to Contacts, Companies, or Activities are exported with metadata and file URL. We download files to a staging bucket and re-upload to Salesforce as ContentVersion records, then create ContentDocumentLink records linking them to the parent Contact, Account, or Opportunity. Original file names and content types are preserved. Files exceeding Salesforce's 25 MB per ContentVersion limit are noted and escalated to the customer for alternative handling.

Smarketing Cloud email templates store HTML content and variable placeholders. We export template structure and content as part of the discovery inventory. Variable naming conventions differ between platforms, and template rebuild in Salesforce (as Visualforce Email Templates or Lightning Email Templates) requires a separate scope. We do not migrate email templates as functional code; we deliver a written template inventory with field-to-variable mapping for your admin or a Salesforce partner to rebuild.

Smarketing Cloud Automation Workflows are configurable per account with branching logic and trigger conditions. We export workflow names, trigger events, condition branches, and downstream actions as a written inventory document. Workflow definitions do not migrate as executable code because Smarketing Cloud's workflow model differs structurally from Salesforce Flow. The inventory document maps each Smarketing Cloud workflow to a recommended Salesforce Flow equivalent (record-triggered, scheduled, or screen flow) for your admin or a Salesforce partner to rebuild post-migration.