Migrate from Touchpoint MX to Freshsales

Touchpoint MX Contacts map to Freshsales Contact records. Because Freshsales uses an Account-Contact hierarchy, we resolve or create a Freshsales Account for each Contact during import. If Touchpoint MX stores an organization name on the Contact, we use it as the Account name. If no organization is stored, we create a single Account named after the Contact's name and link the Contact to it. The Contact's primary email, phone, and any custom field values migrate to Freshsales Contact properties.

Journey Maps in Touchpoint MX use custom stage labels defined by the organization. We export each Journey Map as a structured stage sequence and create equivalent custom fields on the Freshsales Contact record (e.g., Journey_Stage__c, Journey_Start_Date__c, Next_Stage__c). We produce a stage mapping table for customer approval before migration to ensure Contacts land in the correct lifecycle position. This is a configuration step that precedes Contact import.

Touchpoint MX stores Email, SMS, and Voice channel status per Contact. We map these to Freshsales Contact properties: Email_Opt_In__c, SMS_Opt_In__c, and Voice_Consent__c as boolean custom fields. If Freshsales has native communication preference fields, we use those instead of custom fields to avoid unnecessary schema extension.

Touchpoint MX Satisfaction Scores are date-stamped values tied to Contacts. We map these to Freshsales Contacts using a custom field (Satisfaction_Score__c as number) and a companion date field (Score_Date__c) to preserve the collection timestamp. If the customer's Freshsales tier includes a native rating field, we use it and set Score_Date__c for historical context.

Touchpoint MX Feedback Records capture structured customer responses with date collected and related Contact. We export Feedback text, response date, and source interaction, and import these as Freshsales Notes attached to the corresponding Contact record via ContentDocumentLink. We preserve the original Feedback date as the Note CreatedDate to maintain chronological ordering in the Contact's activity timeline.

Touchpoint MX Message Templates define reusable outbound content with personalization tokens. We export Template content, subject lines, and token placeholders as a structured reference list. Freshsales Email Templates use a different token syntax and object model. We do not import templates as code; we deliver a written inventory of all active Message Templates with their content, tokens, and recommended Freshsales Email Template equivalent for the customer's admin to rebuild in Freshsales.

Touchpoint MX custom fields on Contacts (including Manager-only and Attendee-only visibility settings) are exported with their values per Contact. We pre-create matching custom fields in Freshsales before migration. Visibility settings do not transfer; we map the most permissive read setting to avoid data suppression in Freshsales and flag any sensitive fields for the admin to configure access controls post-migration.

Touchpoint MX Users map by email and name to Freshsales User accounts. We export the full user list with role assignments and map Owner references on Contacts and Feedback Records to the corresponding Freshsales User via email lookup. If a Touchpoint MX Owner has no matching Freshsales User, we flag it for the customer's admin to provision before record import resumes.

Attachments associated with Contacts or Feedback Records in Touchpoint MX are exported as files and re-associated in Freshsales as Attachments on the Contact record. Large attachment volumes (over 1,000 files or files exceeding 25 MB) require chunked migration to avoid API timeout. We flag this in scoping if the customer's attachment volume exceeds this threshold.