Migrate from Teamgate to Pipedrive

Teamgate People records map to Pipedrive Person records. If the Teamgate Person has an associated Deal (indicating qualification), we map it to a Pipedrive Person linked to an Organization. If the Person is unqualified with no associated Deal, we create a Pipedrive Lead. The split is computed using the presence of an open or closed Deal on the Person record at migration time.

Teamgate Company records map directly to Pipedrive Organization. The Company domain and address fields transfer to Organization website and address fields. Organization is created before Person import so that the Organization-Person relationship is satisfied at the moment of Person insert.

Teamgate Deals map directly to Pipedrive Deals with the same deal value, expected close date, loss reason, and owner assignment. The Teamgate pipeline and stage assignment map to a pre-created Pipedrive pipeline and stage. We compute the Pipedrive pipeline ID and stage ID before migration and write them directly into the Deal import payload.

Each Teamgate Pipeline is recreated in Pipedrive with the same pipeline name and stage sequence. Stage probability percentages migrate from Teamgate to Pipedrive stage probability values. We create pipelines in Pipedrive first and store their IDs as a lookup table for Deal import mapping.

Teamgate stages within each Pipeline map to Pipedrive stages within the corresponding pipeline. Stage order and probability percentages transfer. Closed-won and closed-lost stages from Teamgate map to Pipedrive's open and lost/dropped stage states.

Teamgate custom fields on People, Companies, and Deals map to Pipedrive custom fields of matching type (text, number, date, dropdown, checkbox). We flag any Teamgate custom fields exceeding Pipedrive's per-tier limit: Essential (30 total), Advanced (100 total), Professional (1,000 total). Customers on Essential or Advanced must consolidate or accept field loss before migration; we document the gap in the scoping report.

Teamgate Custom Objects have no direct Pipedrive equivalent. We flatten Teamgate custom object records into custom fields on the related standard object (typically Person, Organization, or Deal). This is a design-time decision made during scoping; the customer chooses whether to create new custom fields, link via a text reference field, or accept data consolidation. We document the flattening strategy in the mapping workbook.

Teamgate tags are flat string labels on People, Companies, and Deals. We export tags as a normalized list per record. Pipedrive stores tags as a native tag field on Person, Organization, and Deal records; we map the Teamgate tag list directly into Pipedrive's tag field.

Teamgate Activity records (calls, emails, meetings, tasks) map to Pipedrive Activity records. Activity type, timestamp, notes, and duration transfer. The related Person or Deal reference resolves at migration time using the migrated record IDs. We preserve the original Teamgate activity timestamp as the Pipedrive activity date.

Teamgate file attachments (up to the storage tier limit) are exported as binary downloads via API. We re-upload files to Pipedrive linked to the corresponding Person, Organization, or Deal. If the customer's Teamgate tier is Starter or Professional, we calculate total file size during scoping and flag when it approaches or exceeds the destination Pipedrive tier's storage allocation.

Teamgate Users map to Pipedrive Users by email match. Active and inactive status transfers. We export the full user list and resolve owner assignments on Deals, Companies, and People during import. Any Teamgate owner without a matching Pipedrive user is placed in a reconciliation queue for the customer's admin to provision before record import resumes.