Migrate from Swift Digital Suite to Pipedrive

Swift Digital Suite Contacts map directly to Pipedrive People. We export all standard contact fields (first name, last name, email, phone, address), custom properties, engagement score, lifecycle stage, and segment membership. Email addresses serve as the dedupe key during Pipedrive import. Owner resolution maps Swift Digital owner email to Pipedrive user email; any unmatched owner goes to a reconciliation queue for admin provisioning before Person import begins.

Swift Digital Segments define behavioural or demographic groups (for example, 'Event Attendees Q3 2025' or 'SMS Opted-In'). We map each segment to a Pipedrive Label on the Person record. Where the customer uses segments as structured data fields (for example, a segment storing a numeric lead tier value), we map to a Pipedrive custom field of the equivalent type. The customer chooses between label-based and field-based segment strategy during scoping.

Swift Digital Campaigns are parent containers for email sends, event registrations, and survey responses. Pipedrive has no native campaign object. We flatten each campaign participation record into a Pipedrive Activity entry (type=note) on the relevant Person or Organisation, tagged with the campaign name and participation type (opened, clicked, registered, responded). Campaign metadata (name, type, created date) is preserved in the activity note text. This approach keeps the engagement history visible in the Pipedrive activity timeline without requiring a custom object.

Individual email send records from Swift Digital (send timestamp, open timestamp, click events, bounce or unsubscribe status) map to Pipedrive Activities attached to the Person record. Open and click events with timestamps are written as separate note-type activities for timeline fidelity. Bounce and unsubscribe events are mapped to Pipedrive's native email_status field and the person's opt_out flag. Email content body is not migrated to avoid duplicate storage since Pipedrive does not natively host email content; the Swift Digital export retains the full email record for audit.

Swift Digital event registrations (event name, registration date, ticket type, attendance status, RSVP history) map to Pipedrive Activities on the Person record. Event-level metadata is stored in the activity note with structured fields (event_name, registration_date, ticket_type, attendance_status). Complex event custom fields (venue, capacity, cost) are mapped to custom fields on the Person record. Event custom fields requiring hierarchical event-level aggregation (for example, total registrations per event) do not map to Pipedrive natively and are documented in the migration deliverable.

Survey questions and answer options export from Swift Digital as structured records. Individual survey responses per contact flatten into a single Pipedrive Activity note containing the survey name, response timestamp, and all question-answer pairs in a structured text format. Conditional branching logic and skip rules are not exported from Swift Digital; we document the branching structure separately so the customer's admin can rebuild equivalent logic in a survey tool or Pipedrive custom form if required. Complex multi-page surveys with branching may result in multiple activity entries per contact, one per page submitted.

SMS sends from Swift Digital map to Pipedrive Activities of type=call or type=note depending on whether the customer uses Pipedrive's built-in SMS feature or a connected SMS integration. Outbound message content, inbound reply content, and send timestamp migrate into the activity note. The contact's SMS consent flag migrates to Pipedrive's opt_out field (see opt-out reconciliation in gotchas). SMS campaign attribution (which SMS campaign triggered the send) is stored as a label on the activity.

Swift Digital lifecycle stage values (subscriber, lead, customer, etc.) export as a static string property per contact. We create a Pipedrive custom field of type=enum with the same stage values and populate it from the exported Swift Digital value. Pipedrive does not use lifecycle stage for CRM workflow triggers natively; the migrated field serves as a reference and segmentation tool rather than a functional pipeline stage equivalent.

Swift Digital's proprietary engagement score is a numeric value computed by the platform's algorithm on open, click, and conversion events. We export the current score as a static numeric value and map it to a Pipedrive custom field (type=numeric or type=currency depending on score magnitude). Pipedrive does not recalculate engagement scores natively. The migrated score is a historical reference value; the customer's admin can configure Pipedrive automation to update the field based on Pipedrive activity triggers if they wish to maintain a live score.

All active Swift Digital custom properties on Contact, Campaign, Event, and Survey records are exported and mapped to identically named custom fields in Pipedrive. Field type mapping follows the closest Pipedrive equivalent: string properties map to text fields, date properties to date fields, numeric properties to numeric fields, and multi-value properties to multi-select picklist or label. Where a Swift Digital property uses a data type Pipedrive does not support (for example, a JSON blob), we store the value as a text field and document the limitation in the migration scope.

Swift Digital workflows define trigger conditions, time delays, and action steps for automated contact journeys. Pipedrive does not have an equivalent workflow automation model at the contact-journey level (Pipedrive automation is scoped to deal and activity triggers within the CRM). We do not migrate workflows as code. We deliver a structured written inventory of every active Swift Digital workflow with its trigger, conditions, steps, and recommended Pipedrive equivalent (Workflow, Automation Rule, or smart Campaign) for the customer's admin to rebuild post-migration.