Migrate from Marketing 360 to HighLevel

Marketing 360 Contact records map to GoHighLevel Contact. The API exposes id, firstName, lastName, email, phone, contactName, customerId, and organizationId. We map these to GoHighLevel's standard contact fields (firstName, lastName, email, phone, company name) and resolve any organizationId reference to a GoHighLevel Company record. Custom field values migrate into GoHighLevel custom fields created at the destination before import.

Marketing 360 exposes a dedicated Custom Fields API with id-value pairs per contact. GoHighLevel provides a Custom Fields interface under Settings where fields are created per object (Contact or Opportunity). We extract the full custom field taxonomy from Marketing 360, create equivalent fields in GoHighLevel with matching types (Short Text, Long Text, Dropdown, Date Picker, Phone, Email, Radio Select, Checkbox Group, URL), and map values during import. Note: GoHighLevel custom fields are object-scoped and cannot be switched between objects after creation.

Marketing 360 contacts carry tag arrays with id and tag name. We extract the full tag taxonomy and apply tag memberships to migrated contacts in GoHighLevel. GoHighLevel supports tags on contacts and uses a flat tag list rather than Marketing 360's id-name pair structure. The tag taxonomy is preserved in full; duplicate tag names are deduplicated at import. GoHighLevel's import CSV supports tag assignment via a dedicated tag column.

Marketing 360 stores assignees as username, fullName, and email nested under contact records. We map assignee references to GoHighLevel User records by email match. GoHighLevel's user model includes name, email, and role permissions. Where no matching User exists in the destination, we assign to a migration service account and flag the contact for admin reassignment post-migration.

Marketing 360 uses arbitrary name-id pairs for contact Statuses and Types. We extract the full taxonomy from the API and map these to GoHighLevel custom fields, typically as dropdown or radio-select type fields with the original Marketing 360 values as options. The customer selects the field type during scoping. If GoHighLevel does not have an equivalent lifecycle-stage analog, the taxonomy is preserved as a labeled custom field rather than a native property.

The UXi export tool produces XML containing Posts, Pages, Testimonials, and Media content. We extract text content, categories, tags, and media references from the XML. GoHighLevel's site and funnel builder does not import UXi XML directly; content is manually pasted or rebuilt using GoHighLevel's editor. This is a manual rebuild workstream, not an automated migration. We flag this explicitly in scoping and deliver the extracted content as a structured CSV with media URLs for reference.

Testimonials export from UXi XML as structured records with author name, content, and media URLs. We extract this data and prepare it for GoHighLevel's testimonials or reputation management module. Content migrates as structured text; author attribution migrates as contact references where possible. Media files require separate download and re-upload to GoHighLevel's media library.

Marketing 360 automation and journey logic (trigger conditions, time delays, branch rules, subscriber entry points) are stored in the application layer and not exposed via the public REST API. We cannot migrate automations automatically. During migration scoping we document all active journeys from the Marketing 360 UI and provide a manual rebuild checklist mapped to equivalent GoHighLevel Workflow features (trigger types, conditions, actions, delays). The customer's admin rebuilds workflows in GoHighLevel's visual Workflow builder post-migration.

Email subscriber data and segment membership extract from the Marketing 360 CRM contact export. GoHighLevel does not have a separate Email Subscriber object; contacts carry email, phone, and tag associations. We import contacts with segment membership preserved as tags (e.g., original list names become GoHighLevel tags). Automated journey triggers tied to segment entry require review and manual reconfiguration in GoHighLevel Workflows.