Migrate from SwiftCRM to Pipedrive

SwiftCRM Contact records map to Pipedrive People. The client's name, relationship type, Face ID-protected notes, and custom relationship fields transfer to Pipedrive's Person object as standard and custom fields. We use the contact's primary email as the deduplication key. If a SwiftCRM Contact has an associated organization in a future custom field, we create a corresponding Pipedrive Organization first and link it via the Person-Organization relationship.

SwiftCRM Appointments with a scheduled start and end time map to Pipedrive Activity records with type = completed_calendar_slot or an Event with Start and End timestamps. Standalone reminders without a duration map to Task records with a due date. Each Activity is linked to the migrated Person via the Person-Activity relationship to preserve the client-appointment context from the original SwiftCRM record.

SwiftCRM E-Docs associated with a Contact export as file attachments. We map them to Pipedrive Files attached to the corresponding Person record. File names, content, and any folder organization are preserved. If the E-Doc organization in SwiftCRM uses a folder hierarchy, we recreate it as Pipedrive's activity notes or as tagged file metadata depending on the customer's preference during scoping.

SwiftCRM Reminders tied to specific Contacts or Appointments map to Pipedrive Task records with a due date, subject, and linked Person. The reminder's text becomes the Task's subject; any linked appointment context migrates as a Task note referencing the original SwiftCRM Appointment. Reminders that have already fired in SwiftCRM are migrated as completed Tasks.

Notification history tied to client interactions in SwiftCRM maps to activity notes on the Person record in Pipedrive. If the notification includes a specific flag type (such as a privacy alert or a client-update flag), we map it to a custom Person field in Pipedrive rather than a free-text note to preserve structured data.

SwiftCRM Relationship structures between Contacts (family and business relationship types) are evaluated during scoping. If the relationships are binary (related person X to person Y), we create a custom Person field or a linked Activity note. If the relationship graph is complex (multiple relationship types per contact), we use a separate mapping table and document the relationship type in Pipedrive's activity log.

Beta-stage SwiftCRM custom fields vary by account tier and subscription level. We audit available custom fields during scoping and map each to a corresponding Pipedrive custom field. Pipedrive supports custom fields for People, Organizations, Deals, and Activities. Field types are matched (text to text, date to date, number to number, picklist to picklist) to avoid type mismatches during import.

SwiftCRM User accounts and basic permissions map to Pipedrive Users. We match SwiftCRM users to Pipedrive Users by email address during migration. Any SwiftCRM User without a corresponding Pipedrive User is held in a reconciliation queue for the customer's admin to provision before record import resumes, as OwnerId references are required for Activity and Deal ownership.

If SwiftCRM beta accounts include a tagging or labeling feature on Contacts or Appointments, we map these to Pipedrive Activity labels or custom Person fields. The specific mapping depends on the SwiftCRM tagging model discovered during scoping, as beta-stage tagging features may not have a stable API field name.

SwiftCRM exports that include organizational groupings or business entity data map to Pipedrive Organizations, with individual client records mapping to People linked to the Organization. If SwiftCRM does not have a distinct Organization object and all records are individual Contacts, we map everything to Pipedrive People without Organization linkage.