Migrate from Swift Digital Suite to Freshsales

Swift Digital Suite Contact records map directly to Freshsales Contact. The contact's email address becomes the dedupe key. All standard fields (name, phone, company) migrate as-is. Swift custom properties map to Freshsales custom contact fields that we pre-create before import. We flag contacts with Lifecycle Stage values in Swift and preserve these as a custom field swift_original_lifecycle__c in Freshsales for audit and segmentation reference.

Swift Digital Suite Contacts with a lifecycle stage value indicating an early-stage prospect (subscriber, inquiry) map to Freshsales Lead rather than Contact if the customer chooses to preserve a lead-to-contact distinction. The split decision is confirmed during scoping. Email, phone, and custom property values migrate identically. Source_campaign__c stores the Swift campaign name for Lead-to-Contact reporting.

Swift Digital Suite segment membership (each contact can belong to multiple segments) maps to Freshsales Contact tags. Because Freshsales tags are single-value per contact, multi-segment membership converts to a semicolon-delimited custom field swift_segments__c. We confirm with the customer whether to use tags (visual segmentation) or the custom field (full membership preservation) during scoping.

Swift Digital Suite Campaigns are marketing containers with no direct Freshsales CRM equivalent. We map each Swift campaign name to a Freshsales Deal record with the campaign name in Deal Name, a custom field swift_campaign_id__c carrying the Swift campaign identifier, and Campaign Source status set from the Swift campaign type. If the customer prefers to preserve campaigns as tags rather than Deals, we apply campaign names as tags to the linked Contact records instead.

Individual email send records from Swift Digital Suite (send timestamp, open timestamp, click events, bounce status, unsubscribe status) migrate as Freshsales Activity records. Each send becomes a Task with Subject = 'Email: [campaign name]', ActivityDate = send timestamp, and custom fields for open_flag, click_flag, bounce_flag, and unsubscribe_flag. The full email body migrates as a Note attached to the Task for reference. Open and click events become separate child Tasks under the parent send record to preserve the full engagement timeline.

Swift Digital Suite survey definitions and response data map to a Freshsales custom object named Survey_Response__c with lookup fields to Contact. Each question-answer pair becomes a custom field on the custom object. Conditional branching and skip logic defined in Swift are not exportable as code; we document the original survey structure in a written survey map for the customer's admin to rebuild in Freshforms or a comparable form tool post-migration.

Event registrations from Swift Digital Suite (registrant name, ticket type, attendance status, RSVP history) map to a Freshsales custom object named Event_Registration__c with a lookup to the Contact record. Event metadata (venue, date, event type) migrates as custom fields on the registration record. Event-level custom fields (capacity, waitlist count) are preserved as fields on the Event_Registration__c object.

SMS send records from Swift Digital Suite (outbound and inbound message content, send timestamp, consent status) migrate as Freshsales custom object records named SMS_Record__c with a lookup to Contact. The SMS consent flag maps to Freshsales contact-level unsubscribe handling. If the destination Freshsales instance has Freshcaller or Freshchat enabled, we discuss whether to route SMS records into the native conversation object during scoping.

Swift Digital Suite engagement scores are platform-computed numeric values that cannot be replicated in Freshsales without identical behavioural tracking. We export the current score as a static numeric custom field swift_engagement_score__c on the Contact record. Freshsales' Freddy AI will compute its own behavioural score independently after migration; the Swift score is preserved for historical reference and can be used as a baseline for custom reporting.

All active Swift Digital Suite custom properties on Contact and Campaign records are mapped to Freshsales custom fields of equivalent type (text, number, date, picklist). We pre-create every custom field in Freshsales before the first import, matching the data type precisely. If a Swift custom property contains a multi-value list (e.g., multiple checkboxes), it maps to Freshsales as a multi-select picklist.