Migrate from Capsule CRM to Twenty CRM

Capsule's individual Party records map to Twenty Contact records. We preserve first name, last name, email address, phone numbers, job title, and owner assignment. The Contact's relationship to the parent Organisation (now a Company in Twenty) is resolved by looking up the Capsule Party's Organisation ID against the Organisation-to-Company mapping table built in the preceding step.

Capsule Organisation Party records map to Twenty Company records. We preserve company name, domain, address fields, industry, number of employees, and annual revenue where populated. The Company is created before Contact migration begins so that the Company-Contact relationship is satisfied at insert time.

Capsule Opportunities map directly to Twenty Opportunities. We carry forward opportunity name, value, currency, expected close date, probability, owner, and the linked Party (resolved to Contact and Company). Capsule pipeline stage names map to Twenty stage names; if the names differ, we create a stage mapping table during configuration. Closed-won and closed-lost outcomes preserve as-is.

Capsule pipelines (multiple on Growth and above) map to Twenty stage configurations. Each Capsule pipeline stage becomes a Twenty stage with name, probability percentage, and ordering preserved. If the destination workspace uses a single default pipeline, we consolidate all Capsule pipeline stages under one workspace and flag the multi-pipeline source structure in the handoff documentation.

Capsule Cases track support or service issues linked to Parties. We migrate Cases as Twenty Tasks with a case flag or as a custom Case object if configured in the destination workspace. Status, priority, assignee, description, and linked Contact/Company are preserved. Case-type Tasks are segmented in Twenty's task list for visibility separate from standard sales Tasks.

Capsule Project objects (Starter and above) contain milestones and deliverables. Twenty does not have a native Project object in its standard schema. We flatten Project milestones into Tasks under the linked Opportunity, applying a project_name prefix to preserve grouping and setting due dates and completion status from the original milestone. The project structure is documented in the handoff so the customer's admin can decide on a rebuild approach.

Capsule Milestones (sub-objects of Projects) map to Twenty Tasks with a milestone flag field set to true. We preserve milestone name, due date, completion status, and the link to the parent Opportunity or Case. Tasks without a milestone flag represent standard sales or support tasks.

Capsule Tasks linked to Parties or Opportunities map to Twenty Tasks. We preserve due date, status (open, completed, cancelled), assignee, description, and the parent relationship. Tasks without an associated Party or Opportunity migrate as standalone Tasks with a no-parent flag for the admin to reassign post-migration.

Capsule Activities (email, call, meeting, note types) linked to Parties migrate to Twenty Activity records. We preserve activity type, direction (inbound/outbound), timestamp, body text, and the linked Contact. Activity ordering in the Twenty timeline is maintained by setting the activity date to the original Capsule timestamp. Call duration and disposition migrate as custom activity fields where supported.

Capsule's data-tag system requires a separate fetch from the /fields/definitions endpoint before field values can be correctly typed and migrated. We query all field definitions for Parties, Opportunities, and Cases before pulling record data, resolve list field options, and apply the correct type casting. Each resolved custom field maps to a corresponding custom field in Twenty, created in the destination schema before any records are imported.

Capsule tags are flat labels applied to Parties, Opportunities, and Cases. We translate tag names 1:1 into Twenty's tag model, which supports multiple tags per record. Where Capsule tags represent category or status data rather than loose labels, we discuss with the customer whether to migrate as tags or convert to a dedicated custom field with a defined picklist.

Capsule Users are mapped to Twenty Users by email address. We resolve every Capsule user referenced as an owner of Parties, Opportunities, Cases, or Tasks before record migration begins. Any Capsule user without a matching Twenty User goes to a reconciliation queue for the customer's admin to provision before migration resumes.