Migrate from Symplify Communication to Twenty CRM

Symplify Contacts migrate to Twenty People records using the Symplify originalId as a custom field (symplify_original_id__c) for cross-system reference. Email, phone, name, and address fields map directly. We preserve the contact's originalId as a custom field on the People record so that related DataDocs can be linked via lookup after the People migration is complete.

Symplify does not have a native Company object, but DataDocs with relational purchase history or booking data often imply organizational context. If contacts include company affiliation fields, we create Twenty Company records and link them to the corresponding People record via the WorkGroup module if enabled. If no company context exists in the source data, we skip Company creation to avoid orphan records.

DataDocs require pre-auditing of Document Types before migration. Each unique Document Type in Symplify becomes a separate Twenty Custom Object. We create the custom object schema (fields, field types, and lookups) in Twenty Settings Data Model before any DataDoc records are imported. DataDocs without a valid Document Type definition are held in an orphaned queue for customer review. The relational link to the parent Contact migrates by resolving the originalId to the corresponding Twenty People record.

Symplify Lists are static contact groupings. We create a custom multi-select picklist field (symplify_lists__c) on Twenty People and populate it with the list names to which each contact belonged. If the customer uses lists for segmentation in reporting, we recommend creating a dedicated Custom Object for list membership with a Many-to-One relationship to People.

Symplify Campaigns map to Twenty Opportunities to re-frame marketing sendout data as sales pipeline records. The campaign name becomes the Opportunity name, and the campaign send date becomes the Opportunity created date. Campaign-level aggregate stats (total sends, opens, clicks, bounces) migrate as custom fields on the Opportunity record. This is a re-modeling step: Symplify campaigns are marketing events, while Twenty Opportunities represent sales pipeline stages.

Individual messages within a Symplify Campaign migrate as Task records linked to the corresponding Opportunity. The message subject becomes the Task name, and message send status (sent, bounced, opened) becomes a custom status field on the Task. If the message contains meaningful body content, we attach it as a Note on the Task.

Open events per contact per message migrate as Task records on the corresponding People record with a custom field open_timestamp__c preserving the original open time. We deduplicate multiple opens by the same contact on the same message, retaining the first open timestamp as the primary event and the count of total opens as a secondary field.

Click events per contact per message URL migrate as Task records on the People record with custom fields click_url__c and click_timestamp__c. The URL is preserved to allow the customer to map click behavior to any downstream analysis or reporting in Twenty.

Hard bounce records mark permanently undeliverable contacts. We set a custom boolean field email_hard_bounce__c on the People record to True for contacts with hard bounce events. This prevents re-sending from Twenty and protects deliverability reputation in any connected email tool.

Soft bounce records indicate temporary delivery failures. We set a custom field email_soft_bounce__c with the soft bounce count and timestamp. Soft bounce normalization may be needed because Symplify and Twenty use different bounce code conventions. We store the raw Symplify bounce code in a text field for the customer's admin to interpret post-migration.

Optout records track unsubscribe preferences. We set the Twenty People emailOptedOut field to True for all contacts with optout events, preserving the optout timestamp in a custom field unsubscribe_date__c for compliance and audit purposes.

Symplify Projects are organizational containers for campaigns and workflows. If the customer uses Projects to group campaigns by business unit or initiative, we create a Custom Object (Project__c) in Twenty and link each migrated Opportunity (from Campaign) to its parent Project via a lookup field. If Projects contain no meaningful data beyond organizational labels, we skip this object and document the decision.