Migrate from Touchdown to HighLevel

Touchdown Contact records map 1:1 to GoHighLevel Contact. We discover the Contact field schema during API exploration, map standard fields (email, firstname, lastname, phone) by name, and handle any custom contact properties as GoHighLevel custom fields created before import. Duplicate detection uses email as the primary key. Touchdown's personalization tokens stored as contact properties migrate as GoHighLevel contact custom fields.

Touchdown Company records map to GoHighLevel Company. Company schema is confirmed during API discovery since Touchdown's documentation does not explicitly confirm Company as a first-class object. Domain, address, and industry fields map to GoHighLevel Company fields by name. We create GoHighLevel Company records before Contact import so that the contact-company relationship is resolved at insert time.

Touchdown segment definitions are discovered via API and translated into GoHighLevel tag assignments and contact filter logic. Each Touchdown segment becomes a set of GoHighLevel tags applied to matching contacts, plus a GoHighLevel contact filter that reproduces the segment criteria. If Touchdown segments use date-based or behavioral conditions, we document the equivalent filter configuration for the customer's admin to finalize in GoHighLevel's workflow builder.

Touchdown campaign metadata (campaign name, status, start and end dates, audience size) maps to GoHighLevel Campaign records. Campaign audience assignments are preserved as a contact list import linked to the campaign. GoHighLevel's campaign tracking and attribution features require configuration post-migration; we deliver the campaign metadata as structured records and document the setup steps for the admin.

Touchdown email template content and associated merge fields export as structured text. We deliver template content as a written inventory with merge field mappings documented per template. GoHighLevel's template builder requires manual recreation of the template layout and styling; we provide the source content, the merge field equivalent mapping, and a reference import of template text so the admin can rebuild efficiently in GoHighLevel's Email Template Builder.

Touchdown custom field schema is not publicly documented. We discover all custom field definitions during API exploration, determine field types (text, number, date, dropdown), and create equivalent GoHighLevel custom fields before any record import. Custom field values on Contact and Company records migrate as typed values. Field-level dependency or validation rules in Touchdown are documented for manual configuration in GoHighLevel.

Touchdown engagement data (email opens, clicks, sends, and other tracked interactions) is discovered via API during schema exploration. We map engagement records to GoHighLevel Activity Log entries attached to the corresponding Contact. Timestamp preservation is handled by setting the activity date to the original Touchdown engagement timestamp. GoHighLevel's activity timeline displays these as historical interaction records.

Touchdown user object schema is not published. We discover user records referenced on Contact, Company, and Engagement data during API exploration and map them to GoHighLevel Users by email address match. Any Touchdown owner without a matching GoHighLevel User goes to a reconciliation queue for the customer's admin to provision before record import continues.