Migrate from Swift Digital Suite to monday CRM

Swift Digital Suite Contacts map to Monday.com People board items. Each Person item carries the contact's email, name, phone, custom properties, segment tags, lifecycle stage, and engagement score as typed columns. Swift's engagement score migrates as a Number column (original_score__c) to preserve the historical value; Monday does not recalculate it. Email opt-out and SMS opt-out flags collapse into Monday's single Person unsubscribe column — if either flag is true in Swift, the Person is marked as unsubscribed in Monday.

Swift Segments group Contacts by behavioural or demographic criteria. Each segment name migrates as a Tag applied to the corresponding Person item in Monday. If the customer uses segments as primary audience filters for campaigns, we also configure a Segment column (List type) on the People board so that group membership is visible as a column value rather than a tag alone. The customer chooses tag versus column during scoping based on how they plan to use segments in Monday.

Swift Campaigns (email sends, event invitations, survey triggers) map to Monday CRM boards. Each Swift Campaign becomes a named Group within a CRM board, with campaign metadata (name, type, created date, status) stored in board-level columns or a dedicated Info item. Active or paused campaign state is preserved in a Status column. Campaign-to-contact assignments are reconstructed by linking the Person items from the contact export to the relevant Campaign group via a Connect Boards column or a Tag.

Individual email sends from Swift (send timestamp, open timestamp, click events, bounce status) map to Monday's Emails & Activities feature on each Person item. Each send appears as an activity entry in the Person's timeline with the send date, engagement event (opened, clicked), and campaign name. We normalise the Swift engagement event schema into Monday's activity types: sent, delivered, opened, clicked, bounced, unsubscribed. Bounce and unsubscribe events update the Person's status fields in Monday.

Swift survey definitions (question text, answer types, response data) migrate as structured records. We export all questions and answer options, then map survey responses as separate items or as column entries on the related Person item in Monday. Conditional branching and skip logic defined inside Swift are not exposed in the export — we extract a flat response table and confirm with the customer whether the destination survey tool (Monday Forms or a connected tool) needs equivalent branching to be rebuilt manually, or whether a flat response log is sufficient for reporting.

Swift events (registration records, ticket type, attendance status, RSVP history) map to Monday board items within a dedicated Events board. Each registration becomes an item with Status column values (registered, attended, no-show, cancelled), ticket type as a List column, and RSVP date as a Date column. Event metadata (venue, capacity, event date) migrates as a separate Info item or board columns depending on the customer's event management volume.

SMS sends from Swift map to Monday's SMS activity on the Person timeline, or as a Text column (sms_history__c) containing the message content and direction (outbound/inbound). The contact's SMS consent flag merges with the unified unsubscribe field on the Person. Opt-out status for SMS from Swift (tracked separately from email opt-out) is applied to the Person unsubscribe column so that any SMS consent revocation prevents re-engagement on that channel.

Swift Contacts and Campaigns support custom properties with value types including text, number, date, checkbox, and dropdown. We extract all active custom property names and values, then configure identically named custom columns in Monday with matching types: text fields map to Text columns, numeric scores map to Number columns, dates map to Date columns, and multi-value selections map to List columns. Where a property name conflicts with a Monday reserved column name, we prefix with an underscore.