CRM migration
Field-level mapping, validation, and rollback between My Legal Software and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
My Legal Software
Source
Nutshell
Destination
Compatibility
12 of 13
objects map 1:1 between My Legal Software and Nutshell.
Complexity
BStandard
Timeline
48–96 hours
Overview
My Legal Software organizes legal work around matters, clients, time entries, billing records, and documents. Nutshell is a sales CRM built around People, Accounts, Leads, and Deals with activity tracking and pipeline stages. The migration restructures a matter-centric data model into a contact-centric CRM without losing client identity or history. We map My Legal Software client records to Nutshell People (individuals) or Accounts (organizations), depending on contact type. Matter records become Nutshell Deals with stage values derived from matter status. Time-tracking entries attach as Notes on the relevant People or Deal record, preserving billable-hour history. Custom fields from My Legal Software — bar-number fields, practice-area tags, referring-attorney references — migrate into Nutshell's custom field system for People, Accounts, or Leads. Workflows, document templates, billing rules, and document-management folder structures do not transfer; those are destination-side configuration. We provide a rebuild reference export so your Nutshell admin can reconstruct automation logic in Nutshell's sequence and task tools. The migration runs via Nutshell's JSON-RPC API using scoped read access on My Legal Software — your team continues working in My Legal Software throughout the cutover. A 24–48-hour delta window captures in-flight changes at go-live.
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 My Legal Software 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.
My Legal Software
Client (Individual)
Nutshell
Person
1:1My Legal Software stores individual clients as named records with contact details. These map 1:1 to Nutshell People. Address, phone, email, and custom fields transfer directly. Owner assignment is resolved by email match against Nutshell users. All standard fields (name, contact info, address components) migrate as-is without transformation. Custom fields attached to the client record also transfer as custom fields on the corresponding Nutshell Person record, preserving field type and values.
My Legal Software
Client (Organization)
Nutshell
Account
1:1My Legal Software organizations — corporate clients, firms, institutions — map to Nutshell Accounts. Organization name, domain/website, industry, and employee-count custom fields migrate as Account fields. Parent-organization hierarchies become Account hierarchy in Nutshell. When a parent company exists in My Legal Software with subsidiary relationships, those hierarchies are preserved as Nutshell Account parent-child relationships, allowing your team to view organizational structure in the CRM.
My Legal Software
Matter / Case
Nutshell
Deal
1:1Each My Legal Software matter becomes a Nutshell Deal. Matter name maps to Deal name. Matter status (Open, Closed, Pending) maps to Nutshell pipeline stage values via value mapping. Client/matter association becomes Deal.PersonId or Deal.AccountId lookup — the client record must exist first in Nutshell.
My Legal Software
Matter Status / Stage
Nutshell
Deal Stage
1:1My Legal Software matter statuses are mapped value-by-value to Nutshell pipeline stage names. A typical mapping: Intake → Appointment Scheduled, Active → Working, Closed Won → Won, Closed Lost → Lost. Your admin confirms stage mapping before the migration commits.
My Legal Software
Time Entry / Billable Hours
Nutshell
Note (on Person or Deal)
1:1Billable time entries are too granular for Nutshell's native object model. We attach time-entry summaries as Notes on the relevant Person or Deal record, preserving date, hours, description, and billing rate as formatted text. Full time-entry detail is preserved; reporting on billable hours post-migration requires a custom field or export.
My Legal Software
Contact / Responsible Attorney
Nutshell
Lead
1:manyMy Legal Software contacts (attorneys, paralegals, referring counsel) who are not clients split into two groups: those who are already clients migrate as People, and those who are prospective referrals route to Nutshell Leads. This split is based on a source-field flag indicating client vs. non-client status.
My Legal Software
Calendar / Appointment
Nutshell
Event
1:1My Legal Software calendar entries migrate as Nutshell Events. Original start/end datetime, description, and owner are preserved. Events are linked to the relevant Person or Deal by name matching. Recurring appointments create individual Event records in Nutshell rather than a single recurring-event reference, meaning each instance appears as a separate calendar entry in the target system.
My Legal Software
Document / File Attachment
Nutshell
File (attached to Person or Deal)
1:1Documents attached to My Legal Software matters are re-uploaded to Nutshell Files and attached to the corresponding Person or Deal record. File size must be under 25 MB per file (Nutshell API limit). Documents exceeding this are flagged before migration. Folder hierarchy does not transfer — files land in a flat attachment list.
My Legal Software
Custom Field (Matter-Level)
Nutshell
Custom Field (Deal-Level)
1:1My Legal Software custom fields defined on matters — such as practice area, case number, referring attorney, or jurisdiction — migrate as Nutshell custom fields on the Deal object. Custom fields must be pre-created in Nutshell Settings before data import; we provide a custom-field creation plan as part of the migration package.
My Legal Software
Custom Field (Client-Level)
Nutshell
Custom Field (Person or Account Level)
1:1Client-level custom fields in My Legal Software — bar number, client type, billing tier — map to custom fields on Nutshell Person (for individuals) or Account (for organizations). Field type (text, picklist, date, number) is preserved during mapping. These custom fields are created in Nutshell Settings before migration, and the migration plan specifies which fields apply to Person vs. Account objects based on client type.
My Legal Software
Workflow / Automation Rule
Nutshell
Not Migrated
1:1My Legal Software workflow automation (matter intake routing, task assignment rules, email triggers) has no direct equivalent in Nutshell. We export the workflow definitions as a JSON reference document your Nutshell admin can use to rebuild logic using Nutshell's sequence automation and task rules.
My Legal Software
Billing / Invoice Record
Nutshell
Note (on Deal)
1:1My Legal Software billing and invoice records do not map to any native Nutshell object. Invoice summaries (invoice number, date, total, status) are attached as formatted Notes on the related Deal. Nutshell does not include billing or accounting features; billing must remain in My Legal Software or a separate accounting tool post-migration.
My Legal Software
User / Attorney Owner
Nutshell
User (matched by email)
1:1My Legal Software users (attorneys, staff) are matched to Nutshell users by email address. Unmatched users are flagged before migration — your team either creates the Nutshell user first or assigns records to a fallback owner. Active/inactive status from My Legal Software is preserved as a Note for admin review.
| My Legal Software | Nutshell | Compatibility | |
|---|---|---|---|
| Client (Individual) | Person1:1 | Fully supported | |
| Client (Organization) | Account1:1 | Fully supported | |
| Matter / Case | Deal1:1 | Fully supported | |
| Matter Status / Stage | Deal Stage1:1 | Fully supported | |
| Time Entry / Billable Hours | Note (on Person or Deal)1:1 | Fully supported | |
| Contact / Responsible Attorney | Lead1:many | Fully supported | |
| Calendar / Appointment | Event1:1 | Fully supported | |
| Document / File Attachment | File (attached to Person or Deal)1:1 | Fully supported | |
| Custom Field (Matter-Level) | Custom Field (Deal-Level)1:1 | Fully supported | |
| Custom Field (Client-Level) | Custom Field (Person or Account Level)1:1 | Fully supported | |
| Workflow / Automation Rule | Not Migrated1:1 | Fully supported | |
| Billing / Invoice Record | Note (on Deal)1:1 | Fully supported | |
| User / Attorney Owner | User (matched by email)1: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.
My Legal Software gotchas
Unexpected session timeouts cause lost unsaved work
Pricing requires sales contact and is not published
Multi-year billing and trust records may reference inactive Case IDs
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
Inventory source data and plan Nutshell schema
We connect to My Legal Software via read-only API access (or export file if API is unavailable) and inventory all clients, matters, time entries, documents, and custom fields. Simultaneously, we review your target Nutshell environment and create a custom-field creation plan so Deal-level, Person-level, and Account-level custom fields are ready before data lands. We also flag oversized file attachments and matter records missing a client reference at this stage.
Resolve users and owners by email
My Legal Software attorney and staff users are matched to Nutshell users by email address. Any user without a corresponding Nutshell account is flagged with the record count affected. Your team creates the Nutshell user, assigns them an email address, or designates a fallback owner before the migration run. No record lands in Nutshell without a resolved owner, ensuring accountability and proper access control from day one.
Load People and Accounts first, then Deals
Nutshell requires Person or Account records to exist before a Deal can reference them via personId or accountId. We sequence the migration: all People and Accounts load first, then Deals are created with resolved lookups. This ordering also ensures that Nutshell's activity and note attachments attach to the correct parent record. Time entries and calendar items follow in a second pass.
Run sample migration with field-level diff
A representative slice — typically 100–300 records covering a mix of individual clients, organizations, matters, and documents — migrates first. We generate a field-level diff comparing source values against Nutshell values so you can verify stage mapping, custom field values, owner resolution, and file attachment integrity before the full run. You approve the sample output or request mapping adjustments at this stage.
Execute full migration with delta-pickup window
The full dataset migrates to Nutshell using batched API calls respecting Nutshell rate limits. After the initial load, a 24–48-hour delta-pickup window captures any records created or modified in My Legal Software during the cutover. An audit log records every operation. If reconciliation fails — record counts, field values, or attachment checks do not match — one-click rollback is available to revert the Nutshell environment to its pre-migration state.
Platform deep dives
My Legal Software
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across My Legal Software and Nutshell.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
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
My Legal Software: Not publicly documented.
Data volume sensitivity
My Legal Software 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 My Legal Software to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your My Legal Software 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 My Legal Software
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.