How long does a LEAP to Nutshell migration take?

Most LEAP to Nutshell migrations complete within 3–5 business days for firms with up to 2,000 matters and moderate custom field complexity. Firms with 2,000–10,000+ matters, multi-office LEAP configurations, or extensive document libraries extend to 5–10 business days. The document export phase (limited to 100 files per LEAP batch) and Nutshell custom field creation are the longest planning steps. FlitStack delivers a fixed timeline estimate after reviewing your LEAP data scope.

Will my LEAP matter workflows, billing rules, or trust accounting automations migrate to Nutshell?

No. FlitStack migrates data only — matter workflows, billing rules, trust accounting triggers, and document templates do not transfer. LEAP's trust ledger, cost recovery, and billing status are preserved as custom fields on Nutshell Deals for reference, but Nutshell does not manage legal billing or trust accounting natively. Your firm needs a separate billing process or legal accounting software for trust accounting going forward. We can export your LEAP workflow definitions as a reference document for your Nutshell admin to rebuild manually.

What happens to LEAP matters and time entries in Nutshell?

Each LEAP matter becomes a Nutshell Deal with the matter name as the deal name, the responsible attorney as the deal owner, and the matter status mapped to a deal status. All LEAP-specific fields — matter type, originating attorney, case number, client contact, and billing contact — become custom fields on the Deal. LEAP time entries migrate as Nutshell activities with the original date, duration, and description preserved. Billable status is carried as a custom field on each activity since Nutshell has no native billing status. The original matter ID is stored as Source_Matter_ID__c for traceability.

Can I migrate LEAP custom fields to Nutshell?

Yes, all LEAP custom fields migrate. Common examples include matter type, originating attorney, case number, referral source, and billing contact. Each LEAP custom field is created as a matching Nutshell custom field on the Deal (or Person) object before migration. Pick-list values, date fields, and numeric fields are mapped by type. Any LEAP field with a type that Nutshell does not support is stored as a text field. FlitStack delivers a field-creation checklist during discovery so your Nutshell admin can provision all fields in advance of the migration run.

What happens to LEAP trust balances and billing data?

LEAP's trust ledger tracks per-matter trust balances and last transaction dates, exposed via the Trust, TrustLedger, and TrustBankRec API endpoints. Nutshell has no trust accounting or per-record billing model. FlitStack carries trust balance as a custom currency field (Trust_Balance__c) and last transaction date as a custom datetime field (Trust_Last_Transaction__c) on the Nutshell Deal. Outstanding invoice amounts and invoice status (Draft, Sent, Paid, Written-off) are also stored as custom fields. These are reference data only post-migration — Nutshell does not generate or manage legal invoices.

Does the migration affect my LEAP account during cutover?

No. FlitStack uses scoped read-only API access to LEAP — your team continues working in LEAP throughout the migration. Only the final delta-pickup window (typically 24 hours) requires a brief freeze on new matter creation to capture the clean final state. All matters, time entries, and documents created or modified during the migration window are picked up in the delta run. After cutover, your LEAP account is placed in read-only mode so historical records remain accessible for reference.

How are LEAP documents and files migrated to Nutshell?

LEAP documents are exported using its built-in batch export (limited to 100 documents per operation). FlitStack sequences these batches and re-uploads each to Nutshell as a file attachment linked to the corresponding Deal. The original document creation timestamp from LEAP is stored as a custom datetime field on the Nutshell file for audit continuity. Files larger than 25MB are flagged — these can be stored in a linked cloud storage bucket with a URL reference stored in Nutshell. The document migration runs in parallel with the main data migration to minimize total timeline.

LEAP to Nutshell Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

LEAP is a legal practice management platform built around matters — each matter carries the client relationship, associated documents, time entries, and billing data in one bundle. Nutshell is a sales CRM that separates people, companies, leads, and deals into distinct objects with its own pipeline and activity model. The migration therefore has three structural challenges: converting LEAP matters into Nutshell deals (preserving the client-person-company link), preserving LEAP time entries as Nutshell activities, and carrying LEAP's billing and custom fields into Nutshell custom fields. FlitStack AI extracts data from LEAP via its REST API (cost recovery, fee task codes, trust ledger, timesheet, and user endpoints are documented at leap.build/api-reference). We map LEAP clients to Nutshell people and companies, LEAP matters to Nutshell deals, and LEAP time entries to Nutshell activities. Documents are exported in batches of up to 100 from LEAP and re-uploaded to Nutshell as file attachments with original creation timestamps preserved. LEAP's custom fields (matter type, originating attorney, billing contact, trust balance) are created as Nutshell custom fields before migration. The migration uses scoped read-only API access to LEAP with a 24–48 hour delta window for in-flight records created during cutover. FlitStack runs a sample migration first and generates a field-level diff so you can validate every mapping before the full run commits.

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

LEAP

What's pushing teams away

Performance has degraded after recent platform updates, with the software crashing and causing instability in Outlook and Office integrations, which disrupts daily practice operations.
Support responsiveness does not match the promised service level — customers report generic email responses and unwillingness to revert problematic updates or provide hands-on migration assistance.
The transition service is marketed as supported but relies heavily on firm-side data preparation, and LEAP's policy of migrating from only a single source system creates risk for firms running hybrid environments.
Setup and IT onboarding coordination is poor — anti-virus exception requirements are not communicated upfront, leading to machine freezes and slow performance that go unaddressed during the implementation period.

Choosing

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

Each row shows how a LEAP 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.

LEAP

LEAP Company (client)

maps to

Nutshell

Nutshell Company + Person

1:1

Fully supported

LEAP Company stores the firm name, primary contact name, email, and phone in one record. FlitStack splits this into two Nutshell records: a Company with the firm data, and a Person with the primary contact details linked to that Company. If LEAP has multiple contacts per company, additional Person records are created and linked.

LEAP

LEAP Matter

maps to

Nutshell

Nutshell Deal

many:1

Fully supported

LEAP Matter carries case name, responsible attorney, matter type, client reference, open date, and status — none of which have a single direct equivalent in Nutshell. We create one Deal per Matter, using the Matter name as the Deal name, the responsible attorney as OwnerId (matched by email), and the status as a custom field on the Deal. The client firm maps to the linked Company.

LEAP

LEAP Matter

maps to

Nutshell

Nutshell Custom Fields (on Deal)

1:1

Fully supported

Matter type, originating attorney, client contact name, case number, and billing contact have no native Nutshell equivalent. We create a set of custom fields on the Deal object before migration: Matter_Type__c, Originating_Attorney__c, Client_Contact__c, Case_Number__c, and Billing_Contact__c. LEAP's internal matterId is stored as Source_Matter_ID__c for traceability.

LEAP

LEAP Timesheet (time entry)

maps to

Nutshell

Nutshell Activity

1:1

Fully supported

Each LEAP time entry — date, duration, and description — migrates as a Nutshell activity with Subject set to the linked matter name, and Activity type reflecting the time entry. Original timestamps are preserved. The billable/billed status migrates as a custom field (Billable_Status__c) since Nutshell has no native billing status on activities.

LEAP

LEAP Document (file attachment)

maps to

Nutshell

Nutshell File (on Deal)

1:1

Fully supported

LEAP documents are exported in batches of up to 100 via its UI export tool, then re-uploaded to Nutshell as file attachments linked to the corresponding Deal. The original LEAP document creation date is stored as a custom metadata field on the file for audit continuity. Nutshell supports file uploads up to 25MB per file.

LEAP

LEAP User (fee earner / attorney)

maps to

Nutshell

Nutshell User

1:1

Fully supported

LEAP user records are matched to Nutshell users by email address. FlitStack generates a pre-migration user matching report — any LEAP users without a corresponding Nutshell account are flagged and must be provisioned before migration. LEAP user type flags (fee earner, administrator) are preserved in a custom field since Nutshell's role model is simpler.

LEAP

LEAP Trust Ledger (per matter)

maps to

Nutshell

Nutshell Custom Fields (on Deal)

1:1

Fully supported

LEAP's trust accounting ledger tracks per-matter trust balances and last transaction dates. Nutshell has no trust accounting model. We carry trust balance and last transaction date as custom fields (Trust_Balance__c, Trust_Last_Transaction__c) on the corresponding Deal for financial reference after cutover.

LEAP

LEAP Billing / Cost Recovery

maps to

Nutshell

Nutshell Custom Fields (on Deal)

1:1

Fully supported

LEAP invoice records (via CostRecovery and Trust API endpoints) track outstanding amounts and invoice status (Draft, Sent, Paid, Written-off). These are carried as custom fields on the Deal — Outstanding_Amount__c and Invoice_Status__c — because Nutshell does not generate or manage legal invoices.

LEAP

LEAP Custom Fields (matter-level)

maps to

Nutshell

Nutshell Custom Fields (on Deal/Person)

1:1

Fully supported

LEAP's configurable per-matter custom fields are enumerated during discovery and created as matching Nutshell custom fields on the Deal object. Field type is preserved — pick-list values are mapped as pick-lists, dates as dates, numbers as numbers. Any LEAP field with no matching Nutshell type is stored as text.

LEAP

LEAP Matter Association (multi-attorney)

maps to

Nutshell

Nutshell Custom Field (on Deal)

1:many

Fully supported

LEAP allows multiple responsible attorneys per matter. Nutshell Deals have a single OwnerId. We set the primary attorney (first in LEAP) as the Deal owner and store additional attorneys as a custom text field (Other_Attorneys__c) containing a comma-separated list of email addresses for reference.

LEAP	Nutshell	Compatibility
LEAP Company (client)	Nutshell Company + Person1:1	Fully supported
LEAP Matter	Nutshell Dealmany:1	Fully supported
LEAP Matter	Nutshell Custom Fields (on Deal)1:1	Fully supported
LEAP Timesheet (time entry)	Nutshell Activity1:1	Fully supported
LEAP Document (file attachment)	Nutshell File (on Deal)1:1	Fully supported
LEAP User (fee earner / attorney)	Nutshell User1:1	Fully supported
LEAP Trust Ledger (per matter)	Nutshell Custom Fields (on Deal)1:1	Fully supported
LEAP Billing / Cost Recovery	Nutshell Custom Fields (on Deal)1:1	Fully supported
LEAP Custom Fields (matter-level)	Nutshell Custom Fields (on Deal/Person)1:1	Fully supported
LEAP Matter Association (multi-attorney)	Nutshell Custom Field (on Deal)1:many	Fully supported

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.

LEAP gotchas

High

Document export capped at 100 records per batch

High

Single-source datafile migration policy

Medium

Trust accounting jurisdiction rules vary by region

Medium

No published API rate limits or bulk endpoints

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

LEAP gotchas		Nutshell gotchas
Severity	Issue	Severity	Issue
High	Document export capped at 100 records per batch	High	Contact tier limits enforced on import
High	Single-source datafile migration policy	Medium	No bulk API endpoint requires paginated extraction
Medium	Trust accounting jurisdiction rules vary by region	Medium	Email sequences not exportable via API
Medium	No published API rate limits or bulk endpoints	Medium	Foundation plan disables key sales features

Pair-specific challenges

Matter-centric model has no direct equivalent in Nutshell's deal structure

LEAP organizes client data around matters — a matter bundles the client relationship, multiple attorneys, documents, time entries, and billing records. Nutshell separates these into People, Companies, Deals, Activities, and Files with no native concept of a legal matter. FlitStack creates one Deal per Matter, stores LEAP-specific fields (matter type, originating attorney, case number, billing contact) as Nutshell custom fields on the Deal, and links the client Company and Person. Billing status and trust balances also become custom fields. Before migration, you will receive a full schema plan showing every custom field created in Nutshell so your admin can review and adjust labels.
LEAP documents export in batches of 100 with no bulk API download

LEAP's document export tool is limited to 100 documents per export operation via the right-click Export UI. There is no documented bulk API endpoint for programmatic document extraction in the LEAP API reference. FlitStack sequences document export in batches of 100 using LEAP's built-in export, then re-uploads each batch to Nutshell as file attachments on the corresponding Deal. For firms with thousands of documents, this adds a manual coordination step and extends the document migration timeline. We flag the document count during scoping so the batch schedule is planned before migration day.
Trust accounting and per-matter billing status have no Nutshell equivalent

LEAP's trust ledger (exposed via the Trust, TrustReceipt, TrustLedger, and TrustBankRec API endpoints) tracks per-matter trust balances and last transaction dates. Nutshell has no trust accounting, no per-record billing status, and no invoice generation. FlitStack preserves outstanding invoice amounts, invoice status (Draft, Sent, Paid, Written-off), trust balance, and last trust transaction date as custom currency and pick-list fields on the Deal. These fields are readable post-migration but Nutshell will not manage billing — your firm needs a separate billing system or manual process for trust accounting going forward.
Multi-attorney matters collapse to a single Nutshell deal owner

LEAP allows multiple responsible attorneys to be assigned to a single matter. Nutshell Deals have a single OwnerId field. FlitStack maps the primary (first-listed) attorney as the Deal owner, resolved by email match to a Nutshell user. Additional attorneys are stored as a comma-separated email list in a custom text field (Other_Attorneys__c) on the Deal for reference. If your firm relies on seeing all attorneys on a matter in a single view, this custom field is the only option — Nutshell does not support multi-owner Deals natively.
LEAP custom fields require Nutshell-side field creation before data lands

LEAP firms frequently configure per-matter custom fields (e.g., practice area, referral source, court jurisdiction, statutory limitation date). Nutshell custom fields must be created manually in the Nutshell settings UI before migration. FlitStack enumerates every LEAP custom field during the discovery phase, maps each to a corresponding Nutshell custom field, and delivers a field-creation checklist so your Nutshell admin can provision the fields in advance. Migration of records with unmapped custom fields is deferred until the field exists in Nutshell — we flag this clearly in the pre-migration report.

Migration approach

Six steps for a successful LEAP to Nutshell data migration

Discovery and schema planning

FlitStack reviews your LEAP data export and API schema — matters, time entries, documents, custom fields, users, and trust ledger entries. We map every LEAP object to Nutshell's equivalent, enumerate the custom fields needed in Nutshell (matter_type, originating_attorney, trust_balance, and so on), and deliver a schema plan. Your Nutshell admin creates the required custom fields before migration. You also receive a document batch schedule if your LEAP instance holds more than 100 documents.
User matching by email

FlitStack matches LEAP users (attorneys, fee earners, administrators) to Nutshell users by email address. A pre-migration user matching report is delivered showing every LEAP user and their Nutshell counterpart — or a 'not found' flag for users who need to be provisioned. No record migrates to an unmapped owner. LEAP user type flags are stored as a custom field on the Nutshell User record for reference.
Migrate people, companies, and deals before activities and documents

Nutshell requires companies to exist before people (via foreign key) and deals to exist before activities (for linking). FlitStack sequences the migration accordingly: (1) Companies + People from LEAP Company records, (2) Deals from LEAP Matters with all custom fields populated, owner set to the primary attorney, and billing/trust custom fields carrying the financial snapshot from LEAP, (3) Activities from LEAP time entries linked to the corresponding Deals, (4) Document batch re-upload to Nutshell files attached to the relevant Deal.
Run sample migration with field-level diff

A representative sample of LEAP records — typically 50–100 matters spanning a range of matter types, attorneys, and document counts — migrates first. FlitStack generates a field-level diff showing every source field value and its destination counterpart so you can verify matter-to-deal conversion, custom field population, trust balance preservation, owner matching, and activity linking before the full run. You approve or request adjustments at this stage.
Delta pickup and cutover

The full migration runs against Nutshell's JSON-RPC API. A delta-pickup window (24–48 hours) captures any LEAP records modified or created during the cutover — new matters, updated statuses, new time entries. FlitStack captures an audit log of every record inserted or updated. One-click rollback is available if reconciliation fails. After rollback confirmation, your team switches to Nutshell and your LEAP account is placed in read-only mode.

Platform deep dives

Context on both ends of the pair

LEAP

Source

Strengths

All-in-one platform combining practice management, document automation, and financial compliance without third-party integration overhead.
Built-in trust accounting with General Ledger, nominal ledger, and purchase ledger disbursements covering jurisdiction-specific compliance requirements.
AI-assisted document creation embedded directly in the matter workflow reduces manual drafting time for standardised legal documents.
Over 5,140 documented electronic data conversions and 66,000+ global users provide evidence of a mature migration and support ecosystem.
99.9% average uptime globally and cloud-native architecture eliminate on-premise server maintenance for law firms.

Weaknesses

No native bulk document export — LEAP caps batch exports at 100 documents per operation with no zip compression, requiring manual folder batching for large matters.
LEAP's single-datafile architecture enforces migration from one source system only, blocking firms that run multiple integrated practice management products from consolidating in a single transition.
No publicly documented API rate limits, making capacity planning for large data migrations an uncertainty that requires direct inquiry with LEAP's development team.
Custom Fields require schema extraction before migration begins, adding a preparatory step that is not always communicated during the initial scoping conversation.

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

	LEAP Source	Nutshell Destination
Strengths	All-in-one platform combining practice management, document automation, and financial compliance without third-party integration overhead. Built-in trust accounting with General Ledger, nominal ledger, and purchase ledger disbursements covering jurisdiction-specific compliance requirements. AI-assisted document creation embedded directly in the matter workflow reduces manual drafting time for standardised legal documents. Over 5,140 documented electronic data conversions and 66,000+ global users provide evidence of a mature migration and support ecosystem. 99.9% average uptime globally and cloud-native architecture eliminate on-premise server maintenance for law firms.	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	No native bulk document export — LEAP caps batch exports at 100 documents per operation with no zip compression, requiring manual folder batching for large matters. LEAP's single-datafile architecture enforces migration from one source system only, blocking firms that run multiple integrated practice management products from consolidating in a single transition. No publicly documented API rate limits, making capacity planning for large data migrations an uncertainty that requires direct inquiry with LEAP's development team. Custom Fields require schema extraction before migration begins, adding a preparatory step that is not always communicated during the initial scoping conversation.	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

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from LEAP to Nutshell

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

LEAP

Nutshell

How LEAP objects map to Nutshell

What specifically takes care here

Six steps for a successful LEAP to Nutshell data migration

Context on both ends of the pair

How hard is this migration?

Estimate your LEAP to Nutshell migration cost

What are you migrating?

Frequently asked questions about LEAP to Nutshell data migrations

Can't find your answer?

Related migrations to explore

Move from LEAP.
Land in Nutshell, intact.

Migrate from LEAP to Nutshell

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

LEAP

Nutshell

How LEAP objects map to Nutshell

What specifically takes care here

Six steps for a successful LEAP to Nutshell data migration

Context on both ends of the pair

How hard is this migration?

Estimate your LEAP to Nutshell migration cost

Frequently asked questions about LEAP to Nutshell data migrations

Can't find your answer?

How long does a LEAP to Nutshell migration take?

Will my LEAP matter workflows, billing rules, or trust accounting automations migrate to Nutshell?

What happens to LEAP matters and time entries in Nutshell?

Can I migrate LEAP custom fields to Nutshell?

What happens to LEAP trust balances and billing data?

Does the migration affect my LEAP account during cutover?

How are LEAP documents and files migrated to Nutshell?

Related migrations to explore

Move from LEAP. Land in Nutshell, intact.

Move from LEAP.
Land in Nutshell, intact.