Migrate your Teamwork CRM data

Contacts are the primary person records, each associated with exactly one Company. Standard fields (name, email, phone, address) are fully migratable. We map all custom Contact fields and preserve the Company link during import.

Companies are the account-level records that carry billing and firmographic data. Each Company can have multiple associated Contacts. We sequence Companies first in migration runs to preserve the Contact-to-Company parent relationship.

Leads represent early-stage prospects before qualification. Teamwork CRM allows configurable lead stages and the option to run separate Leads and Opportunities pipelines simultaneously. We preserve lead status and owner assignment.

Opportunities are the deal-level records within a pipeline, carrying value, probability, and stage. We map stage names, custom probability weights, and the pipeline association. Note that board-view exports are not available — we always extract from list view.

Teamwork CRM supports multiple named pipelines and allows separate Leads and Opportunities pipelines. We carry pipeline definitions, stage order, and stage-to-probability mappings. Auto-prioritization settings transfer as boolean flags.

Stages are configurable per pipeline and support custom names, sort order, and probability values. We map stage IDs and labels to the destination system and flag any deprecated stages the customer has archived.

Activities include calls, meetings, and tasks linked to Contacts or Opportunities. The SyncHub entity model exposes title, description, start date, duration, due date, completion status, and assignee counts. Activity type taxonomy may differ between CRMs — we normalize type labels at migration time.

Custom fields are available on the Premium/Pro tier and support three types: short text, integer number, and dropdown. Multi-select, date, or boolean custom fields are not supported natively by Teamwork CRM. We flag any unsupported field types found in the source CRM and map them to the nearest equivalent or a custom note field.

Users represent the sales team members who own records and receive assignments. We preserve user IDs, names, and email addresses. Note: the API V2 people endpoint has a known issue where working hours may return zero for users whose profile was never explicitly saved — we flag affected user records during extraction.

Tags allow loose labeling of Contacts and Opportunities for segmentation. Tag names transfer 1:1, but the destination CRM may not have an equivalent tag model — in those cases we map tags to a custom multi-value property or a text list field.

Teamwork CRM does not support attaching files or email threads to Contact records. Reviewers explicitly cite this as a limitation. We do not migrate file attachments associated with Contacts because the target platform cannot receive them. Files linked to Opportunities or Projects are migrated where the Teamwork Projects API supports it.

Saved custom filters are workspace-level configurations that do not carry business data — they are migration metadata only. We capture filter definitions (field conditions and operator logic) as a reference artifact but do not reconstruct them in the destination system unless the target supports an equivalent filter-save feature.