Migrate from Freshmarketer to HighLevel

Freshmarketer Contact records map directly to GoHighLevel Contact. The email address is the dedupe key. Standard fields (name, phone, address, lifecycle stage) map to their GoHighLevel equivalents. Custom contact fields require explicit field-level mapping during scoping because GoHighLevel supports Contact custom fields but not all Freshmarketer field types (multi-select, date-only) have direct GoHighLevel type equivalents. We flag field type mismatches and propose picklist normalization or text fallback before migration begins.

Freshmarketer Company records map to GoHighLevel Company. The org_contact_id relationship is preserved as linkedContacts in GoHighLevel. Company name, domain, industry, and address fields map directly. We create the Company in GoHighLevel before importing Contacts so that the linkedCompanyId lookup is satisfied at the moment of Contact insert. Custom company fields map to GoHighLevel Contact custom fields (not Company custom fields, since GoHighLevel's Company object has fewer customization options than its Contact object).

Freshmarketer Deals map to GoHighLevel Opportunities in the specified Pipeline. Pipeline stage names migrate as GoHighLevel stage names verbatim. Deal owner maps to the GoHighLevel user matched by email. Custom deal fields map to Opportunity custom fields in GoHighLevel. The GoHighLevel Pipeline must be pre-created with the matching stage structure before migration; we configure this during the schema design phase.

Freshmarketer activity records (email logs, sales activities, calls, notes) migrate to GoHighLevel Activity log entries linked to the Contact record. Each activity type maps to its GoHighLevel Activity type: Email to Email Log, Call to Call Log, Note to Note. Timestamp ordering is preserved. Activities without a matching GoHighLevel Contact (due to email dedupe merging) are linked to the surviving Contact record and flagged in the reconciliation report.

Freshmarketer Segments are audience filters built from contact property conditions. GoHighLevel does not have a native Segment equivalent; audience filtering uses Smart Lists (saved filter views) and Tags. We map segment criteria to a corresponding combination of GoHighLevel tags and Smart List filter conditions. Segments with simple single-condition criteria map cleanly to Smart Lists. Complex multi-condition segments may require a tag-based approach with multiple tags applied per contact. The customer chooses the mapping strategy during scoping.

Freshmarketer custom fields on contacts, companies, and deals map to GoHighLevel Contact Custom Fields or Opportunity Custom Fields depending on which object the field lives on in Freshmarketer. Field type differences (dropdown vs. text, multi-select vs. checkbox, date format) are resolved during field-level mapping. GoHighLevel uses merge-field syntax {{custom_field.api_name}} in templates and workflows, so API names are preserved from Freshmarketer where possible to minimize rewiring of downstream references.

Freshmarketer's Marketing Contacts is a billing concept — contacts targeted in email, SMS, or WhatsApp campaigns. GoHighLevel has no equivalent billing concept. We flag which Freshmarketer contacts were enrolled in active campaigns at migration time and preserve this as a custom field (e.g., was_marketing_contact__c) on the GoHighLevel Contact record. This lets the customer understand their post-migration billing exposure at the destination and re-enroll contacts in GoHighLevel campaigns if needed.

Freshmarketer Journeys are marketing automation workflows that cannot be exported as executable logic via API. We do not migrate Journeys as code. Instead, we audit every active Journey at migration time, document its trigger (event-based or time-based), conditions, actions (email send, SMS, task create, stage change), and the list of enrolled contacts at cutover. This Journey inventory is delivered as a structured document so the customer's admin can rebuild each Journey in GoHighLevel's Workflow Builder. The enrolled-contact state at cutover is preserved so Journeys can be resumed from the right point rather than restarted.

Freshmarketer user accounts (name, email, role, team assignment) map to GoHighLevel Team Members. Owner references on Contacts, Deals, and Activities are remapped by email match. Any Freshmarketer Owner without a matching GoHighLevel Team Member is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Freshmarketer users are mapped as inactive Team Members if their historical assignments need to be preserved.

Freshmarketer tags (labels applied to contacts, companies, and deals) migrate as GoHighLevel Tags. Tags are a flat string list in both platforms. We apply tags to the corresponding GoHighLevel record (Contact, Company, or Opportunity) at migration time. No tag hierarchy exists in Freshmarketer, so there is no hierarchical structure to translate.