Migrate from Salescamp CRM to Twenty CRM

Salescamp Leads map directly to Twenty People. Standard fields (name, email, phone, source, status) migrate to the corresponding Twenty People fields. The Lead's Collection membership does not have a direct People field in Twenty; we map Collection to Tags on the People record, creating tag values per Collection name for segmentation. If the same Lead appears in multiple Salescamp Collections, we create a single People record and attach all Collection tags, flagging the deduplication during the import report.

Salescamp Company records map to Twenty Company. Company is created before any People import so that the People-Company link is resolved at insert time. The Company domain or website field becomes the dedupe key. If Salescamp has Company records linked to Leads, we resolve the relationship by matching Company name or domain to the target Twenty Company.

Salescamp Deal Pipeline entries map to Twenty Opportunity. Each pipeline stage from Salescamp becomes a Stage value on the Twenty Opportunity. Deal value, close date, and owner assignment migrate directly. Pipeline assignments that use multiple pipelines in Salescamp map to a custom Opportunity field (e.g., pipeline_name__c) in Twenty if the customer uses more than one pipeline.

Each Salescamp pipeline stage becomes a Twenty Opportunity Stage value. We create the stage names and their ordering in Twenty Settings before importing Opportunities. If Salescamp has probability percentages per stage, we set those in Twenty as stage probability values for forecasting alignment.

Salescamp Collections are organizational groupings without a direct Twenty equivalent. We map Collection membership to Twenty Tags. Each unique Collection name becomes a Tag value. A Lead that appears in Collection A and Collection B receives two Tag records in Twenty, both pointing to the same People record. The customer chooses during scoping whether to use Tags or Topics for this mapping.

Salescamp Call logs migrate to Twenty Task records with call-type metadata preserved in custom fields (call_duration__c, call_disposition__c). The original call timestamp becomes the Task due date. The Task is linked to the parent People or Company record via the Twenty relationship API.

Salescamp SMS logs migrate to Twenty Note records linked to the parent People record. SMS content migrates as Note body text. Timestamp preserves the original SMS send time. If the SMS was attached to a specific Deal, the Note links to the corresponding Opportunity record.

Salescamp email sync data migrates to Twenty Note records with email metadata preserved. Subject line becomes the Note title; email body becomes Note content. The Note is linked to the parent People, Company, or Opportunity record. Email attachments migrate as file attachments on the Note record.

Salescamp meeting notes migrate to Twenty Note records. Meeting title, attendees, location, and body text map to the Note fields. Timestamp preserves the original meeting date. Meeting-related attachments migrate as file attachments on the Note.

Salescamp Users and Owners map to Twenty Members. We match by email address. Any Salescamp Owner referenced on a Lead, Company, or Deal must have a matching Twenty Member record before import; otherwise, the OwnerId reference cannot be set and the record goes to a reconciliation queue. Twenty requires Members to be invited and active before Owner lookups resolve, per Twenty's migration documentation.

Salescamp custom fields per object migrate to Twenty custom fields created in Settings → Data Model before import. Field type mapping is validated per field: picklist values become select options, date fields become date fields, text fields become text fields. We pre-create the custom fields in Twenty during the schema setup phase so that the CSV import references existing fields rather than creating new ones at import time.