Migrate from Lead Guerrilla to Microsoft Dynamics 365 Sales

Lead Guerrilla stores all prospects and customers in a single Contact object with no separate Lead concept. Microsoft Dynamics 365 Sales separates unqualified prospects into Lead records and qualified buyers into Contact records attached to Account records. We define the split rule during scoping based on the customer's lead score thresholds and campaign enrollment status. Contacts with a lead score above the customer's qualification threshold map to Contact records; below the threshold map to Lead records. The original Lead Guerrilla lead score migrates as a custom numeric field lg_original_score__c on both Lead and Contact for audit trail and future segmentation.

Lead Guerrilla Companies map directly to Microsoft Dynamics 365 Sales Account records. The Company name becomes Account Name, the domain field maps to Website, and any address fields map to the address composite on Account. Account is inserted before Contact import so that the parent AccountId lookup is satisfied at Contact insert time. We use Company name as the dedupe key for duplicate detection during import.

Lead Guerrilla Campaigns (multi-channel sequences across email, SMS, Twitter, and web notifications) map to Microsoft Dynamics 365 Sales Campaign. The campaign channel configuration, timing rules, and enrollment triggers are captured as campaign configuration notes. Dynamics 365 Campaign tracks member responses as Campaign Responses. We preserve campaign enrollment history as Campaign Member records linked to the corresponding Contact or Lead.

Lead Guerrilla Segments (behavior-based or demographic contact groupings) have no direct Dynamics 365 equivalent. We export segment definitions including filter conditions and member counts, then translate them into Dynamics 365 Dynamic Distribution Groups (Exchange-based) or Power Platform Security Groups with dynamic membership rules. The customer chooses the distribution model during scoping. Segment membership is not migrated as a static group because contacts change state over time.

Lead Guerrilla calculates a numeric lead score from website behavior, form submissions, and campaign interactions. We export the current score value per Contact as a custom integer field lg_lead_score__c on both Lead and Contact in Dynamics 365. The scoring model itself (point values per action, weightings, thresholds) is not portable. We document the original scoring model in the automation rebuild playbook so the customer's marketing team can implement an equivalent scoring logic in Power Automate or a third-party scoring ISV.

Lead Guerrilla Activities track email opens, page visits, form submissions, SMS sends, and tweet engagement with timestamps and event types. These map to Dynamics 365 Activity (Task), EmailMessage (for email open/click events stored as email tracking records), and Event (for scheduled or completed meetings). High-volume activity records are chunked for Dataverse API ingestion. We preserve the original timestamp as ActivityDate for timeline ordering.

Lead Guerrilla Tags on Contacts and Companies map to Dynamics 365 Tags (introduced in 2020 Release Wave 2 for Unified Interface) or to a custom multi-select picklist field if the destination org uses an older UI version. Tag naming conventions are preserved exactly as-is to maintain segmentation logic that depends on specific naming patterns.

Lead Guerrilla Landing Pages are content assets created in the platform's internal builder with no export path for page HTML or embed scripts. We export page metadata (title, URL slug, published status, redirect configuration) as a written inventory. The customer's web team rebuilds the pages in their target content platform (SharePoint, Power Pages, or a CMS). We provide field-level mapping between the Lead Guerrilla form fields and the replacement destination form fields so the rebuild is guided.

Lead Guerrilla Web Forms collect contact data via embedded tracking widgets. We export form field definitions, submission mappings, and redirect behavior as a written specification. Form logic (field visibility conditions, required field rules, thank-you message text) is documented for rebuild in Power Pages or Dynamics 365 Marketing. The form embed scripts are not portable and require rewrite.