Migrate from Soffront to Twenty CRM

Soffront Contact records map to Twenty CRM Person objects. Standard fields (name, email, phone, address, lifecycle stage) migrate directly. Group assignments from Soffront map to Workspace memberships in Twenty. Custom picklist values on Contact records are mapped during the field inventory phase. Email opt-in and opt-out flags migrate to Twenty's Subscription fields.

Soffront Account records (representing organizations or companies) map to Twenty CRM Company objects. The Account-Contact relationship in Soffront becomes a Person-Company relationship in Twenty. All standard fields including industry, size, and custom properties migrate. Company is created before Person import so the lookup relationship is satisfied at insert time.

Soffront Deal records track opportunities through custom pipelines with stage names, amounts, and owners. Stage names vary between Soffront instances so we perform a value-mapping exercise during discovery to align with Twenty's pipeline stage model. Closed-won and closed-lost reasons from Soffront custom fields become custom opportunity fields in Twenty.

Soffront Activities include calls, emails, meetings, and tasks linked to Contacts or Deals. Activity type labels and custom activity fields require field-level mapping to Twenty's timeline model. Calls and tasks migrate as Task records; meetings migrate as Event records. Email content migrates as Task with the body preserved. Historical timestamps are preserved by setting ActivityDate to the original Soffront activity date.

Soffront Projects include status, milestones, assigned managers, resources, and due dates. Twenty CRM does not have a native Project object, so we split Projects into Workspace-organized Task hierarchies. Milestones become parent Tasks; sub-tasks become child Tasks. Project metadata (status, manager, due date) is stored as custom fields on the root Task record.

Soffront support tickets flow from capture through assignment, escalation, and resolution. If Twenty CRM is configured with the Tickets feature enabled, we map tickets directly. If not, tickets migrate as Tasks with a custom ticket_status__c field and priority preserved. Conversation history migrates as linked Task comments or activity entries.

Soffront Knowledge Base stores articles by category and links them to ticket types for agent lookup. Twenty CRM does not have a native Knowledge Base with category inheritance. We export Soffront articles with their category assignments, create a flat article structure in Twenty (custom object via /metadata API), and store the original Soffront category as a field on each article record for reference. Category labels are delivered as a separate mapping document.

Soffront supports custom object types beyond the standard data model. Twenty CRM exposes custom objects through the /metadata API. We inspect the custom object schema at the start of each migration, pre-create the equivalent Twenty custom object via API, including all custom fields, lookup relationships, and field types, before any custom object data is imported. Custom field naming follows Twenty's conventions.

Custom fields on Soffront standard objects are common due to the platform's high customization capacity. We capture field names, types, and picklist values during discovery and map each to a corresponding custom field in Twenty. Picklist values are re-created in Twenty's field schema before migration. This mapping document is validated against the source and destination before any records move.

Soffront Groups organize records for access control and segmentation. Twenty CRM uses Workspace-based access control. We map Soffront Group memberships to Twenty Workspace memberships during migration. If multiple Soffront Groups should share a single Twenty Workspace (a common pattern when Groups are used for segmentation rather than security), we document this as a merge decision during scoping and apply it during the import phase.

Attachments linked to Contacts, Deals, Tickets, and Projects are exported from Soffront and re-uploaded to Twenty CRM. File size limits and storage location vary by Soffront edition. We preserve the attachment's parent record relationship and store the original Soffront filename and link as metadata fields on the Twenty file record. On-premise Soffront users may have attachments stored in local file systems requiring a different extraction path than cloud users.