CRM migration

Migrate from Legal Files to Nutshell

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

Legal Files logo

Legal Files

Source

Nutshell

Destination

Nutshell logo

Compatibility

85%

11 of 13

objects map 1:1 between Legal Files and Nutshell.

Complexity

BStandard

Timeline

24–48 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Legal Files organizes around matters, parties, documents, and deadlines. Nutshell organizes around People, Companies, Deals, and Activities. The core migration challenge is that Legal Files is matter-centric — every record is anchored to a case — while Nutshell is person-centric — every record is anchored to a contact or company. FlitStack AI maps each Legal Files party to a Nutshell Person, each Legal Files matter to a Nutshell Deal, and each Legal Files company contact to a Nutshell Company. Legal Files custom fields (case_type, party_role, responsible_attorney, opposing_counsel, court, judge) have no native Nutshell equivalent; we create Nutshell custom fields before migration and route each field to the correct object. The migration extracts from Legal Files via database export, transforms field names and values to match Nutshell's API schema, and loads via Nutshell's JSON-RPC API respecting rate limits. Activities, notes, and attachments migrate as records and notes. Workflows, sequences, automations, and integrations do not migrate — these must be rebuilt in Nutshell's automation tools and reconfigured in Nutshell's integration settings.

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

Legal Files logo

Legal Files

What's pushing teams away

  • Reviewer feedback consistently flags the UI as 'outdated' and notes the platform 'may work better with Windows than Mac' — modern Mac-first in-house teams find this friction-heavy.
  • Initial learning curve is described as tricky; onboarding new users takes more time than reviewers expect from a 2020s SaaS product.
  • Enterprise pricing model ($100/user/month + $49/month base fee, billed annually) becomes expensive at scale and lacks transparent lower tiers for smaller teams.
  • Modern integration ecosystem is narrower than newer competitors — packaged connectors to popular SaaS tools are limited compared to native cloud-first platforms.
  • Primary value proposition skews to centralized matter management rather than collaborative or AI-driven workflows, so teams chasing AI demand drafting or generative review features migrate away.

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

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

Legal Files

Party

maps to

Nutshell

Person

1:1
Fully supported

Each Legal Files party becomes a Nutshell Person. Legal Files party_role (Plaintiff, Defendant, Witness, etc.) has no native Nutshell equivalent — we create a custom pick-list field Party_Role__c on Nutshell Person before migration and preserve the role value. Legal Files party_type (Individual or Organization) determines whether the record routes to Nutshell Person or Nutshell Company.

Legal Files

Company Contact (Party with party_type = Organization)

maps to

Nutshell

Company

1:many
Fully supported

Legal Files parties of type Organization split into Nutshell Company records. The organization's name maps to Nutshell Company name. Contact-level fields (primary_email, primary_phone) map to Nutshell custom fields on the Company. Multiple party contacts from the same organization consolidate to one Nutshell Company.

Legal Files

Matter

maps to

Nutshell

Deal

1:1
Fully supported

Each Legal Files matter becomes a Nutshell Deal. The matter_number becomes the Nutshell Deal name (or we concatenate matter_number + matter_description for clarity). Legal Files matter status (Active, Pending, Closed) maps to a Nutshell pipeline stage. All remaining legal fields — case_type, responsible_attorney, opposing_counsel, court, judge — are custom fields on the Deal.

Legal Files

Activity / Calendar Event

maps to

Nutshell

Activity

1:1
Fully supported

Legal Files calendar events and scheduled tasks migrate as Nutshell Activities. Event subject maps to Nutshell Activity subject. Event date maps to the Activity date field. Event description maps to a custom field or the Activity notes. Original owners resolved by email match to Nutshell users. Recurring events split into individual Activity records.

Legal Files

Document / File Attachment

maps to

Nutshell

Note (on related record)

1:1
Fully supported

Legal Files documents and file attachments on parties and matters do not migrate as native files to Nutshell (Nutshell has no built-in document management). We create a Nutshell Note on the related Person or Deal with the document filename, original file path, and a link to the re-uploaded document in your destination storage. The file itself must be re-uploaded to cloud storage (SharePoint, Google Drive, Dropbox) and linked from the Note.

Legal Files

Custom Fields (Parties, Companies, Matters)

maps to

Nutshell

Custom Fields (Person, Company, Deal)

1:1
Fully supported

Legal Files custom fields (case_type, party_role, responsible_attorney, opposing_counsel, court, judge, billing_contact, case_number) have no native Nutshell equivalent. We create each as a Nutshell custom field on the appropriate object (Person, Company, or Deal) before migration, preserving field type (pick-list, text, date, number). Custom pick-list values are mapped value-by-value to Nutshell pick-list options.

Legal Files

Matter Party Relationship

maps to

Nutshell

Deal linked to Person

many:1
Fully supported

Legal Files allows a party to have multiple roles across multiple matters (one party, many matters). Nutshell Deals link to People via a simple association. For each Legal Files matter-party relationship, we link the migrated Nutshell Person to the migrated Nutshell Deal. If a party has multiple roles, we store each role as a separate Deal-Person link via custom field routing.

Legal Files

Party Role

maps to

Nutshell

Custom Field (Party_Role__c on Person)

1:1
Fully supported

Legal Files party roles (Plaintiff, Defendant, Opposing Counsel, Co-Counsel, Witness, Expert, Mediator, Arbitrator, etc.) are a legal-specific field with no Nutshell equivalent. We create a Nutshell custom pick-list field Party_Role__c on the Person object and map each Legal Files role value to the corresponding Nutshell pick-list option. Parties with multiple roles are handled via multiple Person-Deal links or a multi-select custom field.

Legal Files

Matter Type / Case Category

maps to

Nutshell

Custom Field (Case_Type__c on Deal)

1:1
Fully supported

Legal Files categorizes matters by type (Litigation, Corporate, Real Estate, Intellectual Property, Family Law, Bankruptcy, etc.). Nutshell has no native case type field. We create a Nutshell custom pick-list field Case_Type__c on the Deal object, define the pick-list values to match Legal Files, and map each matter's type value. Stage names in Legal Files map to Nutshell Deal pipeline stages, preserving the original stageentered timestamp.

Legal Files

File Attachments on Matter or Party

maps to

Nutshell

External Storage + Note

1:1
Fully supported

Legal Files documents, PDFs, word files, and email attachments stored in the document repository are exported as files. We create Nutshell Notes on the target record (Person or Deal) referencing each document by name and original path. Your team re-uploads the documents to a connected storage system (SharePoint, Google Drive, Box) and updates the Note with the new link. This preserves traceability without requiring Nutshell's native file storage to handle legal-sized document volumes.

Legal Files

Microsoft Office / Outlook Integration

maps to

Nutshell

Not Migrated

1:1
Fully supported

Legal Files' Microsoft Outlook integration (email filing directly to matters, calendar sync) has no Nutshell equivalent. These integrations must be disconnected in Legal Files before migration and reconfigured in Nutshell using Nutshell's native Google Workspace and Microsoft 365 integrations, available in the Nutshell AppConnect marketplace. Email-to-case routing, if used in Legal Files, must be rebuilt using Nutshell's email sync settings.

Legal Files

Workflows and Automations

maps to

Nutshell

Not Migrated

1:1
Fully supported

Legal Files workflows, matter intake forms, approval chains, and deadline escalation rules do not migrate. They must be rebuilt in Nutshell's automation tools (Nutshell Sequences, Workflow Rules). We export your Legal Files workflow definitions as a reference document listing each rule's trigger, conditions, and actions so your Nutshell admin can rebuild them. This export is delivered alongside the migration data map.

Legal Files

Source System ID

maps to

Nutshell

Custom Field (Source_System_ID__c)

1:1
Fully supported

Each Legal Files record carries an internal ID. We store this as a custom text field Source_System_ID__c on the Nutshell record (Person, Company, or Deal) for traceability. The source ID enables delta-run de-duplication, audit logging, and rollback reference if reconciliation fails. Original created_date from Legal Files is preserved as a custom datetime field Created_In_Source__c on the target Nutshell record.

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.

Legal Files logo

Legal Files gotchas

High

No API — migration requires direct SQL Server database access

High

Document file transfer is separate from database migration

Medium

Email routing rules do not auto-migrate

Medium

Custom field discovery requires schema inspection

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-party relationships are many-to-many in Legal Files but simpler in Nutshell

    Legal Files allows a single party to appear in multiple matters with different roles in each — a party can be a Plaintiff in one case and a Defendant in another. Nutshell's Deal-Person link model is one-to-many per deal (one Person linked to one Deal) with no native way to carry per-matter role context. We handle this by creating a Party_Role__c custom field on Nutshell Person that stores the role for each specific matter-party link, using a multi-select pick-list for parties with multiple roles across matters. This preserves the relationship context without requiring a custom junction object.

  • Custom fields must be created in Nutshell before field mapping can be validated

    Legal Files custom fields like case_type, party_role, responsible_attorney, opposing_counsel, court, and judge have no native Nutshell equivalent. These require Nutshell custom field creation before any migration run. If the custom fields are not created and mapped in advance, the field-level diff will flag unmapped fields and the migration will pause. We deliver a custom field creation checklist as part of the pre-migration plan so Nutshell's schema is ready before data moves.

  • Document repository does not migrate as native files

    Legal Files stores documents in an integrated document repository linked to matters and parties. Nutshell has no built-in document management system — file attachments are stored directly on records with a 25MB per-file limit. We export the document repository, create Nutshell Notes on the target Person or Deal referencing each file by name and original path, and flag files that exceed Nutshell's size limit. Your team must re-upload documents to external storage (SharePoint, Google Drive, Box) and update the Note with the live link.

  • Legal Files workflows have no migration path and must be rebuilt

    Legal Files matter intake workflows, approval routing rules, deadline escalation triggers, and automated task generation are built on Legal Files' workflow engine. Nutshell has no equivalent engine for legal matter workflows — it has sales automation and email sequences, not case intake forms or approval chains. We export your Legal Files workflow definitions as a structured reference document, but every workflow must be rebuilt in Nutshell manually or with Nutshell's automation tools.

  • Nutshell's JSON-RPC API has rate limits that affect large migrations

    Nutshell's API is accessible via JSON-RPC over HTTPS and imposes rate limits on requests per minute. For large Legal Files migrations with 50,000+ records, the migration tool must implement request throttling and exponential backoff to avoid 429 errors. We configure the migration pipeline to respect Nutshell's rate limits, adding retry logic for throttled requests. This extends the migration window for large datasets but prevents API lockout that would require manual intervention.

Migration approach

Six steps for a successful Legal Files to Nutshell data migration

  1. Extract and profile Legal Files data

    FlitStack AI connects to your Legal Files database (SQL Server) or processes your Legal Files export. We extract all parties, company contacts, matters, activities, document references, and custom field definitions. We profile the data to understand field types, identify custom fields, and surface data quality issues such as duplicate parties, missing required fields, and matter-party relationship cardinality. This profiling generates the migration plan, custom field creation checklist, and data quality report before any transformation begins.

  2. Build Nutshell custom fields and pipeline stages

    Before data moves, your Nutshell admin creates the custom fields identified in the profiling step: Party_Role__c, Party_Type__c, Case_Type__c, Responsible_Attorney__c, Opposing_Counsel__c, Court__c, Judge__c, Filing_Date__c, Next_Hearing_Date__c, Source_System_ID__c, and Created_In_Source__c. We deliver a step-by-step setup checklist listing each field name, type, and which Nutshell object (Person, Company, Deal) it belongs to. Legal Files pipeline stages map to Nutshell Deal pipeline stages — your admin configures the pipeline stages in Nutshell before migration runs.

  3. Create mapping plan and run sample migration

    We generate the full field mapping plan mapping every Legal Files field to its Nutshell equivalent, including custom field routing, party-type split logic (Organization parties route to Company; Individual parties route to Person), and matter-party link creation. We run a sample migration with a representative slice of 50–100 records — typically 20 parties, 10 company contacts, and 15 matters — and produce a field-level diff so you can verify the mapping before the full run. Any field mapping corrections are made before the full migration commits.

  4. Run full migration respecting Nutshell API rate limits

    The full migration loads all Legal Files parties, company contacts, and matters into Nutshell via the JSON-RPC API, with request throttling to respect rate limits. Records load in the correct sequence: Companies first (since company contacts depend on them), then People, then Deals (since they link to People). Activities load after Deals to maintain parent-record references. Custom fields and source system IDs are populated during the load. Duplicate detection via source_system_id prevents double-importing records that were created in Legal Files during the sample run.

  5. Delta-pickup window and final reconciliation

    A 24–48 hour delta-pickup window captures any parties, company contacts, or matters created or modified in Legal Files during the cutover. We run a final reconciliation comparing Legal Files record counts and field values against Nutshell, producing a mismatch report flagging any records that did not migrate cleanly. If reconciliation fails for any record type, one-click rollback reverts the Nutshell data to the pre-migration state. We deliver the migration audit log, field mapping reference, workflow export document, and document re-upload checklist in a handover package.

Platform deep dives

Context on both ends of the pair

Legal Files logo

Legal Files

Source

Strengths

  • Fully on-premise with data stored directly in Microsoft SQL Server, giving firms complete control over their database
  • Highly customizable by firm administrators without requiring developer assistance
  • Direct Microsoft Outlook email saving into case files is a workflow feature praised across reviews
  • iPad app available for attorneys working outside the office
  • Supports complex litigation case structures with deep matter hierarchies

Weaknesses

  • No public REST API — all data access requires direct SQL Server database queries
  • Desktop-first architecture means no native cloud sync or SaaS deployment model
  • Limited modern integrations compared to cloud-first competitors like Clio
  • Legacy UI is cited less favorably than newer alternatives on modern review platforms
  • Pricing is opaque and requires direct vendor contact, suggesting enterprise-level cost
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. 3 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 Legal Files and Nutshell.

  • Object compatibility

    B

    3 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

    Legal Files: Not applicable — no public API exposed.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Legal Files to Nutshell migrations complete in 24–48 hours for setups under 5,000 records with fewer than 10 custom fields. Larger Legal Files databases with 50,000+ records, extensive custom field schemas (20+ fields), or complex matter-party relationships extend to 5–10 days. Nutshell's API rate limits affect the migration speed for large datasets — the delta-pickup window adds 24–48 hours on top of the initial migration run.

Adjacent paths

Related migrations to explore

Ready when you are

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