Migrate from Lead Guerrilla to Salesforce Sales Cloud

Lead Guerrilla Contacts with a company association and high lead score (above the customer's defined MQL threshold) map to Salesforce Contact attached to an Account. Contacts with low scores or no company association map to Salesforce Lead. The split threshold is defined during scoping using Lead Guerrilla's lead score property and any segment membership data. The original Lead Guerrilla lead score migrates as a custom numeric field (lg_lead_score__c) on both Lead and Contact for rep prioritization and reporting audit.

Lead Guerrilla Company records map directly to Salesforce Account. The company name becomes Account Name, and the website field maps from Lead Guerrilla's company URL. We resolve the Company-to-Contact linkage during import by matching on Account Name or by using a custom external ID field on Account if the customer has a consistent company identifier in Lead Guerrilla. If the customer is simultaneously migrating from 1CRM, we coordinate the Account import to avoid duplicate Account creation from both Lead Guerrilla Companies and 1CRM Accounts.

Lead Guerrilla Campaigns (multi-channel sequences across email, SMS, Twitter, and web notifications) map to Salesforce Campaign records. Campaign configuration including channel assignments, timing rules, and enrollment triggers are preserved in custom fields on the Campaign object (lg_channel__c, lg_trigger_type__c) so the marketing team has a reference record for rebuild. Active enrollment status per Contact migrates as Salesforce Campaign Member records with Member Status mapped from Lead Guerrilla enrollment state.

Lead Guerrilla Segments group contacts based on form source, behavior, or demographic criteria. Segment definitions (filter conditions and member counts) are preserved as Campaign Description text and as a static list in Salesforce Campaign. If the destination org uses Salesforce Campaigns with Campaign Member statuses, we map each Segment to a unique Campaign Member Status value so the marketing team can rebuild dynamic segments in Salesforce Flow or Marketing Cloud Account Engagement (Pardot) post-migration.

Lead Guerrilla Landing Pages cannot be exported as portable HTML or schema files. We export page metadata (title, URL slug, published status) and redirect configuration, then deliver a page-by-page inventory with field-level mapping to guide the rebuild in Salesforce Experience Cloud, HubSpot, or another landing page builder. The actual page rendering code and form embed scripts require manual rebuild; this is not an automated migration artifact.

Lead Guerrilla web forms are embedded tracking widgets with form logic (field visibility conditions, required field rules, redirect behavior) that cannot be exported as portable schema. We export form field definitions and submission mappings as a field-level inventory document. The customer rebuilds forms using Salesforce Web-to-Lead, Salesforce Forms in Experience Cloud, or a third-party form tool. We document the redirect URL rules so that existing form URLs can be preserved via URL redirect configuration in Salesforce.

Lead Guerrilla lead scores calculated from website behavior, form submissions, and campaign interactions are preserved as a custom numeric field (lg_lead_score__c) on both Lead and Contact. The scoring model itself (point values per action, score thresholds for MQL) is documented in the automation rebuild playbook for the marketing team to reimplement in Salesforce Flow or Pardot scoring rules.

Lead Guerrilla activity history tracks email opens, page visits, form submissions, SMS sends, and tweet engagement with timestamps and event types. We export activity records and map them to Salesforce Task (for calls, tasks, and form submissions), Event (for meetings if scheduled), and custom Activity Log records (for behavioral events like email opens and page visits that have no native Salesforce equivalent). High-volume activity records (over 100,000) are chunked and loaded via Salesforce Bulk API 2.0 with parent-record resolution on WhoId and WhatId.

Lead Guerrilla tags on Contacts and Companies migrate to Salesforce custom multi-select picklist fields (lg_tags__c) on Lead and Contact. Tag naming conventions are preserved exactly as-is to maintain segment continuity. If the customer uses tags for content classification rather than contact segmentation, we map them to Salesforce Topics with TopicAssignment records.

Lead Guerrilla user accounts (campaign owners and assignment recipients) map to Salesforce User records. We extract the user list including name and email. Owner resolution happens by email match against the Salesforce destination org's User table. Any Lead Guerrilla Owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before Contact and Lead import begins.

Lead Guerrilla automation logic (time-based triggers, enrollment conditions, score adjustments, campaign enrollment actions) lives entirely inside the Lead Guerrilla workflow engine with no documented export path. We cannot migrate these rules automatically. During discovery we catalog every active automation via screenshots and configuration notes taken from the admin UI, then deliver a detailed rebuild playbook mapping each rule to a Salesforce Flow equivalent and a Pardot Engagement Studio step if the customer licenses Marketing Cloud Account Engagement.

Contact enrollment status in Lead Guerrilla Campaigns (enrolled, completed, unsubscribed, bounced) maps to Salesforce Campaign Member with a Member Status value that corresponds to the Lead Guerrilla enrollment state. We preserve the enrollment date and any campaign-specific interaction scores as custom fields on Campaign Member (lg_enrolled_date__c, lg_interaction_score__c). This allows the customer's sales team to see which campaigns a Lead or Contact has been exposed to without rebuilding the entire campaign logic.