Migrate from Sharpspring to Twenty CRM

SharpSpring contacts map directly to Twenty People. All standard fields (name, email, phone, job title, address) carry over. SharpSpring stores the company name on the contact; the import resolves this to a companyId link once the Company record exists in Twenty. We flag any contacts referencing companies that have no matching SharpSpring company record.

SharpSpring leads also map to Twenty People — both Lead and Contact objects land in the same Twenty People object. We preserve the original SharpSpring object type in a custom Source_Type__c field on each record so your team can distinguish migrated leads from migrated contacts in Twenty's UI.

SharpSpring company records map 1:1 to Twenty Companies. Company name, domain, phone, address, industry, and employee count all migrate. Parent-company relationships in SharpSpring map to Twenty's ParentId field if your Twenty workspace has the relationship configured, or are preserved as a custom field for manual linking.

SharpSpring deals become Twenty Opportunities. Deal name, amount, close date, and owner all map directly. The deal stage from SharpSpring's pipeline maps to Twenty's Stage field — we configure the Stage pick-list values in Twenty to match SharpSpring stage names before the Opportunity import runs.

SharpSpring pipelines define named stages with probability weights. Each pipeline stage name maps to a corresponding Twenty Stage pick-list value. We deliver a stage-mapping reference sheet before import so Twenty admins can pre-create the exact Stage values SharpSpring uses. Stage-enter timestamps are preserved as a custom datetime field for historical pipeline reporting.

SharpSpring lead status (Active Lead, Dead, Qualified, etc.) has no native equivalent in Twenty CRM. We migrate it as a custom single-select field (Lead_Status__c) on the People object. Your Twenty admin configures the pick-list options to match SharpSpring's active status values before migration.

SharpSpring behavioral lead scoring produces a numeric score stored on the contact. Twenty has no native lead scoring. The score migrates as a custom number field (Lead_Score__c) on People. Note that Twenty does not recalculate scores — the migrated value is static and represents SharpSpring's last computed score at migration time.

SharpSpring email logs migrate as Twenty Tasks with Type='Email'. Subject line maps to Task title, body maps to Task body, and original timestamp maps to the Task due date. Each email task is linked to the parent People record via Twenty's task-relation model.

SharpSpring call and meeting logs become Twenty Tasks with Type='Call' or Type='Meeting' respectively. Duration, notes, and outcome fields from SharpSpring map to custom fields on the Twenty Task. Original timestamps and the assigned owner carry over so activity history continuity is preserved on the People record.

SharpSpring notes migrate as Twenty Notes. Body content, create date, and owner all transfer. Notes attached to specific contacts, companies, or deals in SharpSpring are re-linked to the corresponding record in Twenty using the unique identifier mapping established during the People and Company import phase.

SharpSpring tags have no native equivalent in Twenty CRM. Tags migrate as a custom multi-select field (Tags__c) on the relevant object. The set of unique tag values from SharpSpring becomes the pick-list options in Twenty before the import runs. If a record has multiple tags in SharpSpring, all values populate the multi-select in Twenty.

SharpSpring VisitorID tracks anonymous website visitors by IP and cookie fingerprint. This is a behavioral tracking construct with no CRM equivalent. VisitorID migrates as a custom text field (VisitorID__c) on People records for reference. Note that visitor tracking is a marketing function — it does not translate to an operational field in Twenty.

SharpSpring custom objects (Enterprise tier) map to Twenty custom objects. The custom object must be pre-created in Twenty's Settings → Data Model before migration. Custom fields within the object map field-by-field to the corresponding Twenty custom fields. N:N relationships between SharpSpring custom objects may require junction table objects in Twenty.

SharpSpring file attachments on records do not export via standard CSV. We provide a file inventory from SharpSpring's API and a step-by-step re-upload guide for Twenty's file attachment UI. If your SharpSpring plan includes file storage, budget time for manual re-uploading or discuss API-based file migration with our team.