Migrate from Lead Guerrilla to HubSpot

Lead Guerrilla contacts map 1:1 to HubSpot contacts. All standard properties (name, email, phone, address) migrate directly. The contact's original create date is preserved as a custom datetime field since HubSpot's Createdate is set at import time. Custom fields unique to your Lead Guerrilla setup are also migrated as additional properties, provided they are pre-created in HubSpot.

Lead Guerrilla company records map to HubSpot companies. Domain, industry, employee count, and annual revenue fields migrate to their HubSpot equivalents. Multi-company associations per contact collapse to HubSpot's primary-company model. If your Lead Guerrilla data includes additional company-level custom fields, those are exported and recreated as custom properties in HubSpot prior to the migration.

Lead Guerrilla campaigns do not have a direct HubSpot equivalent because HubSpot separates email sequences, SMS, and social into distinct tools. We export campaign metadata (name, description, create date) as a HubSpot custom object record and map campaign enrollment to a HubSpot list membership or workflow-enrollment custom property.

Lead Guerrilla segments define contact-filter logic for audience targeting. We translate segment filter criteria into HubSpot list-builder criteria. Dynamic segments become HubSpot dynamic lists; static segments become HubSpot static lists. Segment membership history is preserved as a property on each contact.

HubSpot has no native lead-score field. We create a custom numeric property (Lead_Score__c equivalent via HubSpot property name) and migrate the Lead Guerrilla score value per contact. HubSpot's own predictive lead scoring tool must be configured separately post-migration. Your team should evaluate whether to continue using the legacy scores or adopt HubSpot's predictive model.

A Lead Guerrilla contact's enrollment in a campaign is stored as a record linking contact ID to campaign ID. We merge these into a HubSpot list membership for the corresponding campaign-list and write the enrollment date as a custom datetime property on the contact.

Lead Guerrilla tracks email send, open, and click events as activity records. These are logged to HubSpot's contact timeline as engagement events. Historical open and click counts migrate as custom number properties if HubSpot's native engagement tracking cannot backfill them.

HubSpot SMS history is tracked within the HubSpot SMS tool and does not have a portable API export. We preserve SMS send records as a JSON-formatted custom property on the contact for reference. The actual SMS threads must be re-established in HubSpot's SMS tool post-migration.

Lead Guerrilla's social-channel campaign actions (Twitter mentions, web notifications) have no HubSpot equivalent. Social engagement records from Lead Guerrilla are preserved as custom properties on the contact record. HubSpot social inbox handles future social interactions separately. If you rely on historical Twitter engagement metrics for reporting, those values remain accessible through the custom property but will not trigger HubSpot workflows.

Lead Guerrilla landing page submissions map to HubSpot form submissions. Each submission is logged on the contact timeline with the original submission date and UTM source fields preserved. Landing page configuration is exported as a rebuild reference for HubSpot native forms.

Lead Guerrilla allows custom data objects beyond contacts and companies. These map 1:1 to HubSpot custom objects. All custom field definitions are exported and recreated in HubSpot before data migration runs. N:N associations between custom objects require HubSpot junction objects.

Lead Guerrilla owner IDs are resolved by email match against HubSpot users. Unmatched owners are flagged before migration — teams either invite them to HubSpot first or assign their records to a designated fallback owner. This prevents orphan records in HubSpot.