CRM migration
Field-level mapping, validation, and rollback between Lead Guerrilla and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Lead Guerrilla
Source
Nutshell
Destination
Compatibility
6 of 8
objects map 1:1 between Lead Guerrilla and Nutshell.
Complexity
CModerate
Timeline
2-3 weeks
Overview
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.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
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
Nutshell
Person
1:1Lead 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
Nutshell
Account
1:1Lead 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
Nutshell
Tag
1:1Lead 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
Nutshell
Task or Event
1:1Lead 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
Nutshell
List or Custom Field
lossyLead 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
Nutshell
Static List
lossyLead 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
Nutshell
None
1:1Lead 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
Nutshell
None
1:1Lead 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.
| Lead Guerrilla | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Tag | Tag1:1 | Fully supported | |
| Activity | Task or Event1:1 | Fully supported | |
| Campaign | List or Custom Fieldlossy | Fully supported | |
| Segment | Static Listlossy | Fully supported | |
| Landing Page | None1:1 | Fully supported | |
| Web Form | None1:1 | Fully supported |
Gotchas + challenges
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 gotchas
No documented API for bulk data export
Marketing automation rules are not exportable
Tight 1CRM coupling creates migration blast radius
Overage billing model creates migration cost surprises
Landing page and form assets require rebuild at destination
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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.
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
Lead Guerrilla
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 4 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Lead Guerrilla and Nutshell.
Object compatibility
4 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Lead Guerrilla: Not publicly documented.
Data volume sensitivity
Lead Guerrilla doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Lead Guerrilla to Nutshell migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Lead Guerrilla
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.