Migrate from Simplicity Enterprise CRM to Twenty CRM

Simplicity Contact records map to Twenty Person. Standard fields (firstName, lastName, email, phone, address) translate directly. Simplicity's behavioural and segmentation properties (lifecycle stage, lead score, source channel) migrate as custom fields on Person because Twenty's data model accommodates these without requiring a separate object. We resolve the Company linkage from Simplicity's contact-company relationship and attach the Person to the corresponding Twenty Workspace during import.

Simplicity Company records map to Twenty Workspace. Company name, domain, industry, employee count, and address fields map 1:1. Simplicity's relational links to Contact records migrate as Person records linked to the Workspace via the workspaceId field. Workspace must be created before Person import so the lookup relationship is satisfied at insert time.

Simplicity Deal records map to Twenty Opportunity. Deal name, value, expected close date, and stage map to Opportunity name, amount, closeDate, and stage. Simplicity's configurable pipeline stages require explicit stage-to-status value mapping during scoping. We pre-create the Twenty pipeline configuration before migration to ensure stage names align with the imported deal records.

Simplicity's client-configurable pipeline stages map to Twenty pipeline stages. Each Simplicity stage name translates to a Twenty stage with an explicit probability percentage. Stage order is preserved in the Twenty pipeline configuration. If Simplicity uses multiple pipelines, we create multiple Twenty pipelines with corresponding stage sets.

Simplicity email activities map to Twenty Task records with taskType = Email. Email subject, body, timestamp, and sender/recipient information migrate as Task fields. The task is linked to the parent Person or Workspace via the Twenty activity API. ActivityDate is set to the original Simplicity timestamp to preserve timeline ordering.

Simplicity call activities map to Twenty Task with taskType = Call. Call disposition, duration, and notes from Simplicity migrate as custom fields on the Task record. The task is linked to the parent Person or Workspace at migration time after Person resolution is complete.

Simplicity meeting activities map to Twenty Task with taskType = Meeting. Meeting title, start and end timestamps, location, and attendee list migrate as Task fields. Attendees resolve to Person records in Twenty and are linked via the activity API.

Simplicity notes map to Twenty Task with taskType = Note. Note body and creation timestamp migrate directly. Notes linked to specific contacts or companies in Simplicity resolve to the corresponding Person or Workspace in Twenty before the Task insert.

Simplicity Campaign records have no native Twenty equivalent. We create a Campaign custom object in Twenty with fields for campaign name, type (email, social, SMS, print), start and end dates, status, and budget. Campaign-to-contact response associations from Simplicity migrate as a separate CampaignMember custom object that links Person to Campaign with response status and channel fields.

Simplicity Segments define which contacts belong to behavioural or demographic groups. Segment membership migrates as a multi-select picklist field on Person in Twenty, or as Tags if Twenty's tag feature is enabled in the target instance. The customer chooses the strategy during scoping based on how segments are used in reporting.

Simplicity Loyalty module stores reward tiers, point balances, and program membership as separate relational records. We create a Loyalty custom object in Twenty linked to Person with fields for program name, membership ID, point balance, tier, and enrollment date. Loyalty program rules and reward tier definitions migrate as a separate LoyaltyProgram custom object for reference.