Migrate from Teamwork CRM to Twenty CRM

Teamwork CRM Companies map directly to Twenty Companies. Each Company can have multiple associated People records. We extract Company records first in every migration run to satisfy the foreign-key constraint when People are imported, because Twenty's Company object is the parent of People in the relational model. We preserve the company domain as the website field and use it as a dedupe key during import to catch duplicates that exist in Teamwork's list-view export.

Teamwork CRM Contacts map to Twenty People records. The primary Company association is resolved to the Twenty Company record inserted in the previous phase, and the foreign key is set at import time. Standard Contact fields (name, email, phone, address) migrate 1:1. Custom Contact fields of type short text, integer, and dropdown map directly to equivalent Twenty field types created in Settings → Data Model before import. Contacts without a valid Company reference are held in a reconciliation queue and imported after the Company mapping is confirmed.

Teamwork CRM Leads (early-stage prospects before qualification) map to Twenty People records. Teamwork allows separate Leads and Opportunities pipelines running simultaneously; we treat Lead records as People with a stage tag or custom field that captures the original Lead pipeline and stage so that the customer's admin can triage qualification after migration. Lead status and lead score migrate as custom fields on the People record.

Teamwork CRM Opportunities map to Twenty Opportunities. The Opportunity value, probability, close date, and pipeline assignment transfer directly. Stage names and stage probability weights are recreated as named stage values in Twenty's Opportunity configuration before import. The primary Contact or Company reference resolves to the Twenty record inserted in earlier phases.

Each Teamwork CRM Pipeline becomes a named Pipeline in Twenty's Opportunity settings. We extract the pipeline ID, name, and stage definitions (stage label, sort order, probability percentage) from Teamwork's list-view export and recreate them as Twenty Pipeline records before any Opportunity data is imported. Auto-prioritization flags and deprecated stages are flagged to the customer for manual cleanup in Twenty's UI post-migration.

Teamwork CRM Stages are configurable per Pipeline and support custom names, sort order, and probability values. We map stage IDs and labels to Twenty's stage model, preserving the probability percentage as the stage weight. If Teamwork uses deprecated stages with zero probability, we flag them as inactive in Twenty and reassign any Opportunity records currently sitting in those stages.

Teamwork CRM call Activities map to Twenty Task records with call-type metadata preserved in custom fields. Call duration, call disposition, and any notes recorded in Teamwork transfer to Twenty's task body and custom fields. We preserve the original Teamwork timestamp as the task due date to maintain activity ordering in the timeline.

Teamwork CRM meeting Activities map to Twenty Task records. Meeting title, description, start time, duration, and location transfer. Attendees from Teamwork's meeting record are stored as a custom multi-select field or note on the Twenty Task, because Twenty does not have a native EventAttendee model at migration time.

Teamwork CRM task Activities map to Twenty Task records. Status (open/closed), priority, due date, and assignee transfer directly. The assignee resolves by matching the Teamwork owner email to the Twenty workspace member record provisioned during the Owner reconciliation phase.

Teamwork CRM custom fields of type short text, integer, and dropdown migrate to Twenty custom fields of equivalent type created in Settings → Data Model before any data import. Multi-select, date, and boolean custom fields do not exist in Teamwork CRM natively (they require workarounds), so no direct migration path exists for those types. We document any workarounds the customer uses for unsupported field types and map them to the closest Twenty equivalent.

Teamwork CRM Users who own records (Contacts, Companies, Opportunities) map to Twenty workspace members by email match. We extract all distinct owner IDs referenced on migrating records and reconcile them against the Twenty workspace members list. Any Teamwork owner without a matching Twenty member goes to a reconciliation queue; the customer's admin provisions the missing member before record import resumes. This is a prerequisite step because OwnerId references are required on standard Twenty objects.

Teamwork CRM Tags (loose labeling on Contacts and Opportunities) transfer to Twenty Tags. If Twenty's workspace does not have an equivalent tag model, we map tags to a custom multi-select field on the target object. The customer selects the tag strategy during scoping. Tag names migrate 1:1; tag frequency and tag taxonomy are preserved.