Migrate from SoulCRM to Twenty CRM

SoulCRM Company records map directly to Twenty Company objects. SoulCRM's company name, domain, industry, phone, address, and any linked GST identifiers in custom fields migrate to Twenty's Company fields plus a custom field for the GST number if present. Companies are imported first because Contacts and Deals have lookup dependencies that require the Company record to exist before the relationship can be established in Twenty.

SoulCRM Contact records map to Twenty Person objects with is_organization set to false. The full contact profile (name, email, phone, address, interaction history) migrates. SoulCRM contacts linked to a Company carry that relationship into Twenty via the Person's workspaceKey field, which is resolved at import time against the previously migrated Company record. Individual email addresses serve as the deduplication key.

SoulCRM Leads from the Marketing Module map to Twenty Person records with is_organization set to false. Lead status, source attribution, assignment fields, and any custom lead scoring values migrate as custom fields in Twenty. If SoulCRM's Marketing Module captures lead scoring, we preserve it in a custom field on the Person record for the customer's admin to use in Twenty's workflow builder.

SoulCRM Deal records map to Twenty Opportunity objects. The pipeline stage name, deal amount, probability (if stored), owner assignment, and expected close date migrate. SoulCRM's stage names are mapped explicitly to Twenty's opportunity stage values during the transform step. If SoulCRM stores a Closed-Won or Closed-Loss reason, it migrates as a custom field on the Opportunity.

SoulCRM pipeline stages (New, Qualified, Proposal, Negotiation, Closed Won, Closed Lost, and any India-specific regional stages) are mapped to Twenty's opportunity stage values during the transform. We configure Twenty's stage list in the workspace before migration begins so that stage values are available as valid picklist entries during Opportunity import.

SoulCRM email activities linked to Contacts or Companies migrate to Twenty TimelineEvent records. The email subject, body content, sender, recipient, and timestamp transfer. SoulCRM email body formatting (HTML or plain text depending on how it was captured in SoulCRM) may require a content-normalization step before display in Twenty's Timeline, and we flag this during the reconciliation phase.

SoulCRM call logs map to Twenty TimelineEvent records with the event type set to call. Call duration, disposition, and any notes from the call record migrate. The linked Contact or Company is resolved via the Person or Company lookup at migration time so the call appears in the correct Timeline in Twenty.

SoulCRM task activities migrate to Twenty Task records. Task status, priority, due date, and description transfer. If the task was assigned to a SoulCRM Owner, the assignee is resolved via the User mapping before import.

SoulCRM Marketing Module campaigns (name, type, start/end dates, budget) map to Twenty Opportunity records tagged with a campaign custom field. Campaign membership links (which SoulCRM associates to Contacts and Leads) are resolved by creating a custom many-to-many relationship: each SoulCRM campaign-contact or campaign-lead association creates a link record in Twenty that associates the Person with the campaign Opportunity. This requires two-phase import: campaign records first, then association records second.

SoulCRM custom fields for GST identifiers, regional sales segments, INR-based pricing tiers, and other India-specific data migrate as Twenty custom fields on the relevant object (Company, Person, or Opportunity). We audit each SoulCRM custom field during scoping, drop any deprecated fields with zero usage, and create the corresponding custom field in Twenty's workspace schema before data import begins. Field type mapping follows: text to text, number to number, date to date, and picklist to select.

File attachments linked to SoulCRM Contacts, Companies, or Deals are extracted as binary files and re-uploaded to Twenty via the File API. Folder hierarchy in SoulCRM is not preserved; all files land in Twenty's default attachment location linked to the corresponding record. We extract attachment metadata (filename, size, upload date) and recreate it as a custom field on the record for reference.

SoulCRM Owner records (sales reps, admin users) are mapped to Twenty User accounts by email address. We extract every distinct Owner referenced on Contacts, Companies, Deals, and Activities and match by email against Twenty's User table. Any SoulCRM Owner without a matching Twenty User is held in a reconciliation queue for the customer's admin to provision the User before the record import resumes.