Migrate from Variable Soft CRM to Twenty CRM

VSCRM's separate Lead object (distinct from Contact) maps to Twenty's unified Person object. We flag any VSCRM Leads that share an email address with an existing VSCRM Contact during deduplication. The original VSCRM Lead source, status, and owner assignment transfer to custom fields on the Twenty Person record. If VSCRM Lead records represent unqualified prospects only, all Leads land in Twenty as Person records with no associated Company link until manually connected.

VSCRM Contact records map directly to Twenty Person records. The VSCRM contact's primary company link resolves to a Twenty Company lookup, and lifecycle stage assignments from VSCRM transfer to custom fields on the Person. We run a deduplication pass comparing email addresses across the combined Lead and Contact export before writing to Twenty.

VSCRM Company records map to Twenty Company records. Company domain, address, and industry fields translate to their Twenty equivalents. The Company record must be written before any Person import so that the Person's companyId lookup is satisfied at insert time. VSCRM company records serve as containers for associated Contacts and Deals; we preserve this hierarchy through the Company-Person and Company-Opportunity relationships during import.

VSCRM Deals map to Twenty Opportunities. The VSCRM deal value maps to Opportunity amount, the pipeline stage maps to Opportunity stageName, expected close date maps to Opportunity closeDate, and owner assignment resolves to a Twenty User by email match. We validate that each Opportunity's linked Person and Company exist in Twenty before writing the Opportunity record.

VSCRM allows multiple named pipelines with custom stages. We extract pipeline names and stage labels from the Deal export and recreate them as Twenty Pipeline stages. Each VSCRM pipeline becomes a distinct stage sequence in Twenty. Stages with no associated Deals are recreated as empty stage containers. The customer confirms stage order and probability values during scoping.

VSCRM Activities linked to Contacts and Deals map to Twenty Activity records. Activity type (call, email, meeting, task), timestamp, linked entity (Person or Company), and content migrate directly. Activity assignment resolves to a Twenty User by email. Activities without a resolvable linked entity are imported as standalone Activity records and flagged for manual association during customer review.

VSCRM custom fields on Contacts, Companies, and Deals are discovered from the export file header row and recreated in Twenty via Settings → Data Model before any record is written. Field type mapping is inferred from VSCRM export data: text strings become Twenty text fields, numbers become number fields, dates become date fields, and multi-select values become select fields. We note any VSCRM custom field that contains data incompatible with its inferred type and flag it for the customer's admin to confirm type selection.

If VSCRM export includes custom object records beyond standard Leads, Contacts, Companies, and Deals, we create equivalent custom objects in Twenty before import. Twenty's custom object model supports many-to-one, one-to-many, and many-to-many relations, including relations with attributes on the relationship itself. We configure the custom object schema, its fields, and all relationships before any custom object data is written.

VSCRM workflow automations are stored server-side with no export mechanism. Any email triggers, field-update rules, or assignment automations configured in VSCRM do not carry over. We document every active automation identified during the discovery call and deliver a written rebuild checklist mapping each automation's trigger, conditions, and actions to its recommended equivalent in Twenty's SDK or via a Zapier workflow. Rebuild is the customer's responsibility post-migration.

VSCRM Owner records map to Twenty User records. We resolve owners by email address across the export. Any VSCRM Owner without a matching Twenty User is placed in a reconciliation queue for the customer's admin to provision the corresponding Twenty User before migration resumes. Inactive VSCRM owners map to inactive Twenty users.