Migrate from Swift Digital Suite to HubSpot

Swift contacts map 1:1 to HubSpot contacts. All standard properties (name, email, phone, job title) transfer directly. Swift's custom contact properties become HubSpot custom contact properties. The primary company association resolves via HubSpot's company lookup — contacts without a Swift company link land as standalone contacts and can be associated manually or via a secondary pass.

Swift company records map to HubSpot companies. Company name, domain, industry, employee count, and annual revenue transfer as HubSpot company properties. Swift's parent-company hierarchy (if used) maps to HubSpot's parent company field. Swift company custom properties become HubSpot company custom properties.

Swift campaign membership does not map to a single HubSpot object — HubSpot uses Lists for campaign grouping and stores email open/click timestamps as properties on the contact record. Each Swift campaign becomes a HubSpot Static List with members added by email. Last email open date, last click date, and total email opens transfer as custom contact properties (e.g., swift_last_email_open__c).

Swift event registrations translate to HubSpot contacts (resolving by email — a new contact is created if no match exists) plus a HubSpot Meeting record. The Swift ticket type, registration date, and check-in status map to custom contact properties (swift_ticket_type__c, swift_registered_date__c, swift_checkin_status__c). Swift event master data (title, date, location) becomes the Meeting record fields.

HubSpot has no native survey response object. Each Swift survey response linked to a contact becomes a custom property on that HubSpot contact, keyed by the survey question label (e.g., swift_survey_q1__c containing the response text or value). Multi-question surveys generate multiple custom properties per contact. We flag any survey with more than 20 questions as a candidate for HubSpot's custom object approach if your team needs relational survey response storage.

Swift's numeric engagement score (derived from email opens, clicks, event attendance, and survey completions) has no native HubSpot equivalent. We create a custom number field (swift_engagement_score__c) on the HubSpot contact and populate it with the Swift score value. HubSpot's own HubSpot Score property is calculated by HubSpot's scoring model and runs separately after migration — Swift's historical score is preserved but not recalculated automatically.

Swift owner records resolve to HubSpot users by email address match. If a Swift owner has no matching HubSpot user, records are assigned to a designated fallback HubSpot owner and flagged in the migration audit log so your admin can redistribute manually after go-live.

Swift drip sequences and workflow rules (lead routing, email triggers, score-based list updates) have no HubSpot equivalent object. FlitStack exports the full workflow definitions in a structured JSON document that maps each Swift rule to the equivalent HubSpot workflow trigger, condition, and action for your admin to rebuild in HubSpot Automation.

Swift email templates (HTML, drag-and-drop layouts, and dynamic content blocks) cannot be transferred to HubSpot's template format. We export the template content as HTML files and provide a mapping guide showing how each Swift content block maps to HubSpot's email editor structure so your team can rebuild templates in HubSpot's design manager.

Swift SMS campaign history (last send date, campaign name, send status) maps to a custom property on the HubSpot contact. HubSpot has a separate SMS product (Operations Hub or Service Hub add-on) — Swift SMS send data is preserved for reference but does not create SMS logs in HubSpot automatically. Rebuilt SMS campaigns in HubSpot will generate fresh send records independently.

Swift file attachments linked to contacts, companies, or events are downloaded and re-uploaded to HubSpot Files. File associations to records are preserved by re-linking the uploaded file URL to the corresponding HubSpot record. HubSpot's 300MB file size limit applies — files exceeding this are flagged and can be stored externally with a link stored on the record instead.