Migrate from Tango CRM to Pipedrive

Tango CRM Contact records map to Pipedrive Person. Standard fields (name, email, phone, address) map directly. Email serves as the merge key during import to prevent duplicate Person records. Custom fields on Contact require explicit type-matching against Pipedrive's supported custom field types (text, number, date, dropdown, multiselect, etc.). We create any missing Pipedrive custom fields before import so that the mapping step can reference them directly.

Tango CRM Company records map to Pipedrive Organization. Organization is created before Person import to satisfy the Organization ID lookup on Person records. Domain-based matching is used as an additional dedupe signal alongside exact name matching. Industry, size, and address fields map to Pipedrive Organization standard fields. Any custom properties on Company are mapped to Pipedrive custom fields on Organization.

Tango CRM Deals map directly to Pipedrive Deals with deal name, value, expected close date, and owner preserved. The Tango CRM deal stage maps to a Pipedrive Stage value that we configure during the pipeline setup phase. Historical deal values and stage-transition timestamps are carried forward where present in the export. Closed-won and closed-lost status from Tango CRM maps to Pipedrive's Stage status values.

Tango CRM pipeline stage names are reconciled against Pipedrive Stage labels during the mapping phase. We produce a stage mapping worksheet during discovery that defines the target Pipeline, stage order, stage labels, and probability percentages for each stage in the destination Pipedrive account. Stage order is preserved independently of label names. Probability values from Tango CRM are rounded to Pipedrive's integer-based probability format and applied to each Stage configuration.

Tango CRM pipeline definitions export as configuration records describing stage count, stage order, and any automation hooks per stage. We create Pipedrive Pipelines via the Pipedrive API or settings prior to data import. Multiple Tango CRM pipelines map to multiple Pipedrive Pipelines by name match. If Tango CRM has only one pipeline, we create one Pipedrive Pipeline; the customer can add additional Pipelines post-migration in Pipedrive Settings.

Tango CRM Activity records are split by activity type during transformation. Emails become Pipedrive email Activity records with content and recipient preserved. Calls become Pipedrive call Activity records with duration and disposition. Meetings become Pipedrive meeting Activity records with attendee list and location. Tasks become Pipedrive task Activity records with due date and completion status. Each activity type is imported separately via the Pipedrive Activity API with the associated Person or Deal ID resolved at migration time.

Custom properties on Tango CRM Contacts, Companies, and Deals require explicit field-level mapping during the transformation phase. We match field names to Pipedrive custom field equivalents, create any missing Pipedrive custom fields before import, and apply type conversions where Tango CRM field types differ from Pipedrive supported types (e.g., currency fields, checkbox fields, or formatted text fields). Dropdown or multiselect custom fields in Tango CRM are mapped to Pipedrive dropdown or multiselect fields with value-level mapping documented in the mapping workbook.

Tags applied to Tango CRM Contacts, Companies, or Deals transfer as Pipedrive Label records. Multi-value tag fields are split into individual label assignments during transformation. Pipedrive maintains separate Label sets for People, Organizations, Deals, and Leads; we map source tags to the appropriate entity's label set based on the record type they were attached to in Tango CRM.

Free-text notes attached to Tango CRM Contacts, Companies, or Deals migrate as Pipedrive Note records linked to the corresponding Person, Organization, or Deal via the note's entity_id and entity_type fields. HTML-formatted notes are stripped to plain text unless the destination Pipedrive account has rich-text note support enabled. Note timestamps are preserved as Activity timestamps for timeline ordering.

Tango CRM Users and record owners are resolved by email match against the destination Pipedrive account's user roster. We extract every distinct owner email from source records during extraction and cross-reference against Pipedrive User email addresses. Users present in Pipedrive receive the migrated records as their owner. Users absent from Pipedrive are flagged in a reconciliation list for the customer's admin to provision before import resumes. Role and permission configurations are not migrated; these are set up in Pipedrive post-migration.

If Tango CRM stores product or service records linked to Deals, those records migrate to Pipedrive Product entries. Product name, code, and pricing fields map to Pipedrive Product fields. Products are created before Deal import so that the Product ID can be associated with any Deal line items during the Deal migration phase.

Closed-lost Deals from Tango CRM migrate to Pipedrive Deals with status set to lost and the loss reason field populated where available. We preserve the original Tango CRM stage label and probability at the time of closure for historical reporting consistency. Closed-lost Deals are included in the migration because the historical pipeline data is relevant for sales performance analysis in Pipedrive.

The relational structure linking Contacts to Companies and Deals to Contacts and Companies is preserved by resolving the target record's ID at migration time. We maintain a cross-reference table mapping Tango CRM record IDs to Pipedrive record IDs. When importing Deals, the resolved Organization ID and Person ID are written into Pipedrive's org_id and person_id fields on the Deal record, preserving the relationship chain in the destination CRM.