Migrate from Swift Digital Suite to Nutshell

Swift Digital Suite Contacts are the primary migration object and map directly to Nutshell People. We extract full contact profiles including name, email, phone, custom properties, engagement score, lifecycle stage, and segment membership. The engagement score from Swift Digital Suite (a proprietary numeric value) migrates as a static numeric custom field on the Nutshell Person record; Nutshell does not compute an equivalent behavioural score and the value is preserved for historical reference only. Lifecycle stage migrates to a custom picklist field. We use the contact email address as the dedupe key during Nutshell import.

If Swift Digital Suite contacts are associated with company records (via custom property or association data), we map these to Nutshell Companies. Company name, domain, address, and custom properties migrate directly. Where a Swift Digital Suite contact has no associated company record, the Nutshell Person is created without a Company link and the customer decides post-migration whether to build out Company records manually or via a secondary enrichment step.

Swift Digital Suite Campaigns (email, event, and survey parent containers) do not have a direct Nutshell equivalent. Nutshell does not have a native campaign object. We handle this by creating a Nutshell Tag for each distinct Swift Digital Suite Campaign name, applied to every Person and Company record that has campaign membership. Where campaign metadata (campaign type, created date, status) is needed for reporting, we add a custom text field campaign_context__c on the Person record. The customer confirms during scoping which campaigns should generate Tags versus custom field values.

Swift Digital Suite Segments are behavioural or demographic groups applied to contacts. We map each Segment to a Nutshell Tag on the Person record, using the segment name as the Tag label. Where the same contact belongs to multiple segments, all segment Tags are applied. Nutshell Tags are string labels and do not support segment membership dates or dynamic re-evaluation; Tags are static after import and do not update if the source segment definition changes.

Individual email send records (send timestamp, open, click, bounce, unsubscribe status per contact per campaign) are mapped to Nutshell Note records attached to the Person. Each Note captures the campaign name, send date, and engagement event type (Sent, Opened, Clicked, Bounced, Unsubscribed) in the Note body, with the timestamp preserved. Nutshell's activity timeline displays Notes in chronological order. This approach preserves the engagement log without requiring a native email send object, which Nutshell does not provide as a standard CRM record type.

Swift Digital Suite engagement scores are computed by the platform's proprietary algorithm and exported as a static numeric value. We import this as a Nutshell custom numeric field on the Person record named swift_engagement_score__c. Nutshell does not generate equivalent behavioural scores, and this value does not update after migration. We document the original Swift Digital Suite scoring scale in the migration notes so the customer can calibrate any future Nutshell-based scoring model against the historical reference.

Survey definitions (question text, answer types) are exported from Swift Digital Suite as structured records. Individual survey responses are tied to the contact record. Complex conditional branching or multi-page skip logic defined inside Swift Digital Suite is not exportable as logic; we extract responses as a flat table. We import each response set as a Nutshell Note on the Person record, or as a series of custom fields if the response set is short and fixed. The customer confirms during scoping whether a flat response note or individual custom fields are preferred for reporting purposes.

Event registrations, ticket type, attendance status, and RSVP history are extracted from Swift Digital Suite and mapped to Nutshell Notes on the relevant Person record. Event-level custom fields such as venue or session selection are added to the Note body or to custom fields on the Person if the customer requires structured event data for reporting. Nutshell does not have a native event registration object, so attendance history is preserved as activity log entries rather than as a standalone record type.

SMS send and receive records tied to Swift Digital Suite contacts are mapped to Nutshell Notes on the Person record. The Note captures the message direction (outbound or inbound), send or receive timestamp, and message content. SMS consent flags from Swift Digital Suite (which tracks email and SMS opt-out separately) are mapped to the Nutshell HasOptedOutOfEmail field; if a contact has opted out of SMS but not email, we set HasOptedOutOfEmail to false but add a custom flag swift_sms_optout__c to track the SMS restriction. This prevents accidental SMS re-engagement via a tool connected to Nutshell.

Swift Digital Suite custom properties on contacts (beyond standard name, email, phone) are mapped to Nutshell custom fields on the Person record. Nutshell supports Text (max 225 characters), Long Text, Currency, Date, Number, and Picklist custom field types. We map property types to equivalent Nutshell types during scoping and create the custom fields in Nutshell before import. Long text properties from Swift Digital Suite that exceed Nutshell's 225-character text limit are truncated with a note appended, or mapped to Long Text fields where the customer confirms the destination account supports this field type.

Swift Digital Suite automation workflows define trigger conditions, time delays, and action steps for campaign automation. Nutshell's CRM Workflows handle task creation and field updates within the sales CRM but do not replicate Swift Digital Suite's campaign-level marketing automation. We do not migrate workflows as code. We extract every active Swift Digital Suite workflow as a structured JSON and Markdown document showing the trigger, each step, its conditions, and the recommended Nutshell equivalent (or a note that no direct replacement exists in Nutshell CRM). The customer's admin uses this document to rebuild automation in Nutshell or a dedicated marketing tool.