Migrate your Lead Guerrilla data

Contacts are the core object in Lead Guerrilla. We extract all contact fields including name, email, phone, address, and custom properties. Lead scoring values are preserved as a custom numeric field in the destination. Contact-source attribution (which landing page or form generated the lead) is mapped to a custom property if the destination CRM does not have an native source field.

Companies are tracked as a separate object linked to Contacts. During migration we preserve the Company record and the Contact-to-Company linkage. If the destination uses an Account object instead, we merge Company data into Accounts and maintain the relationship via a custom lookup field.

Campaigns define multi-channel sequences across email, SMS, Twitter, and web notifications. We export campaign configuration including channel assignments, timing rules, and enrollment triggers. The actual send history and delivery metrics are treated as activity records. Campaign re-implementation in the destination requires manual reconstruction of the campaign logic as the workflow engine differs across platforms.

Segments group contacts based on form source, behavior, or demographic criteria. We export segment definitions including filter conditions and member counts. Segment membership is translated into a dynamic list or tag in the destination CRM where possible. Static segment members are re-imported as contact tags.

Landing pages are content assets created within Lead Guerrilla's builder. We export page metadata (title, URL slug, published status) and redirect configuration. The page HTML content itself is exported as a ZIP archive. Post-migration, we coordinate URL redirects to preserve SEO value and campaign link integrity.

Web forms are embedded tracking widgets that collect contact data. We export form field definitions, submission mappings, and redirect behavior. Form logic (field visibility conditions, required field rules) is preserved as form configuration data. Since forms are tied to Lead Guerrilla's domain, embedding them in the destination requires a rebuild of the form using the destination platform's form builder.

Lead Guerrilla's automation engine orchestrates time-based and trigger-based actions (send email after X hours, enroll in campaign on form submit, score leads on page visit). There is no documented API for exporting these rules. We cannot migrate automation logic programmatically; we document the active rules during discovery and provide a mapping guide so the customer can manually reconfigure them in the destination platform.

Lead scoring is calculated from website behavior, form submissions, and campaign interactions. We export the current numeric score per contact as a custom property. The scoring model itself (point values per action, thresholds) is documented from the admin UI during discovery and re-implemented as a ruleset in the destination CRM where supported.

Activities track contact interactions: email opens, page visits, form submissions, SMS sends, and tweet engagement. We export activity history with timestamps and event types. High-volume activity records are chunked by date range and imported as engagement logs. The destination's activity model determines whether we import as native activity records or as a custom activity log object.

Contacts and companies can be tagged in Lead Guerrilla. We export all tag assignments and reapply them as tags in the destination CRM. Tag naming conventions are preserved exactly as-is to maintain segmentation logic that depends on specific tag strings.

User accounts in Lead Guerrilla map to campaign owners and assignment recipients. We export the user list including name and email. If the destination has a separate CRM with its own user directory, owner assignment on migrated records is mapped by email matching and flagged for manual review where no match exists.