Migrate from Smarketing Cloud to Twenty CRM

Smarketing Cloud Contacts map to Twenty People records. Standard fields (name, email, phone, lifecycle stage) migrate directly. Custom Contact properties in Smarketing Cloud's incremental custom property model require schema auditing during discovery — we map each to a Twenty custom field and flag any Smarketing Cloud properties without a clean Twenty equivalent for customer resolution before import. The email address is the dedupe key.

Smarketing Cloud Company profiles map to Twenty Company records. The Company-Contact linkage is preserved by exporting both objects and reconstructing the relationship via foreign key matching on the contact's company_id field. We resolve the Company reference at migration time so that People records are linked to the correct Company on insert.

Smarketing Cloud Pipelines and their stages map to Twenty Opportunity records grouped by workspace pipeline. Stage names and ordering vary per Smarketing Cloud account since teams configure them freely. We export the full stage sequence from Smarketing Cloud and remap to Twenty stage values agreed with the customer during scoping. The pipeline workspace association in Twenty is set at import time based on the Smarketing Cloud pipeline assignment.

Smarketing Cloud Campaign member lists map to People records with a workspace association or custom field indicating Campaign enrollment. Campaign enrollment history (which Contacts were enrolled in which Campaigns and when) is preserved as a custom field on the People record. We do not migrate Campaign send history records as functional data — they are documented in the inventory handoff. Dynamic Campaign segments are documented as filter criteria for recreation as Twenty filter queries.

Smarketing Cloud custom objects (with their schemas, field definitions, and all record data) map to Twenty custom objects. The destination schema — including all custom fields, lookup relationships, and field types — must be pre-created in Twenty's Settings Data Model before import. We coordinate sequencing so that custom object schemas are created first, then records are imported with their cross-object lookups resolved at migration time.

Smarketing Cloud User records (name, email, role, team assignment) map to Twenty Member records. Role assignment from Smarketing Cloud maps to Twenty's permission system — we document the role mapping during scoping and apply it at import time. Inactive Smarketing Cloud users can be exported but the migration scope for inactive records is agreed with the customer before extraction.

Tags on Smarketing Cloud Contacts and Companies export as tag strings per record. We reapply them in Twenty as bulk tag operations against the migrated People and Company records. The tagging structure (which records share which tags) is preserved. Twenty supports both tag-style and label-style categorization — the customer chooses the preferred approach during scoping.

Smarketing Cloud Activity logs linked to Contacts and Companies export with activity type, timestamp, owner email, and description text. Activity records migrate to Twenty Task or Note objects with the owner resolved via email-to-member lookup. Activity timestamps are preserved for historical timeline accuracy. The migration of activity history depends on what is accessible in the source account's plan tier.

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 Twenty workspace, preserving the original filename and linking the file to the parent record. Attachments without a downloadable URL in Smarketing Cloud are flagged for manual review.

Static Lists export as record sets and re-import as tagged People records. Dynamic Segments export as record sets for a point-in-time snapshot, and we document the active filter criteria for recreation as Twenty filter queries. Dynamic segments are not migrated as live automated queries since the underlying filter logic differs between platforms — the customer recreates them in Twenty after migration.