Migrate from Touchpoint MX to HighLevel

Touchpoint MX Contacts map to GoHighLevel Contacts with standard fields (name, email, phone) preserved. Any custom field values set on the Contact record migrate to GoHighLevel Custom Fields on the Contact object. We extract all active custom fields during scoping, map their values per Contact, and handle the visibility permission by mapping to the most permissive GoHighLevel read setting. Email addresses serve as the dedupe key for import.

Journey Maps in Touchpoint MX define custom stage taxonomy per organization. GoHighLevel has no native journey mapping concept. We flatten each Journey Map by extracting stage labels and contact assignments, then map these to GoHighLevel Tags (one per stage label) applied to the Contact record. We also map the current stage to GoHighLevel's Lifecycle Stage property if the customer uses it, or to a custom Contact field journey_stage__c. A stage mapping table is produced for customer approval before migration to prevent Contacts landing in the wrong lifecycle bucket.

Touchpoint MX supports Email, SMS, and Voice channels assigned per Contact. We preserve which channels are active for each Contact by applying GoHighLevel Tags (e.g., channel_email, channel_sms, channel_voice) on the Contact record. The customer can use these tags in GoHighLevel workflows to trigger channel-specific automations post-migration.

Touchpoint MX satisfaction ratings tied to Contacts migrate to a GoHighLevel Custom Field on the Contact record. We create a numeric or rating-type custom field (e.g., satisfaction_score) and import values with timestamps. If Touchpoint MX stores multiple satisfaction scores over time, we append them as comma-separated values or create a time-series note, depending on the customer's reporting needs.

Touchpoint MX Feedback Records are structured entries with full feedback text, date collected, and related Contact. We export Feedback text and timestamps and import them as GoHighLevel Notes attached to the relevant Contact record. Date-stamped notes preserve the collection timeline for reporting and follow-up purposes.

Touchpoint MX Message Templates define reusable outbound content with subject lines and personalization tokens. We export Template content and subject lines as a documented reference file (CSV/JSON) rather than importing them as GoHighLevel Email Templates directly, because GoHighLevel's template builder uses its own merge field syntax and drag-and-drop editor that requires manual reconstruction. We deliver the exported template content as a handoff document for the customer's admin to rebuild in GoHighLevel.

Touchpoint MX User accounts are mapped by email and name to GoHighLevel Users. Owner assignments on Contacts and Journey Records migrate as GoHighLevel Contact assignments. If a Touchpoint MX User has no corresponding GoHighLevel User at migration time, we flag the unmapped owner in a reconciliation report for the customer to provision before record import resumes.

Attachments associated with Contacts or Feedback Records in Touchpoint MX are exported as files and re-associated in GoHighLevel as Contact Attachments. Large attachment volumes require chunked migration to avoid timeout. We flag any attachment exceeding GoHighLevel's size limits during scoping so the customer can decide whether to compress, link externally, or skip.

Touchpoint MX custom fields on Contacts include Manager/Attendee/Everyone visibility settings. We detect all active custom fields during scoping, extract their values per Contact, and map to GoHighLevel Custom Fields with the appropriate field type. GoHighLevel does not enforce field-level visibility at the same granularity, so we map to the most permissive read setting to avoid data suppression in the destination.