Migrate from MetroLeads to HighLevel

MetroLeads Leads map directly to GoHighLevel Contacts. The Lead name, embedded phones (with type metadata), embedded emails (with type), source_tags, lead_fields (custom properties), assigned_to user reference, and lead_creation_time all migrate as Contact fields. We resolve the MetroLeads assigned_to user to a GoHighLevel Team Member by email match. Merge-pending Lead pairs are resolved during scoping before migration so only one Contact is created per pair.

MetroLeads Companies serve as parent containers for Leads via /companies/<company_uuid>/leads/. We export Company records and map them to GoHighLevel Locations, which serve as the organizational grouping structure. Company-level custom fields migrate to Location custom fields. Each Lead's association to its MetroLeads Company is preserved as a GoHighLevel Location assignment on the Contact.

MetroLeads Events track engagement history tied to Leads. Event type, timestamp, and event details migrate to GoHighLevel Tasks (for call and email events) or Notes (for logged meeting and interaction records). We preserve event_to_lead associations by resolving the MetroLeads lead_uuid to the migrated GoHighLevel Contact ID at migration time.

MetroLeads Intellisearch is a scoring and saved-search layer built on top of Lead data. The scoring logic and saved search definitions do not map 1:1 to standard GoHighLevel objects. We export the raw Intellisearch configuration JSON and either create a GoHighLevel Custom Object to hold the scoring criteria, or map the output to a GoHighLevel Tag set for segmentation. The customer chooses the strategy during scoping.

MetroLeads Advanced Data Modules are tenant-specific data structures extending the base schema with field definitions that vary per organization. We export the module schema alongside records and create equivalent GoHighLevel Custom Objects. Each module's fields are pre-created in GoHighLevel with matching field types before any record import so that the data lands in typed fields rather than generic JSON blobs.

MetroLeads User records (id, name, role) map to GoHighLevel Team Members. We export all User records and preserve assigned_to and user_assigned_to references on Leads and Events so that the migration resolves to the correct GoHighLevel Team Member by email. Any MetroLeads User without a matching GoHighLevel user goes to a reconciliation queue for the customer to provision before import continues.

MetroLeads source_tags are string arrays on Lead records indicating disposition (e.g. disposition_answered). We export the raw tag strings and map them to GoHighLevel Tags, which are applied to the migrated Contact. Tags serve as the primary segmentation mechanism in GoHighLevel and map naturally from MetroLeads source_tags.

MetroLeads Lead state is a tenant-configured string field (e.g. contacted, new, qualified) with values that vary by MetroLeads instance. We extract all unique state values during the export scan, present them to the customer for GoHighLevel mapping, and create a custom Contact field (e.g. original_state__c) to preserve the MetroLeads value. State is also applied as a Tag so contacts can be segmented by their original MetroLeads lifecycle stage in GoHighLevel reporting.