Migrate from Touchdown to Pipedrive

Touchdown Contact records map 1:1 to Pipedrive Person records. Email address serves as the primary dedupe key during import. First name, last name, phone, and any custom contact properties migrate directly. Touchdown's contact property schema is discovered during the API exploration phase before extraction begins, and any non-standard field types are flagged for type conversion to Pipedrive field types.

Touchdown Company records map 1:1 to Pipedrive Organization records. Company name becomes the Organization name field, and domain information maps to the Website field where present. Organizations are created before Persons so that the Person.organization_id lookup relationship is satisfied at the moment of Person insert. This dependency order is enforced in the migration script.

Touchdown Campaign records map to Pipedrive Deals. The campaign name becomes the Deal title, and campaign status (active, archived) maps to a custom Deal field since Pipedrive Deal status is managed through pipeline stages rather than a status property. Campaign audience size is stored as a custom field for reference. We preserve the campaign context by storing the original Touchdown campaign ID in a custom field for audit.

Touchdown segments (audience definitions) do not have a direct Pipedrive equivalent because Pipedrive uses a list and filter model rather than named segment objects. We extract segment definitions as written filter criteria during API discovery, then deliver a segment translation document that maps each Touchdown segment to a Pipedrive static list (built from imported Persons) or a dynamic filter (rebuilt as Pipedrive filter conditions). The customer's admin rebuilds segments in Pipedrive using the documented definitions.

Touchdown email templates and their associated personalization tokens are exported during schema discovery. We map the template content and merge field names to Pipedrive's email template structure. Tokens that reference Touchdown-specific contact properties are flagged for manual replacement with Pipedrive equivalent field names post-migration. Template content transfers as text and HTML bodies where both formats exist.

Touchdown custom contact properties are discovered during API exploration and mapped to Pipedrive custom Person fields. Field types are converted: Touchdown text properties map to Pipedrive text fields, dropdown properties map to Pipedrive select fields, and boolean flags map to Pipedrive checkbox fields. We pre-create the custom fields in Pipedrive via the API before importing data so that values land on the correct field during insertion.

Touchdown custom company properties follow the same type-conversion logic as contact custom fields. We discover the full custom field schema during API exploration, pre-create all custom Organization fields in Pipedrive, then import company records with their associated custom field values in a second pass after Organizations exist and the custom fields are provisioned.

Touchdown email engagement records (sends, opens, clicks) are mapped to Pipedrive Activity records with type = email. The engagement timestamp maps to ActivityDate, and the engagement content maps to the Activity subject and body fields. We link each email activity to the corresponding Person record by resolving the Touchdown contact_id to the Pipedrive Person record created during the Contact migration phase.

Touchdown call engagement records migrate to Pipedrive Activity records with type = call. Call duration and disposition data map to custom Activity fields that we create in Pipedrive before import. The activity timestamp preserves the original Touchdown call date for timeline ordering.

Touchdown meeting engagement records map to Pipedrive Activity records with type = meeting. Meeting title, date, and any attendee data are transferred to the Activity subject and a custom attendees field. The activity is linked to the relevant Person or Organization record by resolving the Touchdown contact or company reference.

Touchdown task engagement records migrate to Pipedrive Activity records with type = task. Task status, priority, and due date are mapped to the equivalent Pipedrive Activity fields. Open tasks with no completed date are imported as open Activities; completed tasks are imported with their completion timestamp for historical accuracy.

Touchdown User (owner) records are mapped to Pipedrive User records by email address. We resolve owners referenced on Contact, Company, Deal, and Engagement records by matching hubspot_owner_id or the equivalent owner reference to the Pipedrive User.email address. Any Touchdown User without a matching Pipedrive User is placed in a reconciliation queue for the customer to provision before record import resumes.