Migrate from Swift Digital Suite to Zoho CRM

Swift Digital Contacts are the central record type with lifecycle stage, engagement score, and segment membership. We split contacts into Zoho Leads (for early-stage prospects) and Contacts attached to Accounts (for engaged or converted records) based on the customer's Swift Digital lifecycle stage values agreed during scoping. We preserve the original Swift Digital lifecycle stage in a custom field sds_original_lifecycle__c on both the Lead and Contact for audit and reporting continuity.

Swift Digital segments are named groups based on behavioural or demographic criteria. We map each segment as a Zoho Tag applied to the Contact or Lead record. Tags are created at migration time and matched by name to avoid duplication. The customer reviews segment priority during scoping to confirm which segments should be tags versus Zoho CRM List membership.

Swift Digital Campaigns are parent containers for email sends, survey triggers, and event invitations. We map campaign name, type, created date, and status to Zoho Campaign records. Campaign membership migrates as Zoho Campaign Member records linked to the relevant Leads or Contacts. We create Campaigns first so that the Campaign Member dependency is satisfied at import time.

Swift Digital email engagement records (send timestamp, open, click, bounce, unsubscribe) migrate to Zoho as individual Task records with the campaign name and event type stored in the Task title and description fields. Zoho does not have a native email engagement detail object, so we use Task records with custom fields for open_date, click_url, and bounce_reason to preserve the full engagement timeline as an activity log against the Contact or Lead.

Swift Digital survey questions, answer types, and response data migrate as Zoho Notes linked to the Contact record. Survey conditional branching and skip logic are not exportable from Swift Digital and are documented separately as a flat question-response table. Before import we confirm with the customer whether Zoho Forms needs equivalent branching to be rebuilt manually, or whether the flat response table is sufficient for reporting purposes in Zoho Reports.

Swift Digital event registrations migrate as structured records in Zoho Notes linked to the Contact. Each record contains ticket type, registration date, attendance status, and RSVP history. Event-level custom fields (venue, capacity, session selection) migrate as custom Note fields. If the customer uses Zoho Events, we create native Event records with invitee status as Event Invitee records instead.

Swift Digital SMS sends (outbound message content, inbound replies, consent status) migrate as Zoho Notes attached to the Contact. The SMS opt-out flag from Swift Digital maps to Zoho's SMS consent field on the Contact record. Dual opt-out states (email opted-out but SMS still subscribed, or vice versa) are preserved as separate consent fields so that re-engagement preferences remain granular across channels.

Swift Digital Workflow definitions describe trigger conditions, time delays, and action steps but are not exportable as executable code. We document each workflow as a structured record showing the trigger source, each condition branch, the action type, and recommended Zoho Blueprint equivalent. The customer's admin or a Zoho implementation partner rebuilds the workflows post-migration.

Swift Digital custom properties on Contacts and Campaigns map to Zoho CRM custom fields of equivalent name and type where possible. We handle data type mismatches (date format normalisation, multi-select text to picklist, numeric strings to number fields) during the transformation phase. Custom field API names in Zoho use the format field_name in lowercase with underscores.

Swift Digital engagement scores are proprietary numeric values computed from open, click, and conversion events. We export the current score value as a static numeric custom field sds_engagement_score__c on the Zoho Contact. Zoho's own scoring model will recalculate independently using its algorithm. We document the exported score as a historical reference value so that the customer's admin can recalibrate Zoho scoring thresholds against the exported baseline.