Migrate your Swift Digital Suite data

Contacts are the central record type. We export full contact profiles including email address, custom properties, engagement score, segment membership, and lifecycle stage. Date fields are normalised to ISO 8601 during export. The platform stores contact-level preferences and subscription status per communication channel.

Segments group contacts by behavioural or demographic criteria. We map each segment as a named tag applied to the contact record in the destination. Where the destination supports native segment objects, we create the equivalent structure and assign contacts to it.

Campaigns are the parent container for email sends, survey triggers, and event invitations. We export campaign metadata including name, type, created date, and status. Active or paused campaign state is preserved as a label on the record in the destination.

Individual email sends are tied to a campaign and a contact. We export the send timestamp, open timestamp, click events, and bounce or unsubscribe status for each contact-campaign pair. Where a contact received multiple sends, we preserve the full engagement timeline.

Survey definitions (question text, answer types, conditional logic) are exported as structured records. Individual survey responses are tied to the contact record. Complex conditional branching or multi-page survey logic is flattened into a flat response schema — we flag any question that relies on skip logic and map answers to the most appropriate destination field.

Events include registration records, ticket type, attendance status, and RSVP history. We export the full event roster as a contact-level log of event participation. Event-level custom fields (venue, capacity, session tracks) are mapped as properties on the event record in the destination.

SMS sends are tied to contacts and campaigns similarly to email sends. Outbound and inbound message content is exported. The contact's SMS consent flag is preserved. Opt-out status for SMS is handled separately from email unsubscribe status in the destination to avoid accidental re-permissioning.

Workflow definitions describe trigger conditions, time delays, and action steps. We document the workflow as a structured record showing the trigger, each step, and its conditions. Because workflows are active objects, we flag whether they should be recreated in the destination platform or retired. Imported contacts inherit any pre-built workflow assignments if the destination supports equivalent automation logic.

Contacts and campaigns support custom properties. We extract all active custom property names and values, mapping them to identically named fields in the destination where possible. Where the destination uses a different field name convention, we apply a customer-confirmed mapping table before import.

Engagement scores are numeric values computed by Swift Digital Suite based on open, click, and conversion activity. We export the current score value as a numeric contact property. Because scoring algorithms differ between platforms, we flag that scores are point-in-time snapshots and do not guarantee equivalent behavioural thresholds in the destination.