Migrate from SwiftCRM to Twenty CRM

SwiftCRM Contact records map directly to Twenty People. Name fields (first name, last name), phone, email, address, and any Face ID-protected custom properties migrate as standard People fields or custom fields pre-created in Twenty Settings → Data Model. Relationship metadata from SwiftCRM's relationship tracking (family, business) migrates to custom contact properties or custom field types in Twenty's People object. We preserve the SwiftCRM contact identifier in a custom field swiftcrm_id__c for cross-system audit.

SwiftCRM stores organization context within Contacts rather than as a separate Company object. During scoping we assess whether the customer uses organizational groupings; if so, we split these into Twenty's Company records and link People via the workEmail domain or a manual organization field. If no formal company structure exists in SwiftCRM, People records are created without a Company link.

SwiftCRM Appointments migrate to Twenty Event records when they represent scheduled calendar entries (with start and end timestamps). The client link preserves by resolving the SwiftCRM contact reference to the migrated Twenty People record via swiftcrm_id__c. Reminders and notification metadata from the Appointment migrate as custom fields or as Twenty Task records if the customer prefers task-based activity tracking.

SwiftCRM Reminders tied to specific clients or appointments map to Twenty Task records. Status, Priority, and due date migrate directly. The SwiftCRM notification context (reminder type, recurrence) is preserved in custom Task fields. Tasks without a matching People record in Twenty are held in a reconciliation queue during scoping.

SwiftCRM notification history tied to client interactions migrates as Note records in Twenty, linked via ContentDocumentLink to the corresponding People record. Notification type, timestamp, and content body are stored in custom Note fields. We do not replicate the active notification delivery mechanism as Twenty does not have a native push notification system for CRM activity.

SwiftCRM e-documents attached to client records migrate as Twenty Attachments linked to the corresponding People record via ContentDocumentLink. We export the file binary and metadata, then attach to the target record during migration. File organization structure (folders, tags) from SwiftCRM's e-doc system is preserved as a custom text field on the Attachment record for navigation reference.

SwiftCRM relationship structures between contacts (family, business) map to custom multi-select or relation-type fields on Twenty's People object. We audit the relationship types during scoping, create matching custom fields in Twenty Settings → Data Model before migration, and populate with the related People record reference where Twenty's relationship field type supports it.

SwiftCRM beta-tier custom fields migrate to equivalent Twenty custom fields. Field types map to Twenty field types (text, number, date, select, multi-select, relation). We audit available custom fields during scoping, create the corresponding fields in Twenty Settings → Data Model before any record import, and flag any fields that cannot be mapped due to type incompatibility for the customer admin to resolve.

SwiftCRM user accounts and basic permissions map to Twenty WorkspaceMember records. We extract users by email address, invite them to the Twenty workspace during preparation, and wait for acceptance before migrating any records that carry an Owner or assignee reference. Users without an email in the destination workspace cannot have Owner lookups resolved and go to a provisioning queue.

If SwiftCRM contains deal or opportunity-like records (closed-won pipeline tracking), these map to Twenty Opportunity. Opportunity name, amount, stage, close date, and owner migrate as standard Opportunity fields. Stage values are mapped to Twenty Opportunity stage picklist values configured before migration. If SwiftCRM has no deal object, this mapping is omitted from the migration scope.