Migrate from Lead Guerrilla to Pipedrive

Lead Guerrilla Contact records map directly to Pipedrive Person. All standard fields (name, email, phone, address) migrate as their Pipedrive equivalents. The Lead Guerrilla lead scoring value migrates as a custom numeric field lead_score__c on the Person record. Any custom contact properties migrate as Pipedrive custom fields. Email deduplication uses the email address as the primary key; any duplicates detected during import are flagged for manual resolution before the Person is committed.

Lead Guerrilla Company records map to Pipedrive Organization. The Company-to-Contact linkage is preserved as a Pipedrive Organization- Person relationship (org_id on Person). If the customer's Lead Guerrilla account stores multiple contacts per company, all linked contacts are imported with the same org_id to preserve the account hierarchy. Organization is imported before Person so that the relationship is satisfied at insert time.

Lead Guerrilla Campaign configuration (channel assignments, timing rules, enrollment triggers) cannot be exported as structured data. We capture campaign metadata via admin UI screenshots and configuration notes, and migrate campaign enrollment history as Pipedrive Activity records with a custom activity type CampaignEnrollment. Each Activity records the campaign name, enrollment date, and enrollment channel (email, SMS, Twitter, web notification) as custom fields. Pipedrive's native campaign object is not used because it is scoped to email marketing only and does not support multi-channel enrollment history.

Lead Guerrilla Segments group contacts by form source, behavior, or demographic criteria. We export segment definitions including filter conditions and member counts, then recreate them in Pipedrive as saved filter views and, where applicable, as custom multi-select picklist fields on Person (for example, segment tags as pipedrive_segment__c). Segment membership itself migrates as tag assignments on the Person record using Pipedrive's native tagging system.

Lead scoring is calculated from website behavior, form submissions, and campaign interactions in Lead Guerrilla. We export the current numeric score per contact and reapply it as a custom numeric field lead_score__c on the Pipedrive Person. The scoring model itself (point values per behavior, score thresholds, and auto-enrollment rules) does not migrate; we document the model in the reimplementation playbook so the customer's marketing team can configure equivalent Pipedrive automation rules post-migration.

Lead Guerrilla activity records track email opens, page visits, form submissions, SMS sends, and tweet engagement with timestamps and event types. We export activity history and import it as Pipedrive Activity records with type set to Email, Call, Meeting, or generic Activity depending on the event type. High-volume activity records (more than 500 per contact) are chunked and paginated to respect Pipedrive's API burst limits (20-120 requests per two-second window depending on plan). The activity timestamp is preserved as the Pipedrive Activity due_date and add_time fields.

Lead Guerrilla tags on Contacts and Companies migrate as Pipedrive Tags. Tag naming conventions are preserved exactly as-is. Tags on Companies become Tags on the corresponding Pipedrive Organization; tags on Contacts become Tags on the corresponding Person. Pipedrive's tag model supports multiple tags per record, matching Lead Guerrilla's multi-tag capability.

Lead Guerrilla User accounts map to Pipedrive Users by email match. We export the user list including name and email. In Pipedrive, the customer admin provisions the matching User records before migration. Any Lead Guerrilla user without a Pipedrive counterpart is held in a reconciliation queue. Pipedrive's SCIM v2 endpoint (Ultimate plan) can be used for automated user provisioning from an IdP like Okta if the customer uses SSO.

Landing Pages created in Lead Guerrilla's builder cannot be exported as portable HTML or schema files. We export page metadata (title, URL slug, published status) and redirect configuration as an asset inventory document. The actual page rendering code and form embed scripts are not portable. Post-migration, the customer must rebuild these assets in Pipedrive's Smart Docs or a dedicated landing page tool. We provide a page-by-page inventory with field-level mapping so the rebuild is guided rather than ad hoc.

Web forms embedded in Lead Guerrilla for contact capture cannot be exported as portable form definitions or embed scripts. We export form field definitions, submission mappings, and redirect behavior as a field mapping document. The customer rebuilds forms in Pipedrive's web forms (if on the relevant plan) or a third-party form tool. Form logic (field visibility conditions, required field rules) is documented for manual reimplementation.