Migrate from Touchpoint MX to Pipedrive

Touchpoint MX Contacts map directly to Pipedrive People. Standard fields (name, email, phone) map to Pipedrive's name, email_id, and phone fields. Any custom field values set on the Contact record are extracted and pre-created as Pipedrive custom fields on Person before migration. Owner assignment on the source Contact maps by email match to the Pipedrive User record. A dedupe check on email prevents duplicate People on re-migration.

Touchpoint MX Journey Maps define stages a Contact moves through. Pipedrive has no native journey concept, so we split Journey Map data across three Pipedrive objects: the stage taxonomy becomes a Pipedrive Pipeline with custom-named Stages, the Contact's current stage is stored as a custom field current_journey_stage__c on the Person record, and the full stage history (with timestamps) is appended as a Note on the Person. We produce a Journey Map stage mapping table for customer approval before any data lands, to prevent Contacts landing in the wrong pipeline stage.

Touchpoint MX tracks Email, SMS, and Voice as active channels per Contact. We map Channel assignments to a custom multi-select picklist field channel_preference__c on the Pipedrive Person record. If the customer uses channel-specific configuration in Pipedrive (such as separate phone and email fields), we align the channel assignments accordingly. This is a configuration choice made during scoping.

Touchpoint MX Message Templates define reusable outbound content. Pipedrive has no native template storage object for email or SMS. We export Template content, subject lines, and personalization tokens as structured Notes on the relevant Person or Organization records, or as a separate Note tagged with a label for the admin to migrate into Pipedrive's Email Templates or a connected tool like HubSpot Marketing if the customer retains a hybrid stack.

Touchpoint MX Satisfaction Scores map to a custom numeric field satisfaction_score__c on the Pipedrive Person record. Score values and collection timestamps are preserved. If Touchpoint MX stores multiple satisfaction records per Contact (e.g., post-interaction and periodic NPS), we append each with a timestamp in the field value or use additional custom fields to distinguish collection points. We flag this during scoping if multiple score types are present.

Touchpoint MX Feedback Records (structured entries with text, date collected, and related Contact) map to Pipedrive Notes linked to the Person record. The Note body contains the full Feedback text and a header with the collection date and source interaction type. If the Feedback was tied to a specific Deal in a CX program context, we create an Activity of type Note attached to the relevant Deal and Person.

Touchpoint MX custom fields on Contacts are extracted during scoping, and each is pre-created in Pipedrive as a custom field on Person with a matching type (text, number, date, picklist, checkbox). Touchpoint MX visibility settings (Manager-only, Attendee-only, Everyone) are exported as a metadata note and mapped to Pipedrive's field visibility settings if the destination plan supports field-level access control. We flag any fields that exceed Pipedrive's plan-based field count limits during scoping so the customer can choose which fields to prioritize.

Touchpoint MX Users are matched to Pipedrive Users by email address. Owner assignments on Contacts and Journey Records are resolved to the corresponding Pipedrive User at migration time. Any Touchpoint MX User without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before Person import resumes.

If the customer has company data in Touchpoint MX (e.g., a Company object or company name on the Contact record), we map it to Pipedrive Organization. Organization is created before Person import so that the organization_id can be resolved and attached to the Person record at insert time. If no company-level data exists in Touchpoint MX, we skip the Organization object and attach all Contacts directly as standalone Person records.

File attachments associated with Contacts or Feedback records in Touchpoint MX are exported as files and re-associated in Pipedrive using the File feature. Large attachment volumes (over 1,000 files or files over 25 MB) require chunked migration to avoid timeout. We flag this during scoping so the customer can decide whether to migrate all attachments or prioritize recent ones.