Migrate from Touchpoint MX to Salesforce Sales Cloud

Touchpoint MX Contacts with early-stage Journey Map labels (e.g., Awareness, Interest) map to Salesforce Lead. Contacts with late-stage labels (e.g., Consideration, Decision, Customer) map to Salesforce Contact attached to an Account. We compute the split using the Contact's primary Journey Map stage at migration time, preserve the original Touchpoint MX stage label in a custom field touchpoint_stage__c on both Lead and Contact, and set the Salesforce Lifecycle Stage to match the nearest equivalent.

Touchpoint MX Journey Maps define customer progression through custom stages. Salesforce has no native Journey Map object, so we flatten each Journey Map into contact-level custom fields (e.g., touchpoint_current_stage__c, touchpoint_entered_customer__c) and create a related list of Activity records capturing stage transitions with timestamps. Stage labels from Touchpoint MX are mapped to Salesforce Lifecycle Stage values using a customer-approved mapping table before any Contact import begins.

Touchpoint MX Satisfaction Scores tied to Contacts migrate to a custom Number or Rating field on Salesforce Contact. Score values and collection timestamps are preserved. Where Satisfaction Scores relate to a specific interaction rather than the Contact overall, we attach a Task record with the score as a custom field to maintain the interaction-level context in the destination.

Touchpoint MX Feedback Records migrate to Salesforce Note objects linked via ContentDocumentLink to the parent Contact or Account. Full Feedback text, collection date, and any associated Channel (Email, SMS, Voice) migrate as Note fields. If the Feedback Record references a specific Journey Map stage, we include the stage label in the Note title for traceability.

Touchpoint MX Channel assignments (Email, SMS, Voice) for each Contact migrate to a Salesforce custom multi-select picklist field (e.g., touchpoint_channels__c). Email opt-in and opt-out status from Touchpoint MX migrate to the standard HasOptedOutOfEmail field. Channel-level preferences do not map to any native Salesforce object because the platform does not have a per-channel subscription preference model.

Touchpoint MX Message Templates (content, subject lines, personalization tokens) are exported as a reference document for the customer's admin to rebuild in Salesforce as EmailTemplates or Salesforce Content. We do not migrate template logic as executable code because Salesforce and Touchpoint MX use different templating languages and personalization token syntaxes.

Touchpoint MX custom fields on Contacts are detected during scoping, extracted with their values per Contact, and mapped to Salesforce custom Contact fields of equivalent type (Text, Number, Date, Picklist, Checkbox). Touchpoint MX Manager-only and Attendee-only visibility settings have no Salesforce analog; we map to the most permissive read access available in the destination profile to avoid data suppression.

Touchpoint MX Users map to Salesforce User records by email match. We export the full user list with name, email, and role assignment. Owner assignments on Contacts and Journey Records are resolved by matching the Touchpoint MX user email to the Salesforce User email. Any Touchpoint MX user without a matching Salesforce User is placed in a reconciliation queue for the customer's admin to provision before record import proceeds.

Files attached to Touchpoint MX Contacts or Feedback Records are exported and uploaded to Salesforce as ContentDocument records with ContentVersion links to the parent Contact or Account. Large attachment volumes may require chunked migration to avoid API timeout; we flag this in the scoping report and recommend Salesforce Content Delivery or Experience Cloud if file delivery at scale is a post-migration requirement.

If Touchpoint MX includes Company-level records (available in some configurations), these map to Salesforce Account. The Company domain becomes the Account Website field and is used as a dedupe key. We create the Account before Contact import so that AccountId is resolved at the moment of Contact insert.

Touchpoint MX products referenced in Message Templates or Satisfaction Surveys map to Salesforce Product2 records with Standard Price Book entries. We only migrate this object if product records exist in the source; most Touchpoint MX deployments do not store a product catalog separate from the messaging layer.

Touchpoint MX integrations (connected apps, OAuth tokens, webhook endpoints) are bound to the source account and cannot be exported or transferred. We export a JSON-formatted list of all active integrations with their configuration parameters as a reference document. The customer's admin uses this checklist to re-establish each integration in Salesforce manually. This is documented work, not migrated data.