Migrate from SuiteCRM to Twenty CRM

SuiteCRM Accounts map directly to Twenty Companies. Account name maps to Company.displayName, industry maps to Company.industry, website maps to Company.domain, and address fields map to Company.address. We extract all Account records via the SuiteCRM REST API (v4.1 for 7.x, v8 for 8.x) before importing Companies into Twenty. The Account ID is preserved in a custom field suitecrm_id__c for relationship reconciliation during the Contact import phase.

SuiteCRM Contacts map to Twenty People records. Name fields (first_name, last_name) map to People.displayName or firstName/lastName depending on the customer's preference. Email, phone, and title migrate to People.email, People.phone, and People.jobTitle. The primary Account link migrates as a Company relation in Twenty. We resolve the Account reference by looking up the SuiteCRM Account ID against the suitecrm_id__c custom field we set during the Account import phase.

SuiteCRM Leads are a separate module from Contacts. In Twenty, Leads can either map to People records (if the customer wants a unified person object) or to a custom Lead object created in Settings → Data Model before import. We make this decision during scoping based on the customer's pipeline: if Leads represent unqualified prospects that go through a separate qualification step, a custom Lead object preserves that lifecycle. Lead status and source fields migrate to custom People fields or custom Lead fields respectively.

SuiteCRM Opportunities map directly to Twenty Opportunities. Deal amount maps to Opportunity.amount, close date maps to Opportunity.closeDate, and sales stage maps to Opportunity.stage. The probability percentage migrates to a custom Opportunity field or is used to compute a display probability. The Account link migrates as a Company relation resolved via suitecrm_id__c lookup. Pipeline-specific stage values become Twenty Opportunity stage values configured before import.

SuiteCRM Cases track support issues linked to Contacts or Accounts. Case records migrate to Twenty Tasks with the case title as Task.title, status mapped to Task.status, and priority mapped to Taskriority. The related Contact or Account link migrates as a People or Company relation in Twenty. Case descriptions migrate as Task.body or Note records attached to the Task. Closed-case history is preserved as completed Tasks.

SuiteCRM custom fields added via Studio are stored in extended database tables with a naming convention appended to the module name. We scan the SuiteCRM database schema to identify all extended column names, map their data types (varchar to text, int to number, date to date, enum to select, multienum to multiselect), and pre-create the equivalent custom fields in Twenty Settings → Data Model before any CSV import begins. This step is critical: Twenty's CSV import creates records only, not fields.

SuiteCRM Documents store files on the server filesystem (typically upload/) with a database record containing metadata. We extract both the file blobs and the metadata records. Files are copied to a local staging directory with checksums validated post-copy. On import into Twenty, we reattach files as Note or Attachment records linked to the parent Company, People, or Opportunity record. File system permission issues during extraction are a known migration risk: we validate file integrity checksums after extraction and flag any inaccessible files in the reconciliation report.

SuiteCRM Users map to the owner field on all records. We export the Users table including usernames and email addresses. In Twenty, Workspace Members must be invited and accept their invitation before data import can reference them as owners or assignees. We extract all distinct owner_ids referenced on Contacts, Accounts, Opportunities, and Cases, match by email against the Twenty workspace Members list, and flag any unmatched owners in a reconciliation queue for the customer's admin to provision before import resumes.

SuiteCRM Campaigns have no direct equivalent in Twenty's core schema. We create a custom Campaign object in Twenty Settings → Data Model before migration, capturing campaign name, type, status, start date, and budget. Campaign target lists (Target Lists module) migrate as custom relationship fields linking People records to the Campaign custom object. Campaign response activity (opens, clicks) migrates as Task records attached to the Campaign custom object rather than as native engagement records.

SuiteCRM Products store the product catalogue used in Quotes and Opportunities. We create a custom Product object in Twenty with fields for name, SKU, description, and price. If the customer uses Quotes heavily, we create line item fields on the custom Product object and reference them from Opportunities. Product taxonomy (categories, families) migrates as select or multiselect custom fields on the Product custom object.

SuiteCRM Quotes reference Opportunities and include line items linked to the Products catalogue. Twenty has no native Quotes object at its current release stage. We export Quote body content and line items, recreate the Quote as a Note attached to the relevant Opportunity record, and preserve the PDF as a file attachment if available. The customer's admin rebuilds formal quoting using Twenty's API or a third-party quoting tool post-migration.

SuiteCRM Invoice records track payment status but have no connection to an accounts-receivable ledger or payment reconciliation system. We export Invoice records as-is and flag them as partial data in the migration report. Since Twenty has no native accounting module, Invoices migrate as Note records attached to the relevant Account, with payment status preserved as a custom field. The customer's finance team sources the full financial reconciliation layer from their accounting system.