How long does a LegalEdge to Nutshell migration take?

Most LegalEdge-to-Nutshell migrations complete in 48–72 hours for under 50,000 records. The pre-migration extraction from LegalEdge (using built-in export tools rather than an API) can add 1–3 business days of scoping and data pull before the migration run starts. Setups with 500,000+ records or 50+ custom fields extend to 5–7 days. The longest single step is custom field mapping validation — we confirm each LegalEdge custom field has a corresponding Nutshell custom field created before data moves.

Will my LegalEdge workflows and matter-routing rules migrate to Nutshell?

No. FlitStack AI migrates data and schema only — workflows, matter-routing rules, conflict-check automations, and legal process triggers do not transfer between platforms. LegalEdge workflows are built on LegalEdge's own rule engine and have no Nutshell equivalent. Nutshell automation (Pro+ plans) handles email sequences and basic task triggers but does not replicate legal practice workflows. We export your LegalEdge workflow definitions as a reference document for your team to rebuild in Nutshell or a dedicated practice management tool.

What does a LegalEdge matter become in Nutshell?

Each LegalEdge Matter becomes a Nutshell Deal in a dedicated 'Matters' pipeline. The matter name maps to the Deal name, the primary client link maps to the Person or Company lookup, and the matter status (e.g., Active, Pending, Closed) migrates as a custom pick-list field called Matter_Status__c on the Deal. Nutshell's native Deal Stage field is available for sales pipeline tracking independently of legal matter status. Billing data from the matter migrates as custom currency and pick-list fields on the Deal for financial reference.

Can I migrate LegalEdge custom fields to Nutshell?

Yes. LegalEdge custom fields on Matters, Clients, and Activities migrate to corresponding Nutshell custom fields on Deal, Person, and Task objects. We create the Nutshell custom fields (with matching types: text, number, date, pick-list) before migration. Pick-list fields require value-by-value mapping if the source and destination pick-list options differ. We surface the full custom field mapping plan during the sample migration phase so you can review and adjust before the full run.

Does the migration affect my LegalEdge account during cutover?

No. FlitStack uses scoped read access to extract data from LegalEdge — your team continues working in LegalEdge throughout the migration. The delta-pickup window (24–48 hours after the initial load) captures any matter, client, or activity records created or modified during the cutover so Nutshell reflects LegalEdge's final state at go-live. We recommend a soft cutover: continue using LegalEdge for 24–48 hours after the initial migration run, then switch to Nutshell after the delta is applied.

Why does LegalEdge's lack of a public API matter for migration?

LegalEdge does not expose a documented REST or GraphQL API for automated bulk data extraction. Most modern SaaS platforms allow migration tools to pull data via API on a schedule, which supports incremental validation and delta syncs. Because LegalEdge relies on built-in export tools (typically manual CSV or JSON downloads), the extraction step requires more manual coordination with your LegalEdge administrator. FlitStack manages this process but flags the extraction as a project risk early in scoping — export limitations discovered mid-migration can delay the timeline.

What happens to my LegalEdge billing and invoice data after migration?

Nutshell has no native billing, invoicing, or time-tracking object — billing data from LegalEdge is preserved as a set of custom fields on the corresponding Nutshell Deal: Billing_Amount__c (currency), Billing_Status__c (pick-list), and Billing_Date__c (date). These fields give your team visibility into historical billing amounts tied to each matter in Nutshell, but Nutshell will not generate new invoices or track trust account balances. For ongoing billing, we recommend integrating Nutshell with a dedicated billing or accounting tool (e.g., QuickBooks, LawPay) post-migration.

What Nutshell plan do I need to accommodate my LegalEdge data?

Nutshell's contact storage limits vary by plan: Foundation starts at 500 People, Pro supports up to 2,500+, and Business handles larger volumes. Before migration, FlitStack audits your LegalEdge client count and compares it against your target Nutshell plan. If your LegalEdge dataset exceeds the plan's contact limit, we recommend upgrading before migration to avoid needing a second migration pass after the upgrade. API access (required for migration) is available on Pro and Enterprise plans only.

LegalEdge to Nutshell Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

LegalEdge organizes legal practice data around Clients, Matters, Activities, and Bills — a schema built for case management workflows rather than sales pipeline tracking. Nutshell uses a CRM model centered on People, Companies, Leads, and Deals with pipeline stages, task assignments, and activity logs. FlitStack AI maps LegalEdge clients to Nutshell People and Companies (based on whether the contact is an individual or organization), LegalEdge matters to Nutshell Deals using the matter name as the deal name and original matter status as a custom stage field, LegalEdge activities (calls, meetings, notes) to Nutshell Tasks and Events preserving original timestamps and assigned users, and LegalEdge custom fields to Nutshell custom fields on the corresponding object. LegalEdge does not expose a public REST API for bulk data extraction, so the migration uses LegalEdge's built-in export tools (CSV/JSON) combined with the Nutshell JSON-RPC API for import. Workflows, billing rules, and matter-specific legal constructs (e.g., conflict checks, trust accounting) have no Nutshell equivalent and must be rebuilt or handled manually. FlitStack runs a test migration against a representative sample before committing the full dataset, with a delta-pickup window capturing any changes made during the cutover.

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

LegalEdge

What's pushing teams away

Reporting interface lacks clear categorization, making it difficult to distinguish between many similar reports and find the right output.
Difficulty separating monthly-use reports from one-off reports means administrators waste time scrolling through irrelevant options.
Some users report a desire for more modern integrations beyond the Pennsylvania court system, limiting appeal to non-PA jurisdictions.
Limited review volume (13 Capterra reviews) makes it difficult to assess long-term reliability compared to higher-review alternatives like Clio.

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

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

LegalEdge

Client

maps to

Nutshell

Person

1:1

Fully supported

LegalEdge Clients who are individual contacts map to Nutshell People. We pull the Client's name, email, phone, address, and created date. If LegalEdge stores multiple contacts per matter (e.g., attorney and client), each contact becomes a separate Nutshell Person linked to the same matter-derived Deal.

LegalEdge

Client (organization type)

maps to

Nutshell

Company

1:1

Fully supported

LegalEdge Clients marked as organizations or companies map to Nutshell Companies. We extract the organization name, domain/website, industry, and address. Individual Client records that represent a company's primary contact link to the newly created Company via Nutshell's primary-company lookup on the Person.

LegalEdge

Matter

maps to

Nutshell

Deal

1:1

Fully supported

LegalEdge Matters map to Nutshell Deals using the matter name as the deal name and the matter's primary client as the deal's Person or Company link. The matter status (e.g., Active, Pending, Closed) becomes a custom pick-list field on the Deal; Nutshell's native Deal Stage is re-used for sales pipeline tracking separate from legal matter status. We create a Nutshell pipeline named 'Matters' to hold all migrated matter Deals.

LegalEdge

Activity (call, meeting, note)

maps to

Nutshell

Task / Event / Note

1:1

Fully supported

LegalEdge activity records with type 'call' migrate as Nutshell Tasks with Type='Call'; 'meeting' migrates as Nutshell Events with the original start/end time preserved; 'note' migrates as Nutshell Notes attached to the related Person or Deal. Original timestamps, assigned user (matched by email), and linked matter are preserved on each record.

LegalEdge

Document / Attachment

maps to

Nutshell

File (attached to Person/Deal)

1:1

Fully supported

LegalEdge documents and file attachments linked to Matters or Clients are downloaded and re-uploaded to the corresponding Nutshell Person or Deal as a File. File size limits from Nutshell apply (25MB per file). Inline images in notes are extracted and re-hosted as attachments on the Note record.

LegalEdge

Custom Field (Matter-level)

maps to

Nutshell

Custom Field (Deal-level)

1:1

Fully supported

LegalEdge custom fields on Matters (e.g., Case Type, Court Jurisdiction, Assigned Judge) require corresponding custom fields to be created in Nutshell on the Deal object before migration. We create Nutshell custom fields with matching types (text, number, date, pick-list) and map values on a field-by-field basis during the migration run.

LegalEdge

Custom Field (Client-level)

maps to

Nutshell

Custom Field (Person/Company-level)

1:1

Fully supported

LegalEdge custom fields on Clients (e.g., Referral Source, Bar Number, Client Status) migrate as Nutshell custom fields on the Person object for individual contacts or on the Company object for organization-type clients. We match the LegalEdge field type to the nearest Nutshell custom field type and apply value mapping for pick-list fields.

LegalEdge

Bill / Invoice

maps to

Nutshell

Custom Field (Deal-level)

1:1

Fully supported

LegalEdge Bills and invoices have no direct Nutshell equivalent. We preserve the billing data as a set of custom fields on the corresponding Deal (e.g., Billing_Amount__c, Billing_Date__c, Billing_Status__c) so the financial history tied to a matter is visible in Nutshell without requiring a separate billing tool.

LegalEdge

User / Staff Member

maps to

Nutshell

User (matched by email)

1:1

Fully supported

LegalEdge user records are matched to Nutshell users by email address. Unmatched LegalEdge users are flagged before migration; your Nutshell admin either creates the user account first or assigns the user's records to a fallback Nutshell owner. No record lands without a valid Nutshell owner reference.

LegalEdge

Lead

maps to

Nutshell

Lead

1:1

Fully supported

If LegalEdge contains prospect or lead records separate from confirmed Clients, those migrate directly to Nutshell Leads with all standard fields preserved. The Nutshell Lead object captures name, email, phone, source, status, and assigned owner — no transformation required for straightforward lead records.

LegalEdge	Nutshell	Compatibility
Client	Person1:1	Fully supported
Client (organization type)	Company1:1	Fully supported
Matter	Deal1:1	Fully supported
Activity (call, meeting, note)	Task / Event / Note1:1	Fully supported
Document / Attachment	File (attached to Person/Deal)1:1	Fully supported
Custom Field (Matter-level)	Custom Field (Deal-level)1:1	Fully supported
Custom Field (Client-level)	Custom Field (Person/Company-level)1:1	Fully supported
Bill / Invoice	Custom Field (Deal-level)1:1	Fully supported
User / Staff Member	User (matched by email)1:1	Fully supported
Lead	Lead1:1	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.

LegalEdge gotchas

High

No publicly documented API for automated export

Medium

PA UJS integration fields are non-standard

Medium

Custom fields have no documented schema

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

LegalEdge gotchas		Nutshell gotchas
Severity	Issue	Severity	Issue
High	No publicly documented API for automated export	High	Contact tier limits enforced on import
Medium	PA UJS integration fields are non-standard	Medium	No bulk API endpoint requires paginated extraction
Medium	Custom fields have no documented schema	Medium	Email sequences not exportable via API
		Medium	Foundation plan disables key sales features

Pair-specific challenges

LegalEdge has no documented public API — data extraction relies on built-in export tools

Unlike most modern SaaS platforms, LegalEdge does not expose a documented REST or GraphQL API for bulk data access. The migration depends on LegalEdge's built-in export functionality (typically CSV or JSON downloads from within the application). If the export tool caps record counts per file or omits custom field data in the export view, our team must work with your LegalEdge administrator to construct a complete export. This pre-migration scoping step can add 1–3 business days to the project timeline before the actual migration run begins.
Matter status maps to a custom field — not Nutshell's native Deal Stage

Nutshell's native Deal Stage field is scoped for sales pipeline tracking (e.g., Prospecting, Qualification, Proposal). LegalEdge matter statuses (e.g., Active, Pending Litigation, Closed) do not map cleanly to those values. We migrate LegalEdge matter status as a custom pick-list field (Matter_Status__c) on the Nutshell Deal object. This means your team will need to reference two fields on each Deal — the Matter_Status__c custom field for legal case status and the native Stage for sales pipeline progress. We recommend configuring a Nutshell pipeline named 'Matters' to separate legal-case Deals from standard sales Deals in the Nutshell UI.
Nutshell's JSON-RPC API requires an admin-created API key with impersonation rights

Nutshell's API uses HTTP Basic authentication with a domain-or-username and API token pair. API keys with impersonation enabled allow actions to be logged under a specific Nutshell user's name. Keys without impersonation log changes under the API key name itself. We require an admin-created API key with impersonation enabled for the migration so that activity records, tasks, and notes show the correct assigned user in Nutshell after migration. If your Nutshell plan does not include API access (API is available on Pro and Enterprise plans), you will need to upgrade before migration begins.
LegalEdge billing and invoicing data has no native Nutshell equivalent

LegalEdge tracks bills, invoices, time entries, and trust account balances as matter-related records. Nutshell has no native billing, invoicing, or time-tracking object — these are handled by separate integrations (e.g., QuickBooks, LawPay). We preserve LegalEdge billing data as a set of custom currency and pick-list fields on the Nutshell Deal (Billing_Amount__c, Billing_Status__c, Billing_Date__c) so the financial history tied to a matter is visible in Nutshell. However, Nutshell will not generate new invoices or track trust account balances — your team will need to maintain those in a dedicated billing tool after migration.
Nutshell's per-seat contact limit applies after migration

Nutshell plans impose contact (Person) storage limits that scale with your tier: Foundation starts at 500 contacts, Pro at 2,500, and Business at higher volumes. LegalEdge's client storage is typically not capped in the same way. Before migration, FlitStack audits the LegalEdge client count and flags if your target Nutshell plan will require an upgrade to accommodate the full dataset. Upgrading Nutshell tiers post-migration is straightforward, but migrating a second time to move from a lower tier to a higher tier adds cost.

Migration approach

Six steps for a successful LegalEdge to Nutshell data migration

Extract data from LegalEdge using built-in export tools

FlitStack works with your LegalEdge administrator to run full exports of Clients, Matters, Activities, and custom field data. Because LegalEdge lacks a public API, our team coordinates the export from within LegalEdge's built-in export interface — typically generating CSV or JSON files covering all standard and custom fields. We validate the export completeness (record counts, field coverage) before proceeding. If LegalEdge's export tool applies per-file record caps or omits certain custom fields in the export view, we document the gaps and agree on a remediation plan with your team before the migration window opens.
Create Nutshell custom fields and pipelines

Before data lands in Nutshell, FlitStack creates the custom fields required for LegalEdge custom field mapping: Matter_Status__c (pick-list), Case_Type__c (pick-list), Court_Jurisdiction__c (text), Billing_Amount__c (currency), Billing_Status__c (pick-list), Matter_Number__c (text), Original_Create_Date__c (datetime), Client_Type__c (pick-list), and Referral_Source__c (text). We also create a 'Matters' pipeline in Nutshell with appropriate stages for legal case tracking. You receive a pre-flight checklist confirming the custom field setup before we initiate the migration run.
Resolve owners and users by email

LegalEdge user and attorney records are matched against Nutshell user accounts by email address. We generate an owner-resolution report before migration: matched users map directly; unmatched LegalEdge users are flagged so your Nutshell admin can create accounts or assign a fallback owner. No record lands in Nutshell without a valid owner reference, preventing orphaned records. This step also identifies any Nutshell API key scope issues before the full migration run begins.
Run sample migration with field-level diff

A representative slice of LegalEdge records — typically 100–500 covering a mix of individual clients, organization clients, matters in various statuses, and activities — migrates first. FlitStack generates a field-level diff comparing source LegalEdge values against the resulting Nutshell records. You review the diff to verify matter-status-to-Matter_Status__c mapping, owner resolution, deal naming, and activity attachment to the correct Person and Deal. We iterate on the field mapping plan based on your feedback before committing the full migration.
Execute full migration with delta-pickup window

The full LegalEdge dataset migrates to Nutshell via the Nutshell JSON-RPC API, with records loaded in dependency order: Companies first (for organization-type LegalEdge clients), then People, then Deals, then Activities. A delta-pickup window of 24–48 hours after the initial load captures any records created or modified in LegalEdge during the cutover period. FlitStack generates a post-migration reconciliation report showing record counts by object, any skipped or flagged records, and a summary of custom field values populated. One-click rollback is available if reconciliation identifies critical gaps.

Platform deep dives

Context on both ends of the pair

LegalEdge

Source

Strengths

Per-user pricing model with published $750/user/month starting rate, enabling accurate budget forecasting.
Pennsylvania Unified Judicial System integration natively imports court docket data without manual entry.
Highly rated customer service (4.9/5) with custom report development available on request.
Intuitive setup and administrator interface reduce training time for new court staff.

Weaknesses

Limited public documentation of API endpoints and data schema complicates migration tooling.
Small review sample (13 Capterra reviews) limits third-party validation of long-term performance.
Reporting interface lacks search or categorization, requiring users to scroll through all available reports.

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

	LegalEdge Source	Nutshell Destination
Strengths	Per-user pricing model with published $750/user/month starting rate, enabling accurate budget forecasting. Pennsylvania Unified Judicial System integration natively imports court docket data without manual entry. Highly rated customer service (4.9/5) with custom report development available on request. Intuitive setup and administrator interface reduce training time for new court staff.	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	Limited public documentation of API endpoints and data schema complicates migration tooling. Small review sample (13 Capterra reviews) limits third-party validation of long-term performance. Reporting interface lacks search or categorization, requiring users to scroll through all available reports.	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 LegalEdge 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

LegalEdge

Nutshell

How LegalEdge objects map to Nutshell

What specifically takes care here

Six steps for a successful LegalEdge to Nutshell data migration

Context on both ends of the pair

How hard is this migration?

Estimate your LegalEdge to Nutshell migration cost

What are you migrating?

Frequently asked questions about LegalEdge to Nutshell data migrations

Can't find your answer?

Related migrations to explore

Move from LegalEdge.
Land in Nutshell, intact.

Migrate from LegalEdge 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

LegalEdge

Nutshell

How LegalEdge objects map to Nutshell

What specifically takes care here

Six steps for a successful LegalEdge to Nutshell data migration

Context on both ends of the pair

How hard is this migration?

Estimate your LegalEdge to Nutshell migration cost

Frequently asked questions about LegalEdge to Nutshell data migrations

Can't find your answer?

How long does a LegalEdge to Nutshell migration take?

Will my LegalEdge workflows and matter-routing rules migrate to Nutshell?

What does a LegalEdge matter become in Nutshell?

Can I migrate LegalEdge custom fields to Nutshell?

Does the migration affect my LegalEdge account during cutover?

Why does LegalEdge's lack of a public API matter for migration?

What happens to my LegalEdge billing and invoice data after migration?

What Nutshell plan do I need to accommodate my LegalEdge data?

Related migrations to explore

Move from LegalEdge. Land in Nutshell, intact.

Move from LegalEdge.
Land in Nutshell, intact.