Migrate from TeamWave to Twenty CRM

TeamWave Contact records map to Twenty People. The mapping preserves name, email, phone, job title, and lifecycle stage as standard Twenty fields. Any TeamWave custom fields on Contact migrate as Twenty custom fields created under Settings → Data Model before import. We extract the contact's linked company_id from the TeamWave CSV and use it to resolve the Company-to-People relationship during the Twenty import phase.

TeamWave Company records map directly to Twenty Company. The company domain, address, and industry fields transfer as standard Twenty fields. Company records import before People records because the People CSV references a companyId foreign key. We cross-reference the TeamWave company_id to build the correct Twenty Company ID mapping for the People import.

TeamWave Deal records map to Twenty Opportunity. We transfer deal name, amount, stage, expected close date, owner, and deal value. The TeamWave dealstage maps to Twenty's opportunityStage field. If the customer has configured custom deal stages in TeamWave, we create matching stage values in Twenty Settings → Data Model before migration. Closed-won and closed-lost values transfer as-is; any custom deal fields become Twenty custom fields.

Each distinct stage value from TeamWave's deal pipeline must exist in Twenty's opportunityStage picklist before the Opportunity CSV is imported. We read the stage set from the Deal export, create the corresponding picklist values in Twenty, and configure probabilities per stage. TeamWave pipeline names do not have a direct Twenty equivalent; we map them to Twenty's Opportunity stage labels and document the pipeline-to-stage correspondence in the mapping spec.

TeamWave Project records carry name, description, status, client association, and start/end dates. Since Twenty has no native Project object, we create a custom object named Project in Settings → Data Model with fields for name, description, status, client (linked to Company), startDate, and endDate. Projects are imported after Companies and before Tasks to satisfy the client lookup.

TeamWave Tasks linked to Projects or Contacts map to Twenty Task records. We flatten the project-task hierarchy by creating Twenty Task records with the projectId resolved to the custom Project object created in Twenty. Task fields mapping: assignee maps to Twenty Task assignee (resolved via User lookup), dueDate maps to dueDate, status maps to status, and priority maps to priority. Standalone Tasks without a project link import with no WhatId.

TeamWave Users map to Twenty Members. We extract name, email, role, and department from the TeamWave Users export. Members must exist in Twenty before importing Opportunities and Tasks because ownerId and assignee references require a valid Twenty Member record. We run the Members import as a validation step before proceeding to record imports that carry ownership.

TeamWave Calendar Events carry event title, date/time, linked entity type (Deal, Project, or Contact), and attendees. Twenty has no native Event object, so we convert Calendar Events to Twenty Tasks with the activity date set to the original event start time and the title preserved. Attendee information is noted as a text custom field on the migrated Task record because Twenty's Task object does not support multi-contact attendee lists.

TeamWave HR module employee profiles (name, role, department, employee_id, hire_date) have no native Twenty equivalent. We map them to Twenty People records with custom fields added for department, role, and employee_id. If the customer uses TeamWave's org structure, we create a custom Department field and populate it from the HR export. Employee records are imported alongside customer People records; a boolean custom field employee_flag__c distinguishes employee records from customer contact records.

TeamWave custom fields on Contacts, Deals, Projects, and Tasks are exported with their data types and values. We create matching custom fields in Twenty under Settings → Data Model before importing each object type. Text fields map to Twenty text, date fields to date, numeric fields to number, and select fields to select. Custom field creation must complete before the associated object CSV is imported because Twenty's CSV import creates records, not fields.

TeamWave provides no bulk attachment download mechanism. We snapshot attachment metadata (filename, size, linked object type, and TeamWave record ID) into a manifest CSV. The customer uses the manifest to manually re-upload attachments to the correct Twenty record after migration. Binary attachments themselves do not transfer through the migration pipeline.