Migrate from Simply CRM to Twenty CRM

Simply CRM Contact records map to Twenty People. Name fields split into firstName and lastName on the Twenty side. Email, phone, and jobtitle transfer directly. The company_id field becomes a companyId relation — the related Company must exist in Twenty first, which is why Companies migrate before People.

Simply CRM Company maps to Twenty Companies with full field parity for name, domain/website, industry, numberofemployees, and annualrevenue. Parent-company hierarchy in Simply CRM (parentid field) maps to a self-referential relation in Twenty using the same parent-company ID logic. Address fields consolidate into a single address string or remain split if Twenty's workspace uses the multi-field format.

Simply CRM Deal records transfer to Twenty Opportunities. Deal name, amount, closedate, and stage map to opportunityName, amount, closeDate, and stage respectively. The owner_id resolves by matching Simply CRM user emails to Twenty Workspace Member emails. Deal pipeline and probability values migrate as-is; stage-entered timestamps are preserved as custom datetime fields for reporting continuity.

Simply CRM call and email activities become Twenty Tasks with Type set to 'Call' or 'Email' and Subject carrying the original activity description. Meeting activities map to Twenty Tasks with type 'Meeting' and startDate/endDate from the Simply CRM activity timestamps. The parent_id field links back to the related Contact or Deal record using Twenty's relation model.

Simply CRM Notes transfer as Twenty Notes. Body text, create date, and owner_id map directly. Notes attach to the same parent record (Contact, Company, or Deal) via Twenty's relation system. Rich-text formatting in Simply CRM notes is preserved as plain text in Twenty's Note body.

Simply CRM Users resolve to Twenty Workspace Members by email address. If a Simply CRM user email has no matching Twenty member, records are assigned to a fallback owner specified by the customer before migration. This prevents orphaned records where Opportunity or Task owner fields would otherwise be null.

Simply CRM deal pipelines map to Twenty Opportunity stage pick-list values. Each pipeline stage in Simply CRM becomes a named stage option in Twenty's stage field. Stage order is preserved based on Simply CRM's stage sequence. If Simply CRM has multiple pipelines, all stage names collect into a single Twenty pick-list — your admin decides which stages apply per opportunity type.

Simply CRM custom fields on Contacts, Companies, Deals, or Activities require pre-creation in Twenty at Settings → Data Model before the import runs. Field type mapping: text strings to text fields, numbers to number fields, dates to date fields, and pick-lists to select or multi-select fields. Custom field values on records migrate after the field definition exists in Twenty.

Simply CRM custom modules (if present) transfer to Twenty Custom Objects. The migration creates the equivalent object definition in Twenty's data model, then imports records with their relation fields pointing to People, Companies, or Opportunities. N:N relationships between custom modules use Twenty's relation fields, which support multi-value linking.

Simply CRM document and attachment records referencing files on the platform do not have a direct equivalent in Twenty's current import model. Files are re-uploaded as attachments to the target record in Twenty if they are accessible via the Simply CRM export. Files that are stored only in Simply CRM's internal document management are flagged for manual re-upload after migration.