CRM migration
Field-level mapping, validation, and rollback between Legal Files and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Legal Files
Source
Nutshell
Destination
Compatibility
11 of 13
objects map 1:1 between Legal Files and Nutshell.
Complexity
BStandard
Timeline
24–48 hours
Overview
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.
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 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
Nutshell
Person
1:1Each 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)
Nutshell
Company
1:manyLegal 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
Nutshell
Deal
1:1Each 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
Nutshell
Activity
1:1Legal 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
Nutshell
Note (on related record)
1:1Legal 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)
Nutshell
Custom Fields (Person, Company, Deal)
1:1Legal 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
Nutshell
Deal linked to Person
many:1Legal 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
Nutshell
Custom Field (Party_Role__c on Person)
1:1Legal 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
Nutshell
Custom Field (Case_Type__c on Deal)
1:1Legal 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
Nutshell
External Storage + Note
1:1Legal 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
Nutshell
Not Migrated
1:1Legal 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
Nutshell
Not Migrated
1:1Legal 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
Nutshell
Custom Field (Source_System_ID__c)
1:1Each 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.
| Legal Files | Nutshell | Compatibility | |
|---|---|---|---|
| Party | Person1:1 | Fully supported | |
| Company Contact (Party with party_type = Organization) | Company1:many | Fully supported | |
| Matter | Deal1:1 | Fully supported | |
| Activity / Calendar Event | Activity1:1 | Fully supported | |
| Document / File Attachment | Note (on related record)1:1 | Fully supported | |
| Custom Fields (Parties, Companies, Matters) | Custom Fields (Person, Company, Deal)1:1 | Fully supported | |
| Matter Party Relationship | Deal linked to Personmany:1 | Fully supported | |
| Party Role | Custom Field (Party_Role__c on Person)1:1 | Fully supported | |
| Matter Type / Case Category | Custom Field (Case_Type__c on Deal)1:1 | Fully supported | |
| File Attachments on Matter or Party | External Storage + Note1:1 | Fully supported | |
| Microsoft Office / Outlook Integration | Not Migrated1:1 | Fully supported | |
| Workflows and Automations | Not Migrated1:1 | Fully supported | |
| Source System ID | Custom Field (Source_System_ID__c)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.
Legal Files gotchas
No API — migration requires direct SQL Server database access
Document file transfer is separate from database migration
Email routing rules do not auto-migrate
Custom field discovery requires schema inspection
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
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.
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.
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.
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.
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
Legal Files
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 3 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 Legal Files and Nutshell.
Object compatibility
3 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
Legal Files: Not applicable — no public API exposed.
Data volume sensitivity
Legal Files 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 Legal Files to Nutshell migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Legal Files
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.