Migrate from Teamwork CRM to Pipedrive

Teamwork CRM Company records map to Pipedrive Organization. The Company name, domain/website, phone, address, industry, employee count, and annual revenue fields migrate 1:1. We sequence Organizations as the first object in the migration run because every Contact record requires an Organization lookup (Pipedrive's person-record model links People to Organizations via the org_id field). If a Teamwork CRM Company has no contacts, we still create an Organization to preserve the firmographic data.

Teamwork CRM Contact records map to Pipedrive People. Standard fields (name, email, phone, address) migrate 1:1. Each Contact's company_id resolves to the Organization record created in the previous step. Custom Contact fields migrate to Pipedrive custom Person fields of matching type where possible. Note: Teamwork CRM does not support attaching files or email threads to Contact records natively, so no attachment migration is required or possible from this object.

Teamwork CRM Opportunities map to Pipedrive Deals. Deal name, value, probability, stage, expected close date, owner, and associated Contact and Company links migrate directly. The pipeline and stage names from Teamwork CRM map to Pipedrive pipelines and stages that we configure in the destination workspace before Deals load. If a Teamwork CRM customer uses the separate Leads pipeline alongside Opportunities, Leads map to Pipedrive Leads (a separate object type) and the customer's Pipedrive admin decides whether to run parallel Pipedrive pipelines or consolidate into a single deal pipeline.

Teamwork CRM Leads (early-stage prospects before qualification) map to Pipedrive Leads. If the customer runs both Leads and Opportunities pipelines simultaneously in Teamwork CRM, we preserve both as separate Pipedrive pipelines or consolidate them into a single deal pipeline per the customer's preference during scoping. Pipedrive requires pipelines and stages to exist before the Import2 tool or API can import Deals and Leads; we configure these as a prerequisite step before any record migration begins.

Each Teamwork CRM pipeline's stages map to Pipedrive Stage records within the corresponding Pipeline. We capture stage order, probability percentage, and stage name. Probability values migrate to Pipedrive stage probability fields with rounding to integer values. Pipedrive stages are tied to a Pipeline; we create Pipedrive Pipelines first, then populate the stage definitions before any deal or lead records load.

Teamwork CRM's named pipelines (Leads pipeline and Opportunities pipeline) map to Pipedrive Pipelines. Multiple pipelines from Teamwork CRM become multiple Pipedrive Pipelines, each with its own stage sequence. If Teamwork CRM has auto-prioritization enabled on a pipeline, we document this as a Pipedrive Workflow automation for the customer's admin to rebuild post-migration.

Teamwork CRM users (owners) map to Pipedrive Users by email address. We extract every distinct owner_id referenced on Contact, Company, Deal, and Engagement records and attempt email matching against the destination Pipedrive account's user table. Any owner without a matching Pipedrive User goes to a reconciliation queue; the customer's Pipedrive admin must provision the User in Pipedrive before record import resumes. Owner assignment on Deals and Contacts uses the resolved Pipedrive User ID.

Teamwork CRM call Activities map to Pipedrive Task records with TaskSubtype set to Call. Title, description, duration, call disposition, and the associated Contact or Deal link migrate. Activity timestamps preserve as the Pipedrive Task due date and completion date. Note: Pipedrive's activity timeline shows Tasks as entries in the deal timeline, which differs from Teamwork CRM's standalone Activity log view.

Teamwork CRM meeting Activities map to Pipedrive Task records with TaskSubtype set to Meeting. Title, description, start time, duration, location, and the associated Contact or Deal link migrate. We set the Pipedrive Task due date and assignee from the original Teamwork CRM meeting record. Recurring meetings are not supported in Pipedrive's standard import model; these are documented for manual rebuild if applicable.

Teamwork CRM task Activities map to Pipedrive Task records with standard Task subtype. Title, description, due date, completion status, and priority migrate. Assignment migrates by resolving the Teamwork CRM owner_id to the Pipedrive User ID via the user lookup step. Recurring tasks are not migratable through API and are flagged for manual rebuild in Pipedrive.

Teamwork CRM custom fields of type short text, integer, and dropdown migrate to Pipedrive custom fields of the equivalent type. We pre-create Pipedrive custom fields for both Organization and Person types before record import. Note: Teamwork CRM does not support multi-select, date, or boolean custom fields natively, so migrations with Teamwork CRM workarounds (such as storing dates as text) require normalization before Pipedrive import to avoid type mismatches.

Teamwork CRM tags on Contacts and Deals migrate to Pipedrive Labels (a native tag model available from the Essential tier). Tags with fewer than 50 distinct values map directly to Labels. Tags with high cardinality or those used for data classification rather than loose labeling are mapped to a Pipedrive custom field (dropdown or multi-select) at the customer's preference during scoping.