Migrate from Touchpoint MX to Zoho CRM

Touchpoint MX Contacts with no assigned Journey Map stage or unassigned owner map to Zoho CRM Lead. Contacts with an established Journey Map stage (active customer, evangelist, or post-sale stage) map to Zoho CRM Contact attached to a Zoho Account. We preserve all standard Contact fields (name, email, phone) and map custom Contact properties from Touchpoint MX to Zoho CRM custom fields on the appropriate module. Owner assignment resolves by email match to Zoho Users.

Touchpoint MX Journey Maps define a custom stage taxonomy (e.g., Awareness, Consideration, Purchase, Retention) that does not map directly to any Zoho CRM native object. We create a custom Journey_Map__c module in Zoho CRM with fields for Stage_Name__c, Transition_Date__c, and Source_Contact_Id__c (lookup to Contact). Alternatively, if the customer prefers simplicity, we store the active stage label as a Contact field journey_stage__c. The remapping table is produced during scoping for customer approval before data lands.

Touchpoint MX Channel assignments (Email active, SMS active, Voice active) map to Zoho CRM Contact fields channel_email__c, channel_sms__c, and channel_voice__c as checkbox fields. If the destination Zoho edition includes Zoho CRM's Multi-channel Support feature, these map to the standard Communication Type picklist.

Touchpoint MX Satisfaction Scores tied to Contacts map to Zoho CRM Contact Rating (1-5 stars, standard field) or a custom field satisfaction_score__c if the source score uses a non-standard scale (e.g., NPS 0-10). Score timestamps migrate as satisfaction_recorded_date__c for historical reference.

Touchpoint MX Feedback Records (structured entries with text, date collected, and related Contact) map to Zoho CRM Notes attached via ContentDocumentLink to the migrated Contact or Lead record. We preserve the feedback text as Note Body, the date collected as Note Title with date prefix, and the source Contact reference via the linked record ID.

Touchpoint MX custom fields on Contacts use permission-gated visibility settings (Manager-only, Attendee-only, Everyone). We export all custom field values regardless of visibility during extraction. Custom field data types in Touchpoint MX map to equivalent Zoho CRM field types: text to Single-Line, multi-value to Multi-Select, date to Date, number to Numeric. We map the most permissive visibility (Everyone-equivalent) in Zoho CRM to avoid data suppression post-migration.

Touchpoint MX Message Templates (email subject, body, personalization tokens) export as content records. We map Template content to Zoho CRM Email Templates or SMS Templates depending on channel. Personalization tokens require remapping to Zoho CRM's $field.name syntax. Message Templates do not migrate as live automation; they are exported as a reference document for manual re-creation in Zoho CRM.

Touchpoint MX User accounts are resolved by email match to Zoho CRM User records. We export the full user list and map Owner assignments on Contacts, Journey Maps, and Feedback records to the corresponding Zoho User. Any Touchpoint MX user without a matching Zoho User goes to a reconciliation queue for the customer's admin to provision before record import proceeds.

Attachments associated with Touchpoint MX Contacts or Feedback records are exported as files and re-associated in Zoho CRM under the relevant Contact or Note. Attachment migration respects Zoho's file size constraints: individual files must fall within the import tool's limits. Large attachment volumes require chunked migration to avoid timeout; we flag this during scoping if attachment volume exceeds 1 GB.

Touchpoint MX integrations (connected apps, OAuth tokens, webhook endpoints) are bound to the source account and cannot be exported or transferred. We export a written inventory of every active integration with connection type, authentication method, and destination endpoint so the customer's admin can re-establish them in Zoho CRM manually. This is a configuration step, not a data migration step, and is scoped separately.