CRM migration
Field-level mapping, validation, and rollback between LegalE and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
LegalE
Source
Nutshell
Destination
Compatibility
10 of 10
objects map 1:1 between LegalE and Nutshell.
Complexity
CModerate
Timeline
2–4 days
Overview
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.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a 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
Nutshell
Person
1:1LegalE'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
Nutshell
Company
1:1LegalE 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
Nutshell
Deal
1:1LegalE 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
Nutshell
Deal Stage
1:1LegalE 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
Nutshell
Note / File
1:1LegalE 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
Nutshell
Task
1:1LegalE 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
Nutshell
Person Custom Fields
1:1LegalE 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
Nutshell
Deal Custom Fields
1:1LegalE 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
Nutshell
Owner (User)
1:1LegalE 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
Nutshell
Person-Company Link
1:1LegalE 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.
| LegalE | Nutshell | Compatibility | |
|---|---|---|---|
| Contact / Person | Person1:1 | Fully supported | |
| Company / Organization | Company1:1 | Fully supported | |
| Matter / Case | Deal1:1 | Fully supported | |
| Matter Stage / Status | Deal Stage1:1 | Fully supported | |
| Note / Document | Note / File1:1 | Fully supported | |
| Task / Activity | Task1:1 | Fully supported | |
| Contact Custom Fields | Person Custom Fields1:1 | Fully supported | |
| Matter Custom Fields | Deal Custom Fields1:1 | Fully supported | |
| Owner / Assigned User | Owner (User)1:1 | Fully supported | |
| Contact-Company Association | Person-Company Link1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
LegalE gotchas
Public technical documentation is sparse
Per-matter pricing makes historical-data scope matter
Document attachments require a separate retrieval path
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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
LegalE
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 1 of 8 objects need a manual workaround.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across LegalE and Nutshell.
Object compatibility
1 of 8 objects need a manual workaround.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
LegalE: Not publicly documented..
Data volume sensitivity
LegalE doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during LegalE to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your LegalE to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave LegalE
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.