CRM migration

Migrate from My Legal Software to Nutshell

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 logo

My Legal Software

Source

Nutshell

Destination

Nutshell logo

Compatibility

92%

12 of 13

objects map 1:1 between My Legal Software and Nutshell.

Complexity

BStandard

Timeline

48–96 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

My Legal Software logo

My Legal Software

What's pushing teams away

  • Session timeouts occur without warning during active use, causing attorneys to lose unsaved case notes and form entries mid-session, which reviewers flag as a recurring frustration.
  • Pricing is not published on the website and requires contacting sales for a custom quote, making it difficult to assess total cost of ownership during the migration planning phase.
  • Advanced users report that the platform lacks depth in complex practice areas and customization options compared to purpose-built tools for larger or specialized law firms.

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 My Legal Software objects map to Nutshell

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)

maps to

Nutshell

Person

1:1
Fully supported

My 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)

maps to

Nutshell

Account

1:1
Fully supported

My 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

maps to

Nutshell

Deal

1:1
Fully supported

Each 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

maps to

Nutshell

Deal Stage

1:1
Fully supported

My 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

maps to

Nutshell

Note (on Person or Deal)

1:1
Fully supported

Billable 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

maps to

Nutshell

Lead

1:many
Fully supported

My 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

maps to

Nutshell

Event

1:1
Fully supported

My 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

maps to

Nutshell

File (attached to Person or Deal)

1:1
Fully supported

Documents 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)

maps to

Nutshell

Custom Field (Deal-Level)

1:1
Fully supported

My 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)

maps to

Nutshell

Custom Field (Person or Account Level)

1:1
Fully supported

Client-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

maps to

Nutshell

Not Migrated

1:1
Fully supported

My 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

maps to

Nutshell

Note (on Deal)

1:1
Fully supported

My 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

maps to

Nutshell

User (matched by email)

1:1
Fully supported

My 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.

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.

My Legal Software logo

My Legal Software gotchas

Medium

Unexpected session timeouts cause lost unsaved work

Medium

Pricing requires sales contact and is not published

Low

Multi-year billing and trust records may reference inactive Case IDs

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

  • Matter-to-Deal association requires client records to exist first

    Nutshell's Deal record requires a valid personId or accountId lookup before it can be saved. My Legal Software matters are often created before or alongside their associated client records, which means the matter-to-client foreign key may not resolve at migration time if we process matters first. We sequence the migration to load all People and Accounts first, then create Deals with resolved personId/accountId lookups. Circular or missing client references are flagged for manual resolution before the full run commits.

  • Nutshell API rate limits on large find() requests affect batch migration speed

    Nutshell's JSON-RPC API rate-limits find() requests that return non-stub responses. Migration batches of 500–1,000 records are the practical ceiling per request cycle. For My Legal Software databases with 50,000+ matter records, this rate-limit ceiling extends total migration clock time beyond the 48-hour target into the 72–96-hour range. We implement exponential backoff and batch-splitting to stay within rate limits without losing records, but migration duration estimates account for this constraint explicitly.

  • File attachments exceeding 25 MB must be handled separately from bulk migration

    Nutshell's file API enforces a 25 MB per-file upload limit. My Legal Software document repositories may contain depositions, discovery packets, or scanned briefs that exceed this threshold. We pre-scan file sizes during the sample migration phase and flag oversized files. These files require manual upload to Nutshell or an alternative document storage solution post-migration — we provide a file inventory report listing each oversized document, its source path, and its associated matter for your team to handle.

  • Billing and invoice records have no native Nutshell equivalent

    My Legal Software integrates billing, trust accounting, and invoicing natively. Nutshell is a CRM with no accounting or billing module. Invoice headers, totals, and payment status from My Legal Software can be preserved as formatted Notes on the related Deal, but they do not become a native Nutshell object. You will need to retain access to My Legal Software for billing lookup, export invoices as PDFs, or implement a separate accounting tool. We include an invoice-summary note template in the migration plan so billable history is not lost.

  • Document folder hierarchy does not transfer — files land in a flat attachment list

    My Legal Software organizes documents in matter-specific folder structures (pleadings/, correspondence/, discovery/). Nutshell attaches files directly to a Person or Deal record with no folder nesting. After migration, your team will need to locate documents by searching the file list on the relevant record or by using Nutshell's global file search. We cannot replicate the source folder hierarchy within Nutshell's flat attachment model. Consider tagging files with matter identifiers or practice-area labels in Nutshell to restore some organizational context post-migration.

Migration approach

Six steps for a successful My Legal Software to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

My Legal Software logo

My Legal Software

Source

Strengths

  • Consolidates case management, billing, document storage, and marketing into a single integrated platform.
  • User-friendly interface consistently praised by small firm reviewers for ease of adoption and daily use.
  • Built-in client communication portal and case notes sharing reduce reliance on external collaboration tools.
  • Responsive customer service with high satisfaction scores on third-party review platforms.
  • Flexible storage allows uploading files without strict size limits per the G2 review data.

Weaknesses

  • Session timeouts occur without warning, risking loss of unsaved work during active sessions.
  • Pricing model is opaque and requires contacting sales, complicating budget forecasting.
  • Platform is best suited for smaller firms and lacks the depth required by complex or large-scale practices.
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?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across My Legal Software and Nutshell.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • 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

    My Legal Software: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your My Legal Software 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 My Legal Software to Nutshell data migrations

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

Can't find your answer?

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 consultation

Most My Legal Software to Nutshell migrations complete in 48–96 hours of clock time for databases under 25,000 records. Larger setups with 100,000+ matter records, extensive time-tracking tables, or many custom fields extend to 5–10 days. Nutshell's API rate limits on large find() requests are the primary variable affecting speed — we batch and paginate to stay within limits without losing records.

Adjacent paths

Related migrations to explore

Ready when you are

Move from My Legal Software.
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