Migrate from SalezShark to Twenty CRM

SalezShark Contacts map to Twenty Person records. Standard fields (name, email, phone, address) have direct equivalents. We preserve any SalezShark enrichment data (company email format, employee headcount) as static custom fields on the Person record since Twenty has no native enrichment engine. Note: Twenty's Person object may lack some standard fields (job title, department, social profiles) out of the box per GitHub issue #13953 — we create these fields in Twenty's Data Model before import if the source data references them.

SalezShark Leads with conversion scoring map to Twenty Person records. If the customer has a distinct lead qualification workflow, we create a custom Lead object in Twenty's Data Model before import and preserve the original SalezShark conversion score as a custom field. Leads that have been converted in SalezShark are treated as Person records with the original lead source preserved.

SalezShark Accounts map directly to Twenty Company records. The company name becomes displayName, website maps to websiteUrl, and industry/size/revenue data from SalezShark custom fields map to custom fields created in Twenty's Data Model. Company is imported before Person to satisfy the relationship reference.

SalezShark Opportunities map to Twenty Opportunity records. Pipeline stage names and order migrate as picklist values in Twenty's stage field. Deal value, close date, owner, and probability migrate directly. If SalezShark uses multiple pipelines, we create a custom pipeline field in Twenty and map stage names per pipeline to separate picklist value sets.

SalezShark Pipelines do not have a direct Twenty equivalent. We export the pipeline configuration (pipeline name, stage list, stage order, stage probabilities) and recreate it in Twenty as a custom Opportunity pipeline field plus stage picklist values. The customer chooses a naming convention during scoping.

SalezShark Tasks map to Twenty Task records. Task title, description, due date, status, priority, and owner assignment migrate directly. Task association (linked to Contact, Account, or Opportunity) resolves via the Person and Company name lookup at migration time. Completed-at timestamp migrates to a custom completedDate field if the standard Twenty task model does not include it.

SalezShark engagement activities map to Twenty Task records for calls and tasks, Comment records for notes, and a custom Activity object for meeting and email history if the customer requires the full timeline preserved. The original SalezShark timestamp becomes the activity date in Twenty. Call duration and disposition migrate as custom fields.

SalezShark Custom Fields are exported as schema alongside records. We create each custom field in Twenty's Settings Data Model before import, matching the data type (text, number, date, select, multi-select, currency). Picklist values in SalezShark migrate as option values in Twenty's select or multi-select fields. Fields are pre-created before any data load.

SalezShark Custom Objects (if any exist on the account) map to Twenty custom objects created via /metadata API. We define the object name, plural label, and all fields in Twenty's Data Model before migration. If the custom object has lookups to standard objects (Contact, Account, Opportunity), we resolve those references during the migration run using name-based lookup.

SalezShark User records map to Twenty WorkspaceMember records by email address match. Owner assignments on Contacts, Accounts, and Opportunities migrate by resolving the SalezShark owner email to a Twenty WorkspaceMember. Any SalezShark owner without a matching Twenty user is held in a reconciliation queue; the customer's admin provisions the WorkspaceMember before record import resumes.