Migrate from Teamgate to Twenty CRM

Teamgate People records map directly to Twenty's Person object. Standard fields (name, email, phone, address) map to the equivalent Twenty Person fields. Custom fields on People migrate as custom fields on Person, which must be created in Settings before import per Twenty's documented import process. We preserve the original Teamgate record creation timestamp as a custom field for audit trails since Teamgate's API exposes created_at and updated_at timestamps.

Teamgate Company records map to Twenty Company. Industry classification, address data, employee count, and website from Teamgate Company map to their Twenty equivalents or to custom fields if the customer requires a field that Twenty does not include as standard. Twenty's standard Company fields are limited per GitHub issue #13953; we document any gap fields as custom fields to be created before import.

Teamgate Deals map to Twenty Opportunity. Deal value, stage assignment, expected close date, loss reason, and owner map to their Twenty Opportunity equivalents. Stage probabilities from Teamgate Pipeline Stages transfer to a custom field or to the Opportunity's stage configuration if Twenty's stage model supports probability weights.

Teamgate Pipelines (multiple named pipelines with stage order and probability weights) require manual recreation in Twenty's workspace. We export the full pipeline definition including stage names, sequence order, and probability percentages, and deliver this as a written configuration guide for the customer's admin to recreate in Settings. Twenty does not support multiple named pipelines at the native level; multi-pipeline teams use custom fields or a workaround strategy determined during scoping.

Each stage within a Teamgate Pipeline becomes an Opportunity stage in Twenty. Stage names, sequence order, and probability weights migrate from Teamgate to Twenty's stage configuration. Loss reason dropdown values from Teamgate export as Opportunity loss reason options in Twenty.

Teamgate custom fields on People, Companies, and Deals (text, number, date, dropdown, checkbox types) map to Twenty custom fields of equivalent type. Twenty's Settings → Data Model requires custom fields to be created before any CSV import, so we sequence field creation as the first pre-import step and validate the schema before beginning data migration. Dropdown options in Teamgate migrate as select options in Twenty.

Teamgate's flat tag strings on People, Companies, and Deals migrate to a multi-select custom field in Twenty. We export tags as a normalized list per record and create a tags custom field on the relevant object before import. If the customer prefers to use Twenty's Topic functionality, we document the alternative during scoping.

Teamgate Activities (tasks, calls, emails, meetings) linked to People or Deals migrate to Twenty Task records. Activity type, timestamps, and notes migrate as Task fields with activity type distinguished by a custom field or Task subtype. The activity timeline ordering is preserved by setting the Task due date to the original Teamgate activity timestamp. Large activity histories (over 50,000 records) require batched import with parent-record lookup resolution.

Teamgate file attachments (up to the tier storage limit of 5-200GB/user) export as file metadata via API, but actual binary files must be downloaded from Teamgate and re-uploaded to Twenty's storage. We calculate total file attachment volume during scoping and flag whether the customer's infrastructure can accommodate the re-upload. File names and links are preserved as custom fields pointing to the re-uploaded location.

Teamgate User records (name, email, role, active status) export for owner mapping in Twenty. Twenty requires all users to accept their workspace invitation before data with owner/user references can be imported, per Twenty's import documentation. We extract all distinct owner references on People, Companies, and Deals, match by email against the Twenty workspace User list, and flag any owners without a matching invited User in a reconciliation queue before migration begins.

Teamgate's configurable loss reason dropdown values migrate as Opportunity loss reason options in Twenty. We export all active loss reason values during scoping and create the corresponding select options in Twenty's Opportunity schema before Deal import.