Migrate from SalesNexus to Twenty CRM

SalesNexus Contacts map directly to Twenty People. We export the full contact schema via the get-all-fields endpoint including custom field IDs, enrichment data, and lifecycle stage properties, then map each to a Twenty People field or custom field created in Settings → Data Model. The contact's primary email address becomes the dedupe key during import. Owner assignment resolves by email match against Twenty Workspace Members.

SalesNexus Company records map to Twenty Companies. The company domain and website transfer to the Company record. We export Companies independently and link them to imported People via the company_name or company_id field on the contact record. No special handling required beyond standard lookup resolution.

SalesNexus Pipelines (up to 10 on Starter, 3 on Free) map to Twenty Opportunities organized by pipeline name. Each SalesNexus pipeline becomes a Twenty Opportunity view filtered by a custom pipeline_name field or a separate Opportunities tab. We preserve pipeline-level configuration including stage count and order for recreation in Twenty's stage editor.

SalesNexus Pipeline Stages (ordered integers with names and probability defaults) map to Twenty Opportunity stage values. We export the full stage schema and recreate it in Twenty via Settings → Data Model as select options on the Opportunities stage field. Probability percentages migrate as informational fields or custom probability fields depending on customer reporting needs.

SalesNexus Tasks with due dates, assignees, and completion status map to Twenty Tasks. Owner assignment migrates via email-to-Workspace-Member lookup. We export open and completed tasks, preserving the original created_at and due_date timestamps for activity timeline accuracy.

SalesNexus stores email templates with merge fields and HTML content. We export template bodies, subject lines, and merge field syntax. Twenty does not have a native email template object; templates migrate as Note records attached to the relevant People or Company for reference, and the customer's admin rebuilds them in their chosen email outreach tool. We document merge field mappings for manual translation.

SalesNexus custom fields on Contacts are identified by integer field IDs retrieved via get-all-fields. We export field labels, types, and values, then create equivalent custom fields in Twenty via Settings → Data Model before import. Field types map to Twenty equivalents: text fields to TEXT, picklists to SELECT, dates to DATE, checkboxes to CHECKBOX. Unique constraint handling uses Twenty's Advanced mode API names per documentation.

Same approach as Contact custom fields applied to Company records. Company-level custom fields export from SalesNexus get-all-fields with field IDs and types, then create in Twenty's Data Model under the Company object before migration. Lookup relationships to People require parent-record resolution before Company import completes.

SalesNexus stores call recordings and transcriptions linked to Contact Activity records. We export the transcription text and a URL reference to the recording. Binary audio files are not downloadable via API. Transcription text migrates as a Note attached to the relevant People record, and the recording URL is stored as a custom URL field for manual access. Call disposition and duration migrate as custom fields on the Note.

SalesNexus unlimited email archival (all plans) exports as email subject, body, date, direction (sent/received), and recipient. The email body exports as HTML; we convert to plain text for Twenty's activity rendering. Each email creates an Activity record on the People timeline. Direction, sender, and recipient map to activity metadata fields. Email threading references are not preserved in Twenty's current data model.

SalesNexus Users and Owners map to Twenty Workspace Members. We export the user list with email addresses and names, then match by email during import. Any SalesNexus Owner without a matching Workspace Member is flagged for the customer's admin to provision before record import resumes. Inactive or archived SalesNexus users map to inactive Twenty members for historical assignment preservation.

SalesNexus drip sequences and their active enrollments are not exportable via API. We can export the list of contacts currently enrolled in each sequence, the sequence name, and enrollment dates. This data migrates as Note records on each People record listing their active drip enrollments. We provide a separate sequence audit report listing all active sequences, step counts, and enrolled contact counts for the customer's admin to rebuild in Twenty's workflow builder or an external sales engagement tool.