Migrate from SalesTown CRM to Twenty CRM

SalesTown Contact records map directly to Twenty Person records. Standard fields (name, phone, email, address) map 1:1. Custom Contact properties migrate to Twenty's custom field infrastructure, with the workspaceMember querying the /metadata API to pre-create destination fields before import. Owner assignment from SalesTown maps to Twenty workspaceMember by email resolution.

SalesTown Leads collected via the Lead Management System split into Twenty Persons for unqualified leads and Twenty Opportunities for leads that progressed to a deal stage. We evaluate the Lead's stage, last activity date, and any deal association to determine the correct destination. The original LMS assignment and distribution rule are preserved as custom fields for audit.

SalesTown Company/Account records map directly to Twenty Company records. Company name, domain, industry, employee count, and address fields migrate 1:1. SalesTown's undocumented Company schema means we inspect the CSV export to identify available fields, map each to Twenty's Company object, and flag any unmapped fields in a reconciliation report for the customer to address post-migration.

SalesTown Deals map to Twenty Opportunities. Deal amount, stage, owner, expected close date, and pipeline assignment transfer directly. We resolve the parent pipeline and stage reference at migration time, ensuring the Opportunity stage maps to a Twenty pipeline stage that the customer's admin has configured before the import phase.

SalesTown Pipelines export with names, stage order, and stage-specific win/loss flags. We recreate Pipelines in Twenty before loading any Deals, configuring stage names, probabilities, and ordering to match the source. Pipelines with different stage counts between systems require explicit stage-to-stage mapping rather than positional mapping to prevent stage misalignment.

SalesTown Pipeline Stages carry names, probabilities, and ordering. Each stage is mapped explicitly to a Twenty Pipeline Stage during the configuration phase. Stage-specific probabilities migrate from SalesTown to Twenty stage probability settings. Stages that do not exist in Twenty are flagged for the admin to create before Deal migration begins.

SalesTown Activities (calls, emails, WhatsApp messages) map to Twenty Task and Event records. WhatsApp activities carry thread-level metadata that flat CSV exports split into individual rows, losing parent-child thread associations. We reconstruct thread relationships during the transform phase using timestamp ordering and sender IDs, rehydrating conversation continuity as grouped Task records in Twenty's activity timeline.

SalesTown User records (name, email, team assignment) map to Twenty WorkspaceMember records. We resolve owners by email match. Any SalesTown User without a matching WorkspaceMember in Twenty goes to a reconciliation queue for the customer's admin to provision before record import resumes. Duplicate email addresses at the destination are flagged and held from import until resolved.

SalesTown customizable email templates exist but have no documented schema. We export available template metadata (name, subject, available tags) and deliver it as a written template inventory. The customer rebuilds templates in Twenty's template editor. Template bodies, conditional content, and dynamic field insertions do not migrate automatically because they require schema-aware content transformation.

SalesTown custom Contact, Lead, and Deal properties migrate to Twenty's custom field infrastructure. We query the /metadata API in Twenty to discover existing custom field definitions, create any missing fields via the API, then map SalesTown custom property values to typed Twenty fields during the data transform phase. Picklist values in SalesTown map to Twenty select options; multi-checkbox properties map to multi-select.