CRM migration
Field-level mapping, validation, and rollback between The Attorney Case File and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
The Attorney Case File
Source
Nutshell
Destination
Compatibility
11 of 12
objects map 1:1 between The Attorney Case File and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
The Attorney Case File structures work around matters, client workbooks, and court-specific fields — a data model tuned for legal practice management. Nutshell structures work around People, Companies, Leads, and Deals — a data model tuned for sales pipeline management. The two platforms share a contact-and-company foundation that makes client-name, address, phone, and email migration straightforward, but every legal-native concept (matter number, case status, opposing counsel, court jurisdiction, billing rates, document folders) requires a Nutshell custom field or a note-to-record translation. FlitStack AI runs a scoped-read export against The Attorney Case File API, maps each matter to a Nutshell Deal with a custom field holding the original case number, translates the client workbook as a Person record with all contact details, and re-attaches document references as Nutshell custom fields pointing to re-uploaded files. Workflows, conflict-check rules, court-filing integrations, and billing rate schedules do not migrate — we document them for manual rebuild in Nutshell's automation tools. The migration runs against Nutshell's JSON-RPC API with email-based owner resolution, delta-pickup window during cutover, and a field-level diff before the full run commits.
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 The Attorney Case File 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.
The Attorney Case File
Client / Client Workbook
Nutshell
Person + Company
many:1The Attorney Case File's client workbook combines the client as an individual and the client's organization in one record. We split this into Nutshell Person (individual contact) and Nutshell Company (organization), preserving the primary role as the Person name and the secondary role as a linked Company. If the client is a solo practitioner or individual client, only a Person record is created.
The Attorney Case File
Matter / Case
Nutshell
Deal
1:1Each The Attorney Case File matter maps to a Nutshell Deal. The matter number from The Attorney Case File is stored as a custom text field (Case_Number__c) on the Nutshell Deal so attorneys can reference the original case identifier. The matter name becomes the Deal name, and the matter's current stage is translated to a Nutshell custom pick-list field (Case_Status__c) since Nutshell's native stage field is sales-pipeline oriented.
The Attorney Case File
Opposing Counsel / Co-Counsel
Nutshell
Person
1:1Opposing counsel, co-counsel, and third-party contacts from The Attorney Case File matter parties list migrate as Nutshell Person records with a custom field (Contact_Role__c) set to 'Opposing Counsel', 'Co-Counsel', or the relevant label. These are linked to the same Deal that represents the matter.
The Attorney Case File
Court / Jurisdiction
Nutshell
Custom Field on Deal
1:1The Attorney Case File stores court name and jurisdiction per matter. Since Nutshell has no native court or jurisdiction field, we create a custom text field (Court_Jurisdiction__c) on the Deal record and populate it with the court name. This field is displayed on the Deal record for reference during case management in Nutshell.
The Attorney Case File
Case Notes / Attorney Notes
Nutshell
Note on Deal / Person
1:1The Attorney Case File's case notes (attorney work summaries, procedural notes) migrate as Nutshell Notes attached to the corresponding Deal. We preserve the original author and create timestamp by setting the Note title to the matter name and the Note body to the full note content. For notes belonging to a client rather than a matter, the Note attaches to the Person record.
The Attorney Case File
Document / File Attachment
Nutshell
Nutshell Custom Field + External Storage Reference
1:1The Attorney Case File stores documents within matter folders. Nutshell attaches files directly to records (25 MB per file limit). We export each document, re-upload it to the linked Nutshell Deal record, and write the original folder path to a custom text field (Original_Folder_Path__c) on the Deal so the firm can re-establish its folder hierarchy in Nutshell or a connected document storage tool.
The Attorney Case File
Billing / Time Entry
Nutshell
Custom Fields on Deal (Reference Only)
1:1The Attorney Case File tracks time entries, billing rates, and invoices per matter. Nutshell has no native billing or time-tracking module. We preserve the total billed amount, total hours, and last invoice date as read-only custom fields on the Deal for historical reference, but the billing workflow must be rebuilt in a dedicated legal billing tool post-migration.
The Attorney Case File
Custom Matter Fields / Practice-Area Fields
Nutshell
Custom Fields on Deal / Person
1:1The Attorney Case File allows per-practice-area custom fields (e.g., immigration case type, bankruptcy chapter, litigation damages claimed). We map each to a Nutshell custom field on the appropriate object (Deal or Person) with the same data type. Pick-list fields map to Nutshell dropdown custom fields with the original values preserved.
The Attorney Case File
Workflow / Conflict Check Sequence
Nutshell
Not Migrated — Documented for Manual Rebuild
1:1The Attorney Case File's conflict-check sequences and matter-intake workflows are legal-automation constructs with no Nutshell equivalent. We export the workflow definitions as a structured document and provide a rebuild guide for Nutshell's automation features and any third-party workflow tools the firm adopts.
The Attorney Case File
User / Attorney Owner
Nutshell
Nutshell User (email resolution)
1:1The Attorney Case File assigns attorneys and staff to matters. Owner resolution maps by email match against Nutshell users. Unmatched owners are flagged before migration — the firm either creates the Nutshell user account first or assigns records to a designated fallback user. No record lands without a Nutshell owner.
The Attorney Case File
Activity (Calls, Emails, Meetings)
Nutshell
Nutshell Activity
1:1The Attorney Case File logs phone calls, emails, and meetings per matter or per client. These migrate as Nutshell Activities linked to the appropriate Deal or Person record. Original timestamps and the attorney/staff owner are preserved. Note that Nutshell's activity model is simpler than a full legal billing log — billable time entries remain in The Attorney Case File's billing module.
The Attorney Case File
Lead / Prospect Contact
Nutshell
Nutshell Lead
1:1Any prospective client records in The Attorney Case File that are not yet opened as matters migrate as Nutshell Lead records. The Lead captures the contact name, email, phone, source of referral, and any notes. Once the firm opens a matter, the Lead is converted to a Person record linked to the new Deal.
| The Attorney Case File | Nutshell | Compatibility | |
|---|---|---|---|
| Client / Client Workbook | Person + Companymany:1 | Fully supported | |
| Matter / Case | Deal1:1 | Fully supported | |
| Opposing Counsel / Co-Counsel | Person1:1 | Fully supported | |
| Court / Jurisdiction | Custom Field on Deal1:1 | Fully supported | |
| Case Notes / Attorney Notes | Note on Deal / Person1:1 | Fully supported | |
| Document / File Attachment | Nutshell Custom Field + External Storage Reference1:1 | Fully supported | |
| Billing / Time Entry | Custom Fields on Deal (Reference Only)1:1 | Fully supported | |
| Custom Matter Fields / Practice-Area Fields | Custom Fields on Deal / Person1:1 | Fully supported | |
| Workflow / Conflict Check Sequence | Not Migrated — Documented for Manual Rebuild1:1 | Fully supported | |
| User / Attorney Owner | Nutshell User (email resolution)1:1 | Fully supported | |
| Activity (Calls, Emails, Meetings) | Nutshell Activity1:1 | Fully supported | |
| Lead / Prospect Contact | Nutshell Lead1: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.
The Attorney Case File gotchas
No public API — extraction requires vendor coordination
Export envelope is limited to workbook-level records
Trust accounting data is outside the export scope
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
Scope the export and map The Attorney Case File data model to Nutshell schema
FlitStack AI begins by connecting to The Attorney Case File API using scoped read access to extract all matters, client workbook records, contacts, activities, and document metadata. We generate a pre-migration schema map showing every source field and its Nutshell destination — both the direct mappings (client name, email, phone) and the custom fields required for legal-native concepts (case number, court jurisdiction, practice area, opposing party). Your firm's administrator reviews and approves the map before any data moves. At this stage we also identify records with missing required fields and contacts with duplicate email addresses that need resolution.
Create Nutshell custom fields and resolve user ownership
Before the migration run, your Nutshell administrator creates the custom fields identified in the schema map: Case_Number__c, Court_Jurisdiction__c, Practice_Area__c, Case_Status__c, Contact_Role__c, and any practice-area-specific fields from The Attorney Case File. We simultaneously resolve attorney and staff ownership by matching The Attorney Case File user emails against Nutshell user accounts. Any unmatched owners are flagged so your team can create Nutshell accounts or assign records to a fallback owner. No record migrates without a resolved owner.
Migrate companies and persons first, then matters, then activities
Nutshell requires the parent object to exist before records referencing it. We sequence the migration: Companies first, then Persons linked to those Companies, then Matters (Deals) linked to the primary Person, then Activities linked to the appropriate Person or Deal. Opposing counsel, co-counsel, and third-party contacts are created as Person records with Contact_Role__c populated and linked to the corresponding Matter Deal. This ordering respects Nutshell's foreign-key constraints and prevents orphaned records.
Run sample migration with field-level diff
A representative slice migrates first — typically 50–200 records spanning a mix of open matters, closed matters, multi-party contacts, and documents. We generate a field-level diff between the source and destination showing every field that populated, every field that defaulted to a fallback value, and any custom field that did not resolve. You verify the Case_Number__c, Court_Jurisdiction__c, and custom stage mapping before the full run proceeds. This sample run also validates that document re-uploads fit within Nutshell's file size limits.
Cut over with delta-pickup and post-migration reconciliation
The full migration runs against Nutshell's JSON-RPC API. Your team continues working in The Attorney Case File during the migration window. A delta-pickup window (24–48 hours after the full run completes) captures any matters opened or contacts modified during cutover. We deliver an audit log of every record created, updated, or skipped, plus a reconciliation report comparing source record counts against Nutshell record counts by object. One-click rollback is available if reconciliation finds a material discrepancy. Post-migration, we provide the workflow export document and rebuild guide for your team to re-implement conflict-check and matter-intake logic in Nutshell's automation layer.
Platform deep dives
The Attorney Case File
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 The Attorney Case File 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
The Attorney Case File: Not publicly documented.
Data volume sensitivity
The Attorney Case File 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 The Attorney Case File to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your The Attorney Case File 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 The Attorney Case File
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.