Migrate from Swift Digital Suite to HighLevel

Swift Digital Suite Contact records map directly to GoHighLevel Contact. Standard fields (first name, last name, email, phone, address) map to GoHighLevel's equivalent Contact fields. We preserve the contact's created date and last-modified date as static date properties in GoHighLevel's custom field set. Any Swift Digital Suite custom properties are mapped to GoHighLevel custom fields of matching type (text, number, date, or picklist) that we pre-create in the GoHighLevel account before import.

Swift Digital Suite segments are behavioural or demographic contact groupings stored as segment membership on the contact record. We export each segment as a named tag applied to the GoHighLevel Contact via the tag import field. Where GoHighLevel supports native List objects for broader grouping, we create a corresponding GoHighLevel List and populate it with the matching contacts. Segment membership with a start or end date is stored as a custom date range field on the Contact in GoHighLevel.

Swift Digital Suite campaigns are the parent container for email sends, event invitations, and survey triggers. We map campaign metadata (name, type, status, created date) to a GoHighLevel Campaign record. Active or paused campaign state is noted as a custom status field. GoHighLevel does not have an equivalent campaign-member tracking model for individual email sends; we create Campaign membership records linking each Contact to the Campaign for attribution purposes. If the campaign tracks a sales motion rather than a marketing sequence, we map it to a GoHighLevel Pipeline with stage notes.

Individual email sends from Swift Digital Suite include send timestamp, open timestamp, click events, bounce, and unsubscribe status for each contact-campaign pair. We create a contact-level activity log entry in GoHighLevel (using a custom activity type or note attached to the Contact) recording the campaign name, send date, open date, click URL, and bounce or unsubscribe flag. GoHighLevel's native contact timeline supports notes and tasks; we use a note with a structured template for the email history entry so it appears in the contact's activity feed. Email engagement scores from Swift Digital Suite migrate as a static numeric custom field rather than as live behavioural data.

Swift Digital Suite survey questions and answer options export as structured records; individual survey responses are tied to the contact record. GoHighLevel's Forms object captures form submissions but does not natively replicate conditional skip logic or question branching from Swift Digital Suite. We export all questions, answer options, and response data as a flat table mapped to GoHighLevel custom fields on the Contact record. Before import, we confirm with the customer whether GoHighLevel's form builder needs equivalent branching rebuilt manually or whether the flat response table (question-label as field name, response as value) is sufficient for reporting purposes.

Swift Digital Suite events include registration records, ticket type, attendance status, and RSVP history. We export the full event roster as contact-level log entries recording event name, registration date, ticket type, attendance status, and any event custom fields. In GoHighLevel, these map to Appointment records attached to the Contact, with the event custom fields stored as custom appointment fields. Event-level properties (venue, date, capacity) are stored as a custom field set on a GoHighLevel Campaign that acts as the event parent record.

SMS sends are tied to contacts and campaigns in Swift Digital Suite. We export outbound and inbound message content, timestamp, direction (inbound/outbound), and the SMS consent flag. GoHighLevel tracks SMS at the contact level with a Conversations feature. We import each SMS record as a note on the Contact using a structured template (direction, timestamp, content snippet). The contact's SMS consent flag from Swift Digital Suite maps to the SMSConsent field in GoHighLevel. Where Swift Digital Suite tracks separate email opt-out and SMS opt-out flags, we apply the most restrictive opt-out state to both the HasOptedOutOfEmail field and the SMS consent field to prevent accidental re-engagement.

Swift Digital Suite contacts and campaigns support custom properties. We extract all active custom property names, data types, and values, then pre-create identically named custom fields in GoHighLevel before import. Where Swift Digital Suite uses a picklist-style custom property, we create a GoHighLevel picklist field with the same options. Free-text custom properties map to GoHighLevel text fields. Numeric and date custom properties map to GoHighLevel number and date fields respectively. We flag any Swift Digital Suite custom properties with a data type that GoHighLevel does not support natively (such as complex JSON or list-of-objects) and discuss a flattened representation with the customer during scoping.

Swift Digital Suite engagement scores are computed from open, click, and conversion events using a proprietary algorithm. We export the current score value as a static numeric contact property. In GoHighLevel, we create a custom numeric field (engagement_score__c) and populate it with the exported value. We document the score as a historical reference value rather than a live behavioural metric, since GoHighLevel's own contact scoring model will recalculate independently. If the customer requires a live engagement score in GoHighLevel, we recommend configuring GoHighLevel's built-in contact scoring feature after migration as a separate post-migration setup step.