Migrate from Glaze CRM to HighLevel

Glaze CRM Contact records map directly to GoHighLevel Contact. Standard fields (name, email, phone, address) migrate 1:1. Any Glaze CRM custom properties on Contact require manual field mapping against the customer-provided schema. GoHighLevel does not have a separate Contact type; all contact records regardless of qualification status live as Contacts.

Glaze CRM Lead records map to GoHighLevel Contact with the original lead status preserved in a custom field for audit. GoHighLevel does not maintain a separate Lead object; all unqualified prospects land in the unified Contact model. We set a custom field (e.g., original_lead_status__c) to carry the Glaze CRM lead source, lead stage, and any scoring data.

Glaze CRM Company records hold business name, address, industry, and related contact associations. GoHighLevel does not have a native Company or Account object; the company name is stored as a text field on the Contact record. We map the Glaze CRM Company name to the GoHighLevel Contact Company field and preserve industry and address data in custom fields on the primary Contact.

Glaze CRM Deal records map to GoHighLevel Opportunities. Deal name, amount, stage, owner, and associated contact link migrate directly. Pipeline stages are configured in GoHighLevel before Deal migration; we document the existing Glaze CRM pipeline stages from the customer's schema and replicate them as GoHighLevel pipeline stages.

Glaze CRM pipeline configurations are organizational-level settings that must be replicated in GoHighLevel before Deals migrate. We capture the pipeline name, stage names, stage order, and probability percentages from Glaze CRM and build the equivalent GoHighLevel Pipeline with matching stage values. Pipeline configuration is documented as a written deliverable for the customer to implement or validate.

Glaze CRM Tasks (subject, due date, assignee, status, linked entity) map to GoHighLevel Tasks. Completed versus open task flags preserve. Task associations to Contacts, Deals, or Companies remap using GoHighLevel's task linking model. GoHighLevel tasks support linking to multiple object types (Contacts, Opportunities, Companies, etc.) which may require reconfiguration if Glaze CRM tasks are singly linked.

Glaze CRM Users (team members assigned as deal owners or task assignees) map to GoHighLevel Users by email address match. We resolve inactive Glaze CRM Users by archiving or deactivating them in GoHighLevel if they have no active assignments. User provisioning in GoHighLevel requires the customer to invite team members directly during migration setup.

Glaze CRM Tags stored as flat string arrays on Contacts, Deals, or Companies map to GoHighLevel Tags. Tags migrate as text values and are reapplied to the corresponding Contact or Opportunity records in GoHighLevel. Multi-select tag fields require flattening if the destination does not support array-type tag storage.

Glaze CRM custom fields on Contacts, Companies, and Deals require schema inference from a customer-provided sample record export before migration. We request a full field inventory from the customer during scoping, infer field types (text, dropdown, date, number, multi-select) from sample data, and build GoHighLevel custom fields to match. Multi-select fields from Glaze CRM require special handling as GoHighLevel may use tag arrays or custom multi-select picklist fields.