CRM migration

Migrate from Lead Guerrilla to Nutshell

Field-level mapping, validation, and rollback between Lead Guerrilla and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

Lead Guerrilla logo

Lead Guerrilla

Source

Nutshell

Destination

Nutshell logo

Compatibility

75%

6 of 8

objects map 1:1 between Lead Guerrilla and Nutshell.

Complexity

CModerate

Timeline

2-3 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Lead Guerrilla to Nutshell is a migration from a niche marketing automation platform built on 1CRM infrastructure to a well-supported SMB CRM with thousands of customers and a documented JSON-RPC API. Lead Guerrilla has no public API for bulk data export, so we choreograph a staged extraction process using CSV downloads from the admin UI combined with manual screenshots for campaign and automation configuration. Nutshell's architecture uses People (Contacts in API terminology) and Accounts (Companies) as the primary entity types, with a separate Lead object for pipeline tracking. We map Lead Guerrilla's Contact records to Nutshell People, Companies to Accounts, and preserve lead scoring values as custom numeric fields. Marketing automation rules, landing pages, and web forms do not migrate automatically; we deliver written inventories with configuration notes so the customer's team can rebuild these in Nutshell or a replacement marketing tool. The tight 1CRM coupling in Lead Guerrilla means some internal cross-references may require manual relinking in Nutshell after migration.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Lead Guerrilla logo

Lead Guerrilla

What's pushing teams away

  • The platform has an extremely small market footprint (reportedly fewer than 20 companies using it as of 2025), making peer reviews, community support, and third-party integrations scarce compared to established marketing automation tools.
  • Lead Guerrilla has no publicly documented REST API or developer portal, making it difficult to export data programmatically, integrate with modern tools, or automate anything outside the built-in workflow builder.
  • The tight coupling with 1CRM as both parent product and primary integration point means teams that outgrow 1CRM or want to use a different CRM are effectively locked out of the platform's core value proposition.
  • Hidden overage fees for exceeding contact or email limits can catch small businesses off guard, with ITQlick reporting unexpected charges ranging from $50 to $500 per incident.
  • The platform competes against tools like MailChimp, Klaviyo, and HubSpot Marketing Hub, all of which offer substantially larger feature sets, better documentation, and richer ecosystems at comparable or lower price points.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Lead Guerrilla objects map to Nutshell

Each row shows how a Lead Guerrilla object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Lead Guerrilla

Contact

maps to

Nutshell

Person

1:1
Fully supported

Lead Guerrilla Contact records map to Nutshell Person records. Standard fields (name, email, phone, address) transfer directly. Custom contact properties map to Nutshell Person custom fields created during schema setup. Lead scoring values from Lead Guerrilla migrate as a custom numeric field lead_score__c on the Person record. The Person's email address serves as the dedupe key during import to prevent duplicate records.

Lead Guerrilla

Company

maps to

Nutshell

Account

1:1
Fully supported

Lead Guerrilla Company records map to Nutshell Account records. The HubSpot-equivalent Company domain or website field becomes the Account website field. We create Account records before Person import so that the Account lookup reference is satisfied at Person insert time. If Lead Guerrilla Company records have no web presence data, we populate the Account name as the sole identifier.

Lead Guerrilla

Tag

maps to

Nutshell

Tag

1:1
Fully supported

Lead Guerrilla tags applied to Contacts and Companies map directly to Nutshell Tags. Tag names transfer exactly as stored to preserve segmentation logic. If a Contact had multiple tags in Lead Guerrilla, all of them attach as separate Tag records in Nutshell via the Person-Tag relationship.

Lead Guerrilla

Activity

maps to

Nutshell

Task or Event

1:1
Fully supported

Lead Guerrilla activity records (email opens, form submissions, page visits, SMS sends, tweet engagement) with timestamps map to Nutshell Task or Event records. Activities that represent a logged interaction with a duration or outcome map as Task with the activity type stored in a custom field. Event-type activities (webinar attendance, scheduled sends) map to Event. The activity timestamp becomes the Task or Event due date for timeline ordering.

Lead Guerrilla

Campaign

maps to

Nutshell

List or Custom Field

lossy
Fully supported

Lead Guerrilla Campaigns (multi-channel sequences across email, SMS, Twitter, web notifications) have no direct Nutshell equivalent because Nutshell is a CRM without a native marketing automation campaign engine. We export campaign configuration including channel assignments, timing rules, and enrollment triggers as a written inventory document. The customer rebuilds campaign logic in their chosen marketing automation tool (Nutshell integrations with Mailchimp or a dedicated platform). Campaign enrollment history on Contact records transfers as a multi-select custom field listing enrolled campaigns.

Lead Guerrilla

Segment

maps to

Nutshell

Static List

lossy
Fully supported

Lead Guerrilla Segment definitions (filter conditions, membership criteria, member counts) export as written configuration notes. Segment membership (the actual list of Contacts in each segment) migrates as Nutshell Static Lists created from the exported member email addresses. Dynamic segments that re-evaluate based on behavior do not have a Nutshell equivalent and must be rebuilt using the destination marketing platform's segment logic.

Lead Guerrilla

Landing Page

maps to

Nutshell

None

1:1
Fully supported

Lead Guerrilla landing pages cannot be exported as portable HTML or schema files. We export page metadata (title, URL slug, published status, redirect rules) as a written inventory. The customer rebuilds landing pages in their chosen platform. We provide a page-by-page field mapping so the rebuild has field-level continuity, but the actual page rendering and form embed scripts require manual reconstruction.

Lead Guerrilla

Web Form

maps to

Nutshell

None

1:1
Fully supported

Lead Guerrilla web form field definitions, submission mappings, and redirect behavior export as written configuration notes. Form logic (field visibility conditions, required field rules, thank-you page redirects) is cataloged for rebuild in the destination platform. Form submission records that exist as Activity history migrate as Task records attached to the submitting Person.

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Lead Guerrilla logo

Lead Guerrilla gotchas

High

No documented API for bulk data export

High

Marketing automation rules are not exportable

High

Tight 1CRM coupling creates migration blast radius

Medium

Overage billing model creates migration cost surprises

Medium

Landing page and form assets require rebuild at destination

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • No documented API forces manual export choreography

    Lead Guerrilla does not publish a REST API, GraphQL endpoint, or developer documentation for programmatic data access. All data export must be performed through the admin UI's CSV download functionality for Contacts and Companies, with manual screen-by-screen cataloging for campaign configuration, segment definitions, and automation rules. We choreograph a staged export process that extends migration timelines significantly compared to platforms with open APIs. For activity history, we rely on CSV exports where available and flag any activity data that cannot be extracted for manual entry or omission.

  • Marketing automation rules are not migratable

    Lead Guerrilla's workflow engine defining when emails fire, when contacts enroll in campaigns, and what score adjustments occur on specific actions has no documented export path. We cannot migrate automation logic as code. During discovery we catalog every active automation through screenshots and configuration notes from the admin UI, then deliver a detailed rebuild playbook so the customer's marketing team can reconstruct each rule in their new platform. This rebuild work is manual and is not included in the standard migration scope.

  • 1CRM cross-references require manual relinking

    Lead Guerrilla shares internal identifiers with 1CRM at the database level. When migrating data to Nutshell, cross-references between Lead Guerrilla records and 1CRM records can become orphaned. We explicitly audit every cross-referenced record pair during scoping and relink them manually in Nutshell. If the customer is simultaneously migrating away from 1CRM, the relinking scope doubles. We recommend sequencing any CRM migration before the marketing automation migration to avoid cascading relinking work.

  • Landing pages and web forms require manual rebuild

    Lead Guerrilla landing pages and embedded web forms cannot be exported as portable HTML or schema files. Page metadata, form field definitions, and redirect rules transfer as written inventory, but the actual page rendering code and embed scripts must be rebuilt in the destination platform. We provide field-level mapping for each landing page and form, but the rebuild work is performed by the customer's team post-migration.

  • Dual billing during parallel-run window

    Lead Guerrilla charges overage fees when contact or email volumes exceed plan thresholds, and these fees are not predictable from the contract alone. When we import Contacts into Nutshell, the customer pays Nutshell subscription costs while continuing to pay Lead Guerrilla contract costs during a parallel-run validation period. We recommend a hard cutover date to stop Lead Guerrilla billing as quickly as feasible after Nutshell goes live and the customer confirms record accuracy.

Migration approach

Six steps for a successful Lead Guerrilla to Nutshell data migration

  1. Discovery and export preparation

    We audit the Lead Guerrilla admin UI across Contacts, Companies, Tags, Campaigns, Segments, Landing Pages, Web Forms, and any visible automation rules. Because there is no documented API, we identify the CSV export paths available in the admin UI, the manual screenshots required for campaign and automation configuration, and any data visible only through the 1CRM backend. We pair this with a Nutshell account audit to confirm available entity types, custom field limits per tier, and API rate limits for the import phase.

  2. Schema design in Nutshell

    We design the destination schema in Nutshell. This includes creating custom fields on Person, Account, and Lead objects to accommodate Lead Guerrilla's custom contact properties and lead scoring values. We define the tag structure, any static lists derived from Lead Guerrilla segments, and the custom fields that will carry campaign enrollment history. Schema design is validated against the Nutshell API's field type constraints before any data export begins.

  3. Staged CSV export from Lead Guerrilla

    We choreograph a staged export process from Lead Guerrilla's admin UI. Contact and Company CSV exports run first. Tag assignments export alongside their parent records. Activity history exports by type (email, form, page visit, SMS, Twitter) using available CSV or report paths. Campaign configuration and automation rules are cataloged via screenshots and manual configuration notes. This staged approach takes longer than API-based extraction and is the primary timeline driver for this migration pair.

  4. Data transformation and deduplication

    We transform the exported CSVs into Nutshell API-compatible payloads. Contact emails serve as the dedupe key to prevent duplicate Person records. Company records insert into Account before Person insert so that Account-Person relationships resolve correctly. Tags attach to the correct Person or Account records by email match. Any Lead Guerrilla custom properties without a direct Nutshell field equivalent become custom fields created during schema design.

  5. API-based import into Nutshell

    We use Nutshell's JSON-RPC API to insert records in dependency order: Accounts first (from Lead Guerrilla Companies), then Persons (with Account lookups resolved), then Tags, then Tasks and Events for activity history. We implement rate-limit handling with exponential backoff per the API documentation. Each phase emits a row-count reconciliation report. Bulk CSV import is not available for activity history in Nutshell's API, so high-volume activity migrations use batched API calls with chunking.

  6. Cutover, validation, and automation rebuild handoff

    We freeze writes in Lead Guerrilla during cutover, run a final delta migration of any records modified during the export window, then mark Nutshell as the system of record. We deliver the campaign and automation inventory document to the customer's team with field-level mapping guidance for landing page and form rebuilds. We support a brief hypercare window for reconciliation issues. We do not rebuild marketing automation rules in Nutshell as part of the standard migration scope.

Platform deep dives

Context on both ends of the pair

Lead Guerrilla logo

Lead Guerrilla

Source

Strengths

  • Multi-channel campaign delivery across email, SMS, Twitter, and web notifications from a single interface.
  • Integrated landing page and web form builder with visitor tracking and A/B testing capabilities.
  • Native tight integration with 1CRM for seamless lead-to-record synchronization.
  • Lead scoring engine that automatically ranks prospects based on interaction behavior.
  • Flexible month-to-month billing with no long-term contract required.

Weaknesses

  • No publicly documented REST API or developer portal, severely limiting programmatic data export and third-party integrations.
  • Extremely small market footprint with very few independent user reviews, making peer validation difficult.
  • Pricing is opaque and requires a sales quote, with hidden overage fees for contact and email volume.
  • Primary integration is locked to 1CRM, making the platform impractical for teams using any other CRM.
  • Scarce third-party ecosystem; limited connector availability compared to HubSpot, MailChimp, or Klaviyo.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Moderate CRM migration. 4 of 8 objects need a mapping; the rest are 1:1.

C

Overall complexity

Moderate migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Lead Guerrilla and Nutshell.

  • Object compatibility

    C

    4 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Lead Guerrilla: Not publicly documented.

  • Data volume sensitivity

    B

    Lead Guerrilla doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Lead Guerrilla to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Lead Guerrilla to Nutshell data migrations

Answers to the questions buyers ask most during Lead Guerrilla to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Lead Guerrilla to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most migrations land between two and three weeks for accounts under 5,000 Contacts with no complex 1CRM cross-references. Migrations with high activity volumes (over 100,000 records), simultaneous 1CRM exit, or large campaign configuration inventories requiring manual cataloging move to four to six weeks because of the manual export choreography that replaces a programmatic API extraction.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Lead Guerrilla.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day