Migrate your Smarketing Cloud data

Core CRM record type. Exports include standard fields (name, email, phone, lifecycle stage). We handle custom Contact properties by mapping them to destination custom fields and flagging any Smarketing Cloud-specific naming conventions.

Company profiles are linked to Contacts via a relationship table. We preserve the Company-Contact linkage during migration by exporting both objects and reconstructing relationships via foreign key matching.

Pipelines and Pipeline Stages are supported. Stage names and ordering vary by account since teams configure them freely. We export the full stage sequence and remap to destination stage names agreed with the customer during scoping.

Marketing Campaigns store member lists and send history. We export Campaign membership records and preserve which Contacts were enrolled in which Campaigns and when.

Workflow definitions are configurable per account. Complex branching logic requires manual documentation review before migration. We export workflow names and trigger conditions but recommend rebuilding complex automations in the destination system.

Email templates are stored with HTML content and variable placeholders. Template structure exports cleanly but variable naming conventions differ between platforms — we remap placeholder syntax during import.

Activity logs (calls, emails, notes) are linked to Contacts and Companies. We export activity type, timestamp, owner, and description text. Owner assignment is preserved via user email mapping to avoid orphaned records.

Smarketing Cloud supports custom object creation. We export custom object schemas, field definitions, and all record data. Destination schema must be created first — we coordinate the sequencing so custom object data loads after the schema is in place.

User records export with name, email, role, and team assignment. We map Smarketing Cloud roles to equivalent destination permission sets. Inactive users can be exported but migration scope is agreed per customer to avoid importing deprecated accounts.

Contacts and Companies can carry multiple Tags. We export tag strings per record and reapply them as destination tags or labels, using a bulk apply operation to preserve the tagging structure.

Static lists and dynamic segments are exported as record sets. For dynamic segments we document the filter criteria and recommend recreating them as queries in the destination platform rather than exporting a static snapshot.

File attachments linked to Contacts, Companies, or Activities are exported with their metadata and file URL. We download files to a staging bucket and re-upload to the destination, preserving the original file name and upload date.