CRM migration

Migrate from LegalE to Nutshell

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

LegalE logo

LegalE

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

10 of 10

objects map 1:1 between LegalE and Nutshell.

Complexity

CModerate

Timeline

2–4 days

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

LegalE and Nutshell both organize around people and companies, but their data models diverge in how they handle custom fields, deal stages, and activity attachments. LegalE typically stores contact records with extensible custom properties, while Nutshell uses dedicated Person and Company objects with a separate custom-fields model per record type. The migration carries everything LegalE stores natively — people, companies, deals, notes, tasks, and custom properties — into Nutshell's schema. The harder problems are mapping LegalE's custom object extensions to Nutshell's custom fields, consolidating LegalE's address sub-structures into Nutshell's combined address fields, and getting note attachments routed to Nutshell's Files entity correctly. Workflows, templates, and automation logic do not migrate — those require manual rebuild in Nutshell using its own automation tools. FlitStack sequences the migration via Nutshell's JSON-RPC API with Basic auth, using a test-then-cutover approach with a 24–48 hour delta window to capture in-flight changes at go-live. During the migration, FlitStack maintains a detailed audit log of all API calls and record transformations. This log enables rapid troubleshooting if any discrepancies appear after cutover. The delta-pickup window ensures that any updates made in LegalE during the final 24–48 hours are captured in Nutshell without a full re-export.

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

LegalE logo

LegalE

What's pushing teams away

  • Limited third-party reviewer footprint makes independent feature validation difficult during evaluation.
  • Public pricing and feature breakdowns are not published, so side-by-side comparisons require direct sales engagement.
  • Integration catalogue is narrow — Microsoft 365 and document storage are the typical connection points; modern SaaS connectors are bespoke.
  • Reporting and analytics depth lags larger ELM platforms (TyMetrix, Onit, SimpleLegal); teams needing matter-level spend benchmarking outgrow it.
  • Mobile experience is functional but not differentiating — outside-counsel collaboration and on-the-go legal review favor cloud-native competitors.

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

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

LegalE

Contact / Person

maps to

Nutshell

Person

1:1
Fully supported

LegalE's contact records map 1:1 to Nutshell Person records. Name, email, phone, title, address, and custom fields on the contact transfer directly. LegalE contacts without an associated company link to a placeholder company or get assigned to a default Nutshell Company record.

LegalE

Company / Organization

maps to

Nutshell

Company

1:1
Fully supported

LegalE organization records map to Nutshell Company records. Company name, domain, industry, employee count, and address fields transfer directly. Parent-child company hierarchies in LegalE map to Nutshell's Parent Company field if configured. FlitStack also ensures that any custom fields on the company record are transferred to the corresponding Nutshell Company custom fields.

LegalE

Matter / Case

maps to

Nutshell

Deal

1:1
Fully supported

LegalE matters (cases) map to Nutshell Deals. Matter name becomes Deal name; matter status maps to Nutshell pipeline stage via value-by-value mapping. Amount fields from LegalE transfer as the Nutshell Deal amount. Custom matter fields become Nutshell custom fields on the Deal.

LegalE

Matter Stage / Status

maps to

Nutshell

Deal Stage

1:1
Fully supported

LegalE matter status values (e.g., Intake, Active, Pending, Closed) map to Nutshell Deal stage values. Each LegalE status string requires a corresponding Nutshell stage to be created or mapped to an existing stage. Probability and forecast category re-applied from Nutshell's stage configuration.

LegalE

Note / Document

maps to

Nutshell

Note / File

1:1
Fully supported

LegalE notes attached to contacts or matters transfer as Nutshell Notes (text body) or Files (attachments). Text notes with original create dates and owner attribution land as Nutshell Note records. File attachments (PDFs, documents) re-upload to Nutshell's Files entity linked to the corresponding Person or Deal.

LegalE

Task / Activity

maps to

Nutshell

Task

1:1
Fully supported

LegalE tasks and activities map to Nutshell Tasks. Subject, description, due date, completion status, and owner transfer directly. Original timestamps preserved. Recurring tasks in LegalE map to single Nutshell tasks with the recurrence pattern noted in the description field for manual rebuild.

LegalE

Contact Custom Fields

maps to

Nutshell

Person Custom Fields

1:1
Fully supported

LegalE custom fields on contacts (e.g., bar_number, practice_area, referring_counsel) become Nutshell Person custom fields. Each custom field requires creation in Nutshell Settings > Custom Fields before migration. Field type mapping: LegalE text → Nutshell text, LegalE date → Nutshell date, LegalE pick-list → Nutshell pick-list with corresponding options.

LegalE

Matter Custom Fields

maps to

Nutshell

Deal Custom Fields

1:1
Fully supported

LegalE custom fields on matters (e.g., matter_type, billing_arrangement, court_division) become Nutshell Deal custom fields. Requires pre-creation in Nutshell. Multi-value pick-lists in LegalE are flattened to comma-separated strings in Nutshell unless a custom multi-select field is available. If your Nutshell plan supports multi-select fields, FlitStack will attempt to preserve the original multiple selections during migration.

LegalE

Owner / Assigned User

maps to

Nutshell

Owner (User)

1:1
Fully supported

LegalE owner IDs resolve by email match against Nutshell users. Unmatched owners are flagged before migration — your team either creates Nutshell user accounts first or assigns records to a fallback owner. This is critical for matter assignments. Ensuring all owners are mapped prevents orphaned cases and maintains accountability after go-live.

LegalE

Contact-Company Association

maps to

Nutshell

Person-Company Link

1:1
Fully supported

LegalE contacts linked to companies map to Nutshell's person-company association. Nutshell allows one primary company per person with the option to add secondary company relationships. The primary company defaults to the most recently modified association in LegalE. If a contact has multiple company links, FlitStack preserves the most recent link as the primary and notes the others for manual review.

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.

LegalE logo

LegalE gotchas

High

Public technical documentation is sparse

Medium

Per-matter pricing makes historical-data scope matter

Medium

Document attachments require a separate retrieval path

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

  • LegalE custom fields require pre-creation in Nutshell before data lands

    Nutshell's custom field model requires each custom field to be created in Settings > Custom Fields before any data is imported into that field. LegalE setups with more than 10 custom fields on contacts or matters need those fields created in Nutshell first — field type must match (text, number, date, pick-list). If a LegalE pick-list has an option that doesn't exist in Nutshell, FlitStack creates it during migration setup. This is a planning step, not an automation step — the Nutshell admin must configure the field types and option lists before the migration runs.

  • LegalE matter-stage to Nutshell deal-stage value mapping requires manual decisions

    LegalE matter status values (e.g., Intake, Active, Under Review, Closed Won) have no direct Nutshell equivalents — each must be mapped to a specific Nutshell Deal stage. If Nutshell does not have a matching stage, one must be created before migration. FlitStack surfaces the value-mapping plan during the sample migration phase so your team can decide which LegalE statuses map to which Nutshell stages and what the probability weighting should be. Stage mapping errors at this step produce incorrect deal pipeline views in Nutshell after go-live.

  • LegalE note attachments do not auto-link in Nutshell — manual file linking required post-import

    LegalE notes may contain inline file attachments or linked documents. Nutshell stores attachments as Files (separate entity) rather than inline with notes. FlitStack downloads LegalE attachments and re-uploads them to Nutshell Files, then links them to the parent Person or Deal record. Large attachments (>25MB) may be excluded or require alternative handling. The file association is preserved via Nutshell's file linking API, but your team should spot-check attachment counts in Nutshell's Files section after migration.

  • LegalE's per-page API pagination at 100 records requires iterative fetching

    LegalE's REST API returns a maximum of 100 records per page with pagination tokens. Migrating contacts or matters in bulk requires sequential page fetches, which multiplies API call volume. FlitStack handles pagination automatically, but high record counts (>10,000) against LegalE's rate limits extend migration duration. The sample migration run tests LegalE's paginated export speed to calibrate the full run schedule and identify any throttling early. This testing phase helps prevent surprises during the final data transfer.

  • LegalE owner resolution by email fails for deactivated LegalE users

    Nutshell's owner field requires a valid Nutshell user account. LegalE owner assignments for deactivated or archived users cannot resolve to a Nutshell user by email match. FlitStack flags these records during the pre-flight owner resolution step. Your team must either create Nutshell accounts for those users or reassign their LegalE records to an active user before the migration runs. Records without a resolvable owner land in a fallback queue and require post-migration manual assignment.

Migration approach

Six steps for a successful LegalE to Nutshell data migration

  1. Audit LegalE data and create Nutshell custom fields

    FlitStack extracts a full schema inventory from LegalE — all custom field names, types, and pick-list options. We compare that schema against Nutshell's existing custom field configuration and identify gaps. You or your Nutshell admin create the missing custom fields in Settings > Custom Fields before data moves. This step prevents field-not-found errors during the import phase. FlitStack delivers a custom-field creation checklist with exact field names, types, and pick-list values to enter.

  2. Map LegalE matter stages to Nutshell deal stages

    FlitStack extracts all LegalE matter status values and presents a value-mapping plan. Your team reviews and approves which LegalE statuses map to which Nutshell pipeline stages, including probability weights per stage. New Nutshell stages are created during this step if no suitable existing stage exists. FlitStack documents the mapping in the migration plan before any data is moved. This mapping ensures accurate pipeline reporting from day one in Nutshell.

  3. Resolve owners and run a sample migration

    LegalE owner IDs are matched against Nutshell user email addresses. FlitStack generates an owner resolution report listing matched users, unmatched users, and the record count affected by each. Unmatched owners require Nutshell account creation or record reassignment before the full migration runs. A representative slice of LegalE data (typically 100–500 records) migrates first — FlitStack generates a field-level diff comparing source LegalE values against the Nutshell records so you can verify mapping accuracy before the full run.

  4. Run full migration with delta-pickup window

    The full migration moves all LegalE people, companies, matters, notes, tasks, and custom field values into Nutshell. A delta-pickup window of 24–48 hours after the initial load captures any LegalE records created or modified during cutover. FlitStack uses Nutshell's JSON-RPC API with Basic auth and API token to write records in batched pages, respecting rate limit guidance. Audit logging captures every operation; a reconciliation report compares LegalE source counts against Nutshell destination counts by record type.

  5. Validate, hand off, and rebuild automations

    After migration, FlitStack delivers a validation report showing record counts by type, custom field fill rates, owner assignment completeness, and attachment link verification. Your team spot-checks Nutshell pipeline views, person records, and deal stages against LegalE reports. FlitStack exports LegalE workflow definitions as a rebuild reference for your Nutshell admin to reconstruct in Nutshell's automation tools. One-click rollback is available if reconciliation identifies critical gaps requiring a re-run.

Platform deep dives

Context on both ends of the pair

LegalE logo

LegalE

Source

Strengths

  • Vertical focus on in-house and corporate legal — workflows fit legal departments better than horizontal CRM.
  • Web-based access without per-device install.
  • Document templating aligned to corporate legal use cases.
  • Flexible per-matter and per-user pricing model.
  • Direct vendor relationship typical of smaller-vendor engagements.

Weaknesses

  • Limited third-party reviewer footprint.
  • Pricing and feature breakdowns not publicly published.
  • Narrow native integration catalogue.
  • Reporting depth trails larger ELM platforms.
  • Mobile experience is functional but not differentiating.
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. 1 of 8 objects need a manual workaround.

C

Overall complexity

Moderate migration

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

  • Object compatibility

    C

    1 of 8 objects need a manual workaround.

  • 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

    LegalE: Not publicly documented..

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most LegalE-to-Nutshell migrations complete in 2–4 days of clock time for under 10,000 total records (contacts, companies, matters). LegalE's 100-record-per-page API pagination extends the extraction phase for larger datasets; migrations over 50,000 records extend to 5–8 days. Custom field count and matter-stage mapping complexity are the longest planning steps before data movement begins. The actual migration clock time is independent of your team's working hours, as FlitStack runs the process in the background.

Adjacent paths

Related migrations to explore

Ready when you are

Move from LegalE.
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