Migrate from Swift Digital Suite to Microsoft Dynamics 365 Sales

Swift Digital Suite Contacts with lifecycle stage of subscriber or unconfirmed map to Salesforce Lead. Contacts with a confirmed lifecycle stage (customer, evangelist, or sales-qualified) map to Dynamics 365 Contact tied to an Account. We compute the split using the Swift lifecycle stage and hs_lead_status properties at migration time and preserve the original stage in a custom field swift_original_lifecycle__c on both Lead and Contact for audit and reporting continuity.

Swift Digital Suite Company records map to Microsoft Microsoft Dynamics 365 Sales Account. The company domain stored in Swift becomes the Account Website field and is used as a dedupe key during import. We create Account records before Contact import so that the AccountId lookup is satisfied at Contact insert time.

Swift Digital Suite Campaigns map to Dynamics 365 Campaign (a Marketing Sales feature available in Sales Enterprise or as a separate Dynamics 365 Marketing licence). Campaign metadata (name, type, status, created date) migrates directly. Active or paused campaign state is preserved in a custom Status field because Dynamics 365 Campaign uses a different status model.

Swift Digital Suite Segments group contacts by behavioural or demographic criteria. We map each segment as a named tag applied to the Contact or Lead record in Dynamics 365. Where the destination includes Dynamics 365 Marketing, segments map to native Segment objects; otherwise, segment membership is stored as a multi-select picklist or tag on the Contact record.

Individual email sends tied to a Swift campaign and contact migrate to Dynamics 365 EmailMessage records (the email content and send metadata) linked to an Activity Task record (the timeline entry). Send timestamp, open timestamp, click events, bounce status, and unsubscribe status transfer to custom EmailMessage and Task fields. Each EmailMessage is linked to the migrated Contact or Lead via WhoId and to the related Campaign via WhatId.

Swift Digital Suite SMS sends migrate as custom Activity records or Notes attached to the Contact or Lead. The SMS consent flag from Swift collapses into Dynamics 365's email opt-out field (HasOptedOutOfEmail) for the SMS channel, and a custom field swift_sms_consent__c preserves the original SMS-specific consent state. If Dynamics 365 Customer Service is available, SMS history can attach to the Contact timeline as custom activity records.

Swift Digital Suite survey definitions (question text, answer types, conditional logic) are exported as structured records. Survey questions and answer options migrate to a custom survey_questions entity in Dynamics 365 or to Dynamics 365 Customer Voice if the customer holds that licence. Conditional branching and skip logic are not exportable from Swift Digital Suite and must be rebuilt manually in Customer Voice or Power Apps.

Individual survey responses tied to a contact migrate as records in a custom survey_response entity with fields for question_id, response_value, and submitted_date. A lookup links each response to the corresponding Contact record. Where response volume is low, responses attach as Notes on the Contact. The customer confirms during scoping whether a flat response table is sufficient for reporting or whether a rebuild in Dynamics 365 Customer Voice is preferred.

Swift Digital Suite event registrations (name, ticket type, attendance status, RSVP history) migrate as Campaign Member records linked to the corresponding Dynamics 365 Campaign. Ticket type and attendance status map to Campaign Member Status and custom fields. Event-level custom fields (venue, date, capacity) are stored on the parent Campaign record. If the customer uses Dynamics 365 Event Management, event data maps to native Event entities instead.

Swift Digital Suite engagement scores are numeric values computed from open, click, and conversion activity. We export the current score as a static numeric custom field swift_engagement_score__c on Contact or Lead. Microsoft Dynamics 365 Sales recalculates its own AI-driven lead or opportunity scoring from live data after migration; the exported Swift score serves as a historical reference value for comparison during the transition period.

Swift Digital Suite custom properties on Contacts and Campaigns map to identically named custom fields on the corresponding Dynamics 365 entity. We create the custom fields in the destination schema before migration using the Power Platform admin centre or a deployment package, matching Swift field types to appropriate Dynamics 365 field types (text, number, picklist, date).

Swift Digital Suite automation workflows are documented as structured records showing trigger, conditions, delays, and actions. We deliver a written inventory of every active Workflow with a recommended Dynamics 365 or Power Automate equivalent. Because workflows are platform-specific code, they do not migrate as executable assets. The customer's admin rebuilds them in Microsoft Dynamics 365 Sales automation or Power Automate post-migration.