Migrate from Touchpoint MX to Microsoft Dynamics 365 Sales

Touchpoint MX Contact records map directly to Dynamics 365 Contact. Standard fields (FullName, Email, Phone, BusinessPhone, JobTitle) map to the equivalent Dynamics Contact fields. We preserve any Touchpoint MX custom field values on the Contact record as custom Contact fields in Dynamics 365, created during schema design. Owner assignment resolves by email match to a Dynamics User; unresolved owners go to a reconciliation queue for the customer's admin to provision.

Touchpoint MX Journey Maps define custom stage labels and transitions per organization. Dynamics 365 has no native Journey Map object, so we flatten the journey structure into Contact. The current stage label becomes a custom Contact field (tp_current_journey_stage__c), the complete stage history becomes a custom multi-select or text field (tp_journey_history__c), and transition timestamps become date fields. We produce a stage mapping table during scoping so the customer approves which source stage maps to which label before data lands.

Touchpoint MX Channel assignments (Email active, SMS active, Voice active) map to Dynamics 365 Contact Communication preferences or custom boolean fields (tp_email_channel__c, tp_sms_channel__c, tp_voice_channel__c). Channel delivery metadata (last sent date, channel status) preserves as custom fields on Contact if the customer requires audit trail of communication channel activity.

Touchpoint MX Satisfaction Scores tied to Contacts map to the Dynamics 365 Contact rating field (scale 1-5) or a custom decimal field (tp_satisfaction_score__c) with timestamp (tp_satisfaction_date__c). If the customer collects multiple satisfaction records per Contact, we create a custom Satisfaction Survey entity in Dynamics 365 linked to Contact via a lookup relationship.

Touchpoint MX Feedback Records (structured entries with text, date collected, and related Contact) map to Dynamics 365 Note records attached via ContentDocumentLink to the parent Contact. Feedback author, collection date, and channel source preserve as Note title prefix and custom fields. Large Feedback volumes (over 100,000 records) migrate in Bulk API batches to avoid timeout.

Touchpoint MX Message Templates (content, subject lines, personalization tokens) export as a written reference document listing Template Name, Subject, Body content, and token placeholders. Dynamics 365 Email Templates serve as the equivalent object, but template migration requires manual rebuild because the token syntax differs between platforms. We deliver the full template inventory so the customer's admin rebuilds them in Dynamics Email Template format.

Touchpoint MX custom fields on Contacts (with Manager-only, Attendee-only, or Everyone visibility) export with their values per Contact. We create equivalent custom fields in Dynamics 365 during schema design, preserving the most permissive visibility setting to avoid data suppression. Any permission-gated visibility logic is noted as a custom field description for the Dynamics admin to configure field-level security post-migration.

Touchpoint MX User accounts map by email and FullName to Dynamics 365 User records. Owner assignments on Contacts, Feedback Records, and Journey Records resolve by email match to the Dynamics User. Users without a matching Dynamics User go to a reconciliation queue for the customer's admin to provision before record import resumes.

Attachments associated with Touchpoint MX Contacts or Feedback Records export as files and re-associated in Dynamics 365. We use Dynamics 365's SharePoint integration (if configured) or attach files to the Contact record via Notes with ContentDocumentLink. Large attachment volumes require chunked migration to avoid API timeout. We flag estimated attachment volume during scoping so the customer can pre-configure SharePoint document libraries if needed.