CRM migration

Migrate from Lead Docket to Nutshell

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

Get a quote See object mapping
Lead Docket logo

Lead Docket

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

10 of 10

objects map 1:1 between Lead Docket and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Lead Docket is a legal-intake CRM designed for law firms — its data model centers on leads, case types, lead statuses, attorney rotation, and intake-specific automations. Nutshell is a general-purpose sales CRM with People, Companies, Leads, and Deals objects plus pipeline stages, activity tracking, and built-in email marketing. The two platforms share few native equivalents beyond basic contact fields, which means the migration requires reconstructing legal-intake concepts (case types, lead statuses, attorney assignments) as Nutshell custom fields and value-mapped pick-lists. We map Lead Docket's leads to Nutshell's Leads object, Lead Docket contacts to Nutshell People, Lead Docket companies to Nutshell Companies, and case-type/stage data to Nutshell custom fields. Lead Docket's automation rules (status-change triggers, email follow-ups, Vinesign integration) do not migrate — they must be rebuilt in Nutshell's workflow tools or exported as configuration references for your admin. The migration uses Nutshell's bulk import CSV format for People and Companies, API-based lead creation, and manual field mapping for custom properties. We sequence the migration so foreign-key relationships (contact-to-company links) resolve correctly before deals attach. We disclose honestly: integrations that push leads INTO Lead Docket (Filevine, intake forms, PPC tracking) will need new webhook endpoints 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.

Lead Docket logo

Source platform

Lead Docket platform overview

Scorecard, SWOT, gotchas, and pricing for Lead Docket.
Nutshell logo

Destination platform

Nutshell platform overview

Scorecard, SWOT, gotchas, and pricing for Nutshell.

Data migration guide

The complete Nutshell migration guide

Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.

Destination checklist

Nutshell migration checklist

Pre- and post-cutover tasks for moving onto Nutshell.

Why teams make this switch

Two sides of the same decision

Leaving

Lead Docket logo

Lead Docket

What's pushing teams away

  • Reporting is weak—reviews across G2 and Capterra cite poor reporting accuracy and limited analytics as a persistent pain point for data-driven firms.
  • The platform's API is severely limited: integrations and external calls can only create new leads, not update existing records, which breaks live sync setups.
  • Messaging and communication features have reliability issues according to verified reviews, with users reporting dropped texts or notification failures.
  • The Filevine integration has known quirks—reviewers note minor but recurring issues when syncing lead data to Filevine case files.
  • Some users report billing surprises, particularly around the paid add-on model for automations, which are not included in base subscriptions.

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 Docket objects map to Nutshell

Each row shows how a Lead Docket 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 Docket

Lead Docket Lead

maps to

Nutshell

Nutshell Lead

1:1
Fully supported

Lead Docket leads map to Nutshell leads 1:1 via email matching. Lead Docket's 11 default lead statuses (New, Attempting Contact, Qualified, Consultation Scheduled, etc.) map to Nutshell custom pick-list values created as a Lead Status field. Any lead without an email address requires a fallback identifier field.

Lead Docket

Lead Docket Contact

maps to

Nutshell

Nutshell Person

1:1
Fully supported

Lead Docket contacts map to Nutshell People records by email. Phone, address, job title, and custom fields on the contact migrate as Nutshell Person custom fields. Nutshell People do not have a native role field — attorney vs. referral-source roles are stored in a custom Role pick-list field on the Person record.

Lead Docket

Lead Docket Company

maps to

Nutshell

Nutshell Company

1:1
Fully supported

Lead Docket companies map directly to Nutshell Companies. Company name, domain, industry, phone, and address fields migrate as direct equivalents. Parent-child company hierarchies in Lead Docket map to Nutshell's parent_company_id field. Companies without a name receive a placeholder identifier based on the primary contact name.

Lead Docket

Lead Docket Case Type

maps to

Nutshell

Nutshell Custom Field (Lead)

1:1
Fully supported

Lead Docket's practice-area case types (Personal Injury, Criminal Defense, Family Law, etc.) have no Nutshell native equivalent. We create a Case_Type__c custom pick-list field on Nutshell Leads and map each Lead Docket case type value to the corresponding Nutshell pick-list entry. This preserves intake categorization for reporting by practice area.

Lead Docket

Lead Docket Lead Status

maps to

Nutshell

Nutshell Custom Field (Lead)

1:1
Fully supported

Lead Docket's 11 lead statuses map to a custom Lead Status field in Nutshell. Status names map value-by-value: 'New' → 'New', 'Attempting Contact' → 'Attempting Contact', 'Qualified' → 'Qualified', etc. We preserve the original status-transition timestamps in a separate Status_Changed__c datetime field for audit continuity.

Lead Docket

Lead Docket Attorney Assignment

maps to

Nutshell

Nutshell Custom Field (Lead)

1:1
Fully supported

Lead Docket's attorney rotation and manual attorney assignment map to an Assigned_Attorney__c text field on Nutshell Leads. If Lead Docket's attorney rotation used a round-robin logic, we capture the final assigned attorney name rather than the rotation algorithm (which cannot be reconstructed). Owner resolution by email match applies to users in Nutshell.

Lead Docket

Lead Docket Lead Source / Source Rule

maps to

Nutshell

Nutshell Custom Field (Lead/Person)

1:1
Fully supported

Lead Docket's Marketing Source and Contact Source fields map to Nutshell custom fields (Lead_Source__c on both Lead and Person). The Source Rule automation that auto-populates these fields does not migrate — we document the rule logic for manual reconfiguration in Nutshell.

Lead Docket

Lead Docket Activity (Calls, Emails, Notes)

maps to

Nutshell

Nutshell Task / Activity

1:1
Fully supported

Lead Docket call logs, emails, and notes with original timestamps migrate as Nutshell Tasks. Task subject, body, owner, and create date are preserved. Call duration and disposition fields map to Nutshell custom task fields. Notes attached to leads migrate as Nutshell note entries linked to the corresponding Lead record.

Lead Docket

Lead Docket Custom Fields

maps to

Nutshell

Nutshell Custom Fields

1:1
Fully supported

Any Lead Docket custom fields (on Lead, Contact, or Company) that have no Nutshell native equivalent are created as Nutshell custom fields on the corresponding object. Field type mapping: text → text, number → number, date → date, pick-list → pick-list with value mapping. Nutshell supports custom fields on Person, Company, and Lead objects via the Settings → Custom Fields UI.

Lead Docket

Lead Docket Integrations (Filevine, Vinesign, PPC forms)

maps to

Nutshell

No equivalent

1:1
Fully supported

Lead Docket integrations that push leads from external sources (Filevine case handoff, Vinesign document completion, PPC form submissions with click IDs and campaign tracking) have no Nutshell equivalent. After migration, webhook endpoints must be reconfigured to point to Nutshell's API or integration platform (Zapier, Make) for real-time lead capture.

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 Docket logo

Lead Docket gotchas

High

API write-only limitation blocks record updates

High

Automations are excluded from all export methods

Medium

Filevine integration has documented one-way sync issues

Medium

50-automation-change cap per lead

Low

Custom fields require manual recreation and type mapping

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

  • Lead Docket's write-restricted API forces bulk CSV import instead of API-based migration

    Lead Docket's API only permits creating new leads — it cannot update existing records, query custom field values, or retrieve lead status history. This means FlitStack AI cannot use Lead Docket's API as the primary migration channel for all objects. Instead, we export Lead Docket data via their native CSV export (Contacts, Leads, Companies, Expenses) and supplement with manual record-by-record export for custom field values that CSV does not expose. Nutshell's full API receives the imported data, but the extraction phase requires CSV-based extraction from Lead Docket, which may truncate nested custom field data or multi-select pick-list values.

  • Legal-intake data model has no direct Nutshell equivalent — case types and lead statuses require custom fields and value mapping

    Lead Docket's core objects (Lead Status, Case Type, Attorney Assignment) exist specifically for legal intake workflows. Nutshell has no native case-type or intake-status concept — all legal-intake metadata must be recreated as Nutshell custom fields on the Lead object. The 11 default Lead Docket lead statuses must be mapped value-by-value to a custom pick-list field in Nutshell, and any custom lead statuses your firm added require manual value creation before the mapping can be defined. This is manual schema setup that your Nutshell admin must approve before migration data lands.

  • Lead Docket automations and workflows do not migrate and cannot be automatically rebuilt

    Lead Docket's automations (a paid add-on) execute status changes, send Vinesign documents, and push leads to Filevine based on trigger conditions. Nutshell has no equivalent to Lead Docket's automation engine, and automation logic does not export in a machine-readable format. We document your automation rules as a configuration reference — triggers, conditions, and actions — so your Nutshell admin can rebuild them in Nutshell Pro's sales automation tool. The rebuild is a manual, billable services effort separate from the data migration.

  • PPC tracking data (click IDs, campaign names, keywords) requires pre-migration field creation in Nutshell

    Lead Docket captures PPC click IDs, campaign names, keywords, and UTM parameters from form submissions via its Advanced Lead Tracking feature. Nutshell does not have native fields for UTM parameters or click IDs — these must be created as custom text fields on the Lead object before migration. If your team relies on this marketing attribution data for ROI reporting, coordinate with your Nutshell admin to create Lead_Click_ID__c, Lead_Campaign__c, and Lead_Keyword__c fields before migration runs. Data not mapped to existing fields at migration time is lost.

  • Integrations pushing leads INTO Lead Docket need new endpoints post-migration

    Lead Docket integrations (Filevine case handoff, Vinesign document completion, website intake forms, PPC form trackers) push data into Lead Docket via webhook. These integrations are destination-specific and do not exist in Nutshell. After migration, your development team must reconfigure webhook endpoints to point to Nutshell's API or your middleware platform (Zapier, Make, webhook relay). FlitStack AI provides a migration completion report listing all integration touchpoints identified in your Lead Docket configuration so your dev team can prioritize rebuild work.

Migration approach

Six steps for a successful Lead Docket to Nutshell data migration

  1. Extract Lead Docket data via native CSV export and supplemental API calls

    FlitStack AI initiates the migration by exporting Lead Docket's core objects — Contacts, Leads, Companies, and Expenses — via their built-in CSV export tool. For custom field values and lead status history not fully exposed in the standard export, we use Lead Docket's API for read access (leads, people, companies) to supplement the CSV with complete field-level data. We document all identified custom fields, lead statuses, case types, and integration webhooks during this phase so the Nutshell schema setup phase has a complete field inventory.

  2. Design Nutshell custom fields and pick-lists for legal-intake metadata

    Before importing data, your Nutshell admin (or our team) creates the custom fields required for the migration: Lead_Status__c (pick-list for the 11 lead statuses), Case_Type__c (pick-list for practice-area case types), Assigned_Attorney__c (text), UTM_Click_ID__c (text), UTM_Campaign__c (text), and any other Lead Docket custom fields with no native Nutshell equivalent. We deliver a field creation checklist with the exact pick-list values pulled from your Lead Docket instance so nothing is missed. Nutshell's custom field interface (Settings → Custom Fields) supports field creation on Person, Company, and Lead objects.

  3. Map and transform records, then run sample migration with field-level diff

    We map each Lead Docket record to its Nutshell equivalent using the field mapping matrix, applying value mapping for lead statuses and case types, transforming company hierarchies into Nutshell's parent_company_id model, and resolving attorney assignments to named text fields. A representative sample (100–500 records spanning leads, people, companies, and activities) migrates first into your live Nutshell instance. We generate a field-level diff showing source vs. destination values for every mapped field so you can verify pick-list value coverage, custom field creation completeness, and record linkage before the full run commits.

  4. Execute full migration with delta-pickup window and audit log

    The full migration loads all Lead Docket leads, people, companies, activities, and custom field data into Nutshell. A delta-pickup window (typically 24–48 hours) runs alongside the full migration, capturing any records created or modified in Lead Docket during the cutover period so your Nutshell instance reflects the final state of your Lead Docket data at go-live. Every import operation is logged in an audit trail. If reconciliation fails — record counts don't match, foreign keys are missing — one-click rollback reverts the Nutshell data to pre-migration state while your team continues working in Lead Docket.

  5. Deliver integration rebuild reference and post-migration handoff documentation

    After migration completes, we deliver a Migration Completion Report listing all migrated records by object, all identified but unmapped fields, and all integration touchpoints (Filevine, Vinesign, PPC trackers) that need new webhook endpoints. We also provide an Automation Reference Document summarizing your Lead Docket automation rules — triggers, conditions, and actions — formatted as a rebuild guide for Nutshell Pro's sales automation tool. Your team transitions to Nutshell with a complete data foundation and a prioritized rebuild checklist for the integration and automation work that follows.

Platform deep dives

Context on both ends of the pair

Lead Docket logo

Lead Docket

Source

Strengths

  • Purpose-built for legal intake rather than adapted from a horizontal CRM, with native case type and attorney rotation concepts.
  • Granular lead source attribution shows exactly where each case originated for marketing spend accountability.
  • User-friendly dashboard keeps all leads visible and organized without requiring technical training.
  • Automation engine can trigger status changes, send intake forms, and push leads to Filevine or Vinesign in real time.
  • Supports custom fields on leads and contacts, allowing firms to tailor the data model to their practice areas.

Weaknesses

  • API is write-only: external systems can only create new leads, not update or deduplicate existing records.
  • Reporting is widely cited as weak and inaccurate, limiting data-driven decision-making for firm management.
  • Automations are gated behind a paid add-on, increasing total cost of ownership beyond the base subscription.
  • Integrations are one-directional and unreliable for two-way sync, particularly the Filevine connection which has documented quirks.
  • Messaging features have reliability issues reported by multiple reviewers, including dropped texts and notification failures.
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?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

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

  • Object compatibility

    B

    2 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 Docket: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Lead Docket 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 Docket to Nutshell data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Lead Docket to Nutshell migrations complete in 48–72 hours of clock time for under 5,000 records. Larger setups with 5,000+ records or complex custom field taxonomies extend to 5–10 business days. The primary time driver is the extraction phase — Lead Docket's API limitations mean we rely on CSV export supplemented by API reads, which takes longer than a pure-API migration. Nutshell custom field creation and pick-list value mapping are the longest planning steps before data can land.

Adjacent paths

Related migrations to explore

Other ways to leave Lead Docket

Lead Docket logo
Freshsales logo
Lead Docket to Freshsales Migration
Lead Docket logo
HighLevel logo
Lead Docket to HighLevel Migration
Lead Docket logo
HubSpot logo
Lead Docket to HubSpot Migration

Other ways to arrive at Nutshell

aACE logo
Nutshell logo
aACE to Nutshell Migration
Accelo logo
Nutshell logo
Accelo to Nutshell Migration
Access CRM logo
Nutshell logo
Access CRM to Nutshell Migration

Same-CRM migrations

Freshsales logo
HighLevel logo
Freshsales to HighLevel Migration
Freshsales logo
HubSpot logo
Freshsales to HubSpot Migration
Freshsales logo
Mailchimp logo
Freshsales to Mailchimp Migration

Ready when you are

Move from Lead Docket.
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.

Book a call
Accuracy guarantee Rollback included Quote in 1 business day