Migrate from UPNIFY CRM to HighLevel

UPNIFY Clients map to GoHighLevel Contacts as the primary contact object. Standard fields (name, company email, mobile phone) transfer 1:1. Custom client fields map as key-value pairs into GoHighLevel Contact custom fields. Mobile phone from UPNIFY becomes the Contact phone field; WhatsApp number if distinct from mobile is stored in a custom field. We sequence Contact import after Location import to satisfy any account-linking fields.

UPNIFY Companies map to GoHighLevel Locations, which serve as the B2B account object. Company name becomes Location name, and any parent-child company hierarchy in UPNIFY maps to GoHighLevel's location relationship fields. We import Locations before Contacts so that any Company-Contact linkage in UPNIFY resolves to the correct LocationId in GoHighLevel.

UPNIFY Opportunities map to GoHighLevel Opportunities with pipeline stages remapped via a customer-supplied stage matrix. Closed-won and closed-lost status transfer directly. UPNIFY stage names (customizable per account) map to GoHighLevel pipeline stages, and the Opportunity amount becomes the GoHighLevel dollar value field. We resolve OwnerId by email match against GoHighLevel users before import.

UPNIFY Prospects (pre-qualified leads in a separate object from Clients) map to GoHighLevel Leads. Lifecycle stage values from UPNIFY migrate as a custom field on the Lead so that the customer's existing qualification tier is preserved. Any lead source or attribution data in UPNIFY migrates to GoHighLevel custom Lead fields.

UPNIFY Quotations carry product line items, pricing, currency, and embedded exchange-rate metadata. Multi-currency metadata is flattened into a single price field during transform (we apply the embedded exchange rate to produce a normalized value in the customer's preferred currency). The Quotation header and line items migrate as a custom object structure in GoHighLevel, since GoHighLevel does not have a native quotation object at the Starter tier. We document the custom object schema before import.

UPNIFY Products from Catalogs migrate to GoHighLevel Products with name, SKU, price, and description preserved. ProductCode maps from UPNIFY's SKU field. Stock-level data is not consistently populated in UPNIFY and is flagged as absent during scoping. We create GoHighLevel Products before importing any Quotation line items that reference them.

UPNIFY Goals track team or user-level sales targets with name, period, target value, and owner. We migrate Goals as GoHighLevel Tasks scoped to the goal owner, storing the target value in a custom task field and the period as task due date or custom date fields. Goals do not have a native GoHighLevel equivalent, so the configuration maps to a structured task pattern that the customer's admin can report against.

UPNIFY Calendar entries (tasks, reminders, appointments) map to GoHighLevel Tasks with title, status, due date, and owner assignment preserved. Completed vs. open status transfers directly. Appointment-style calendar entries with start and end times migrate as Tasks with a custom date range field since GoHighLevel's native calendar focuses on booking rather than task history.

UPNIFY Tags are applied across Clients, Companies, and Opportunities for segmentation. We export all tag assignments per object and reconstruct tag lists in GoHighLevel using GoHighLevel's Tag feature. Each unique tag from UPNIFY becomes a GoHighLevel Tag, and tag assignments are linked to the migrated Contact, Location, or Opportunity records. Tag segmentation used for marketing audience building requires a separate rebuild in GoHighLevel Workflows.

UPNIFY Custom Fields on Clients, Companies, and Opportunities (types: text, number, date, dropdown) map to GoHighLevel Contact, Location, and Opportunity custom fields. We create the destination custom field schema before data import, preserving field type where possible. Text maps to text, number to number, date to date. Dropdown values in UPNIFY map to GoHighLevel option sets with values preserved.