Migrate from Sellsation CRM to Twenty CRM

Sellsation Customers are the primary account-level records storing company information, linked to Contact Persons and Sales Projects. We map them 1:1 to Twenty Companies. The Sellsation Customer name becomes Company name, and any linked Contact Persons are resolved via companyId during the People import phase. Sellsation does not publish an API, so export relies on the platform's CSV export function — we validate record counts against any UI-exportable data during scoping to confirm full field coverage before migration day.

Sellsation Contact Persons are individual contacts linked to Customers with full activity history. We map them 1:1 to Twenty People, preserving the link to the parent Company via the email domain or explicit companyId where available in the export. Any multi-email or multi-phone custom fields are mapped to Twenty's email and phone property formats. Because Twenty requires People to be imported after Companies (the companyId relation must resolve), we sequence the People import as phase two.

Sellsation Sales Projects are deal records tracked through pipeline stages with automated potential analysis. We preserve the pipeline stage name as an Opportunity status value in Twenty, and deal value migrates to the Opportunity amount field. Phase change history from Sellsation (stage movement timestamps) migrates as a series of Tasks or as a custom field capturing the last stage transition date. Sellsation's automated potential and strengths/weaknesses analysis data migrates as custom fields on the Opportunity if the platform exposes those values in its export.

Sellsation logs every call, appointment, note, and task as a separate activity record, and activity counts of 10–20x the contact count are common in mature accounts. We split activities at migration time: call engagements map to Twenty Task with TaskSubtype=Call preserved in a custom field; appointment records map to Twenty Task with the date range and attendee list migrated; notes migrate as Twenty Notes linked to the parent People or Company record. We process activity exports in time-bounded batches to avoid export file bloat, and we validate the chronological relationship between activities and their parent Contact Person or Sales Project.

Sellsation's multi-level campaigns with conditional stage movements, automated emails, and task creation have no direct equivalent in Twenty CRM. We export campaign enrollment data and campaign member records as a CSV that maps to Twenty's People records with a campaign tag. The campaign structure itself — conditional branching, automated follow-up sequences, stage-triggered actions — does not migrate; we deliver a written campaign inventory document describing each Sellsation campaign's trigger, conditions, and actions for the customer's admin to rebuild using Twenty's Workflow capabilities post-migration.

Sellsation supports custom fields on primary objects. We enumerate all custom fields during scoping and map them to Twenty's custom field schema under Settings → Data Model. Twenty requires custom fields to be created before CSV import (import creates records, not fields), so we pre-create the full custom field schema in Twenty during the schema preparation phase. Any picklist-dependent custom fields require additional mapping to ensure the Sellsation picklist values align with Twenty's select option configuration.

Sellsation's geo map and heatmap feature stores territory visualization as internal map state rather than standard geographic coordinates. We export the linked Sales Project location data as standard address fields in Twenty, preserving the geographic context without the native heatmap. The territory and heatmap configuration cannot be replicated in Twenty's current feature set; we document the original geo data as a structured export for any future BI or mapping tool integration the customer chooses.

Sellsation's standard reports and custom dashboard configurations do not have an export mechanism. We export the underlying data — Sales Projects, activity history, pipeline metrics — as CSV so the customer's Twenty team can rebuild reports from complete source data. The KPI definitions, chart configurations, and dashboard layout require manual rebuild in Twenty. We deliver a written KPI inventory describing each Sellsation report's metrics, filters, and data sources as a rebuild specification.

If Sellsation has custom objects defined, we map them to Twenty custom objects of equivalent name and schema. Twenty's custom object model requires pre-creation under Settings → Data Model before any data import, including all custom fields and lookup relationships. We sequence custom object import last because they often have lookups to standard objects (Companies, People, Opportunities), which must exist first. Any picklist values, validation logic, or formula dependencies in Sellsation custom objects are documented during scoping and recreated in Twenty's Data Model.

Sellsation user assignments on Contact Persons, Sales Projects, and Activities resolve to Twenty Workspace Members by email match. Twenty requires all team members to be invited and to accept their invitations before import, because OwnerId references on People, Opportunities, and Tasks must resolve to an existing user. Any Sellsation Owner without a matching Twenty member goes to a reconciliation queue for the customer's admin to provision before record import resumes.