Migrate your Touchpoint MX data

Contacts are the primary customer records in Touchpoint MX. We map Contacts with their standard fields (name, email, phone) and preserve any custom field values set on the contact record. Owner assignment is carried over as a user reference.

Journey Maps define the stages a customer moves through. Touchpoint MX stores stage labels and transitions. When migrating to a CRM without a native journey concept, we flatten Journey Maps into Contact properties or custom object records that represent the stage history.

Touchpoint MX supports Email, SMS, and Voice channels. We preserve which channels are active for each Contact and map Channel assignments to the destination system's communication preferences. Channel-level metadata (opt-in status) is included.

Message Templates define reusable outbound content. We export Template content, subject lines, and personalization tokens. At the destination, Templates are mapped to equivalent email/SMS template objects or preserved as content blocks in the destination system.

Touchpoint MX collects satisfaction ratings tied to Contacts and/or specific interactions. We preserve Score values with timestamps and map them to the destination CRM's native rating or NPS field, or to a custom metric field if no native equivalent exists.

Feedback Records are structured entries capturing customer responses and comments. We export the full Feedback text, date collected, and related Contact. These land in the destination system as notes, survey responses, or a dedicated Feedback object depending on the target platform.

Touchpoint MX supports custom fields on Contacts and Attendees with read/write permissions per field. We detect all active custom fields during scoping, extract their values per Contact, and map them to equivalent custom fields in the destination, applying the same visibility settings where supported.

User accounts in Touchpoint MX are mapped by email and name. We preserve the user list and map Owner assignments on Contacts and Journey Records to the corresponding user in the destination system. Role differences between platforms are flagged for manual review.

Attachments associated with Contacts or Feedback records are exported as files and re-associated in the destination. Large attachment volumes may require chunked migration to avoid timeout. We flag any attachment size limits in the destination system during scoping.

Touchpoint MX integrates with external tools via API or plug-in connectors. Integration credentials and OAuth tokens are not portable between systems. We export integration configuration as a reference document for reconfiguration in the destination platform — this is a manual step requiring re-authentication.