Migrate from Lead Guerrilla to HighLevel

Lead Guerrilla Contacts map directly to GoHighLevel Contacts. We extract all standard fields (name, email, phone, address) plus custom properties. Lead scoring values transfer as a numeric custom field (e.g., lead_score__c) stored on the GoHighLevel Contact. Tags assigned in Lead Guerrilla transfer as GoHighLevel Tags and are reapplied at import time. Any 1CRM cross-reference identifiers embedded in Lead Guerrilla contact records are stripped during transform — these have no GoHighLevel equivalent and would create orphaned lookups.

Lead Guerrilla Companies map to GoHighLevel Locations. The Company record name, address, domain, and custom properties transfer. GoHighLevel Locations are available from the Starter plan and support custom fields. If the customer uses GoHighLevel's Agency settings with sub-accounts, we assign each migrated Company to the appropriate sub-account Location based on owner or segment metadata in Lead Guerrilla.

Lead Guerrilla Campaigns (multi-channel sequences across email, SMS, Twitter, and web notifications) do not have a single GoHighLevel equivalent. We map each Lead Guerrilla Campaign to a GoHighLevel Opportunity record with the campaign name as the Opportunity name and campaign enrollment history stored as a custom text field (enrollment_history__c) listing enrolled dates and campaign names. Campaign tags migrate as GoHighLevel Tags applied to the related Contact records to preserve segmentation context.

Lead Guerrilla Segments define dynamic contact groups based on form source, behavior, or demographic criteria. GoHighLevel uses Smart Lists for dynamic filtering and Tags for static membership. We export segment definitions including filter conditions and member counts, then deliver a GoHighLevel Smart List build guide keyed to the original segment logic. Members are also tagged in bulk during migration so the customer has both the dynamic Smart List and a static tag backup.

Lead score values per contact migrate as a GoHighLevel Contact custom field. The scoring model itself (point values assigned per behavior, score thresholds that trigger enrollment) is catalogued as a written reimplementation guide for the customer's marketing team to rebuild in GoHighLevel's Workflow builder using trigger-based actions and tag conditions.

Lead Guerrilla Activity records (email opens, page visits, form submissions, SMS sends, tweet engagement) migrate as GoHighLevel Contact Activity entries. High-volume activity records (over 100 per contact) are aggregated into a summary custom field to avoid inflating the GoHighLevel contact record with thousands of individual timestamp entries. The customer chooses the aggregation granularity during scoping.

Lead Guerrilla Tags assigned to Contacts and Companies migrate to GoHighLevel Tags. Tag naming conventions are preserved exactly as-is to maintain segment continuity. Tags serve as the primary mechanism for preserving Lead Guerrilla segment membership in GoHighLevel because Smart Lists provide dynamic filtering but tags persist on the record for direct use in Workflow triggers.

Lead Guerrilla User accounts map to GoHighLevel Users. We extract the user list (name, email, role assignment) from Lead Guerrilla and reconcile against GoHighLevel Users by email match. Any Lead Guerrilla Owner without a matching GoHighLevel User goes to a reconciliation queue for the customer's admin to provision before record import begins.

Lead Guerrilla Landing Pages cannot be exported as portable HTML or schema files. We export page metadata (title, URL slug, published status, redirect configuration) and deliver a GoHighLevel Funnel page rebuild inventory. The customer's marketing team rebuilds each page in GoHighLevel's drag-and-drop funnel builder guided by the inventory document. This is a content rebuild, not an automated migration.

Lead Guerrilla Web Forms (embedded tracking widgets with field definitions, submission mappings, and redirect behavior) have no export path for form logic or embed scripts. We export form field definitions, required field settings, and redirect behavior as a written field mapping document. The customer rebuilds each form in GoHighLevel's Form builder using the mapping document as a guide. Form logic conditions are reimplemented manually as GoHighLevel Workflow triggers on form submission events.