Migrate from Swift Digital Suite to Salesforce Sales Cloud

Swift Digital Suite Contacts map directly to Salesforce Contacts with Email, FirstName, LastName, Phone, and custom property fields preserved. We use the contact email address as the dedupe key during import. Custom properties from Swift Digital Suite migrate to custom Contact fields (custom__c naming per Salesforce convention). Engagement score exports as a static numeric custom field sw_engagement_score__c for historical reference only — Salesforce's own scoring model recalculates independently after migration. Segment membership from Swift Digital maps to Campaign Membership in Salesforce.

Swift Digital Suite Segments group contacts by behavioural or demographic criteria and are used to target campaigns. We map each named segment to a Salesforce Campaign with Campaign Type set to Segmentation and a descriptive custom field sw_segment_source__c storing the original Swift Digital segment name. Segment membership becomes Campaign Member records attached to the Campaign, preserving the contact's membership date and source.

Swift Digital Suite Campaigns are parent containers for email sends, event registrations, and survey triggers. Campaign metadata (name, type, created date, status, owner) maps to Salesforce Campaign. Active or paused campaign state from Swift Digital maps to Campaign Status (Active, Planned, Completed, Aborted). Campaign type mapping (email, event, survey) becomes Salesforce Campaign Type values.

Individual email sends from Swift Digital Suite are tied to a contact and a campaign. We export send timestamp, open timestamp, click events, bounce status, and unsubscribe status per contact-campaign pair. These migrate to Salesforce as EmailMessage records (the email body and metadata) linked to a Task record for the activity timeline entry. WhoId on Task points to the Contact; WhatId points to the related Campaign. Open and click events become custom Task fields rather than separate records.

Swift Digital Suite Survey definitions and responses do not have a native Salesforce equivalent at standard tier. Survey questions and answer types migrate as a custom object schema: Survey_Response__c (header: survey name, contact reference, response date) and Survey_Response_Answer__c (detail: question text, answer value, answer type). Survey conditional branching and skip logic are not exportable from Swift Digital Suite and are not recreated by our migration; we deliver a written survey logic map for the customer's admin to rebuild in Salesforce Survey, a third-party survey tool, or a Flows-based branching form.

Swift Digital Suite Event registrations include registration record, ticket type, attendance status, and RSVP history. We export the full event roster as Salesforce Campaign Member records (one per contact per event) with custom fields for ticket_type__c, attendance_status__c, and rsvp_date__c. Event-level details (venue, date, capacity) map to a Salesforce Event record linked to the Campaign. Multi-session or multi-day events map to multiple Event records with shared Campaign reference.

SMS sends from Swift Digital Suite are tied to contacts and campaigns similarly to email sends. Outbound and inbound message content migrates as a Task with TaskSubtype = SMS, with message content stored in Task.Description and direction (inbound/outbound) stored in a custom field sms_direction__c. The contact's SMS consent flag from Swift Digital Suite migrates to the Salesforce SMS Opt Out object and to a custom field sms_consent__c for reference.

Contacts in Swift Digital Suite support custom properties as key-value pairs. We extract all active custom property names and data types (text, number, date, boolean, picklist) and map them to identically named custom fields on the Salesforce Contact object using the __c suffix. Where Swift Digital stores a date as a numeric epoch timestamp, we transform to Salesforce datetime format. Picklist values from Swift Digital map to Salesforce picklist or multi-select picklist depending on whether the source property allowed single or multiple values.

Swift Digital Suite engagement scores are computed using a proprietary algorithm based on open, click, and conversion events. We export the current numeric score as a custom field sw_engagement_score__c on the Contact record. This field is a historical snapshot only — Salesforce has no native engagement scoring engine that inherits Swift Digital's algorithm. We document the exported score alongside the scoring criteria (open weight, click weight, conversion weight) so the customer's admin can configure an equivalent scoring model in Salesforce Flow, Pardot, or a third-party scoring app.

Automation Workflows in Swift Digital Suite define trigger conditions, time delays, and action steps across email, SMS, and event channels. We document each active workflow as a structured record listing the trigger, each step, its conditions, and its actions. We do not migrate Workflows as code because Salesforce Flow uses a different trigger and action model with distinct governor limits, expression syntax, and element types. The workflow inventory is delivered as a written document with recommended Salesforce Flow equivalents for the customer's admin to rebuild.

Swift Digital Suite tracks email unsubscribe status independently from SMS opt-out. We collapse both flags into a single Salesforce HasOptedOutOfEmail field using the more restrictive opt-out state: if a contact has opted out of SMS but not email, we set HasOptedOutOfEmail to true in the destination to prevent accidental SMS-to-email re-engagement. The original email-specific and SMS-specific flags are preserved in custom fields sw_email_unsubscribed__c and sw_sms_unsubscribed__c for audit.

Swift Digital Suite tracks campaign membership status (invited, registered, attended, bounced, unsubscribed) per contact per campaign. These map to Salesforce CampaignMember Status values. We configure a Campaign Member Status picklist on the Salesforce Campaign that mirrors the Swift Digital membership states, ensuring reporting consistency between the source data and the migrated Campaign Member records.