CRM migration
Field-level mapping, validation, and rollback between Legal Case Tracker and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Legal Case Tracker
Source
Nutshell
Destination
Compatibility
11 of 12
objects map 1:1 between Legal Case Tracker and Nutshell.
Complexity
BStandard
Timeline
24–72 hours
Overview
Legal Case Tracker is a vertical-specific case management tool built around matters, parties, documents, calendars, and expenses for law firms and legal departments. Nutshell is a horizontal CRM organized around Companies, People (contacts), Leads, and Deals (opportunities) with a pipeline view, activity tracking, and custom fields per entity type. The two platforms share a person-and-company data model but diverge significantly on case handling: Legal Case Tracker has dedicated case objects with status workflows, court calendars, and expense logging; Nutshell has no native case object, so legal cases map to Nutshell Deals with a custom Status__c field holding the original case lifecycle values. We extract cases, parties, documents, and custom fields via the source API or structured export, transform case-level metadata into Nutshell Deal fields, re-attach documents to the corresponding Deal record in Nutshell's file storage, and preserve party-role labels as custom fields on the People record. Workflows, calendar rules, and automated reminders do not migrate — Legal Case Tracker's automation logic requires manual rebuild in Nutshell's rule system. The migration mechanism uses API extraction where available, falling back to CSV export with field-level transformation and bulk import into Nutshell's REST API.
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 Case Tracker 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 Case Tracker
Case / Matter
Nutshell
Deal
1:1Cases become Nutshell Deals. The original case number is stored as a custom field (Original_Case_Number__c) on the Deal so teams can cross-reference without renumbering. Case status is mapped to a custom Status__c pick-list field on the Deal, preserving all original status values. If multiple case types exist (litigation, transactional, advisory), each type can be separated into its own Nutshell pipeline via the pipeline feature.
Legal Case Tracker
Party / Contact
Nutshell
Person
1:1Parties on a case (attorneys, opposing counsel, clients, witnesses) map directly to Nutshell People. Role labels — e.g., 'Client', 'Opposing Counsel', 'Expert Witness' — are preserved as a custom Role__c text field on the Person record. Each Person is associated with the corresponding Company record (client organization) via Nutshell's built-in company-person relationship.
Legal Case Tracker
Organization / Client Company
Nutshell
Company
1:1Client organizations on Legal Case Tracker cases map to Nutshell Companies. Company-level fields (name, address, industry) migrate as direct field maps. The Company's Nutshell page becomes the parent record for all Person entries belonging to that client. Parent-child company hierarchies in Legal Case Tracker are preserved using Nutshell's parent-company field.
Legal Case Tracker
Document / File
Nutshell
Deal File Attachment
1:1Documents attached to a case in Legal Case Tracker are downloaded and re-uploaded as file attachments on the corresponding Nutshell Deal. The original file name and uploaded date are preserved in the Nutshell file metadata. Nutshell's 25MB per-file limit is enforced — files exceeding 25MB are flagged and split or linked externally. Role-based document access from Legal Case Tracker cannot be replicated in Nutshell's standard sharing model.
Legal Case Tracker
Calendar / Court Date
Nutshell
Activity (Task / Event)
1:1Court dates and calendar entries from Legal Case Tracker migrate as Nutshell Activities. Hearing dates and filing deadlines map to Tasks with the due date populated from the source. All-day or multi-day events (e.g., trial dates) map to Nutshell Events with start and end times. Nutshell's activity model does not support legal-specific recurrence rules — complex recurring court dates require manual review post-migration.
Legal Case Tracker
Expense
Nutshell
Activity Note / Custom Field on Deal
1:manyLegal Case Tracker expenses (filing fees, court costs, expert witness fees) are split: the total expense amount per case is stored as a custom currency field (Total_Expenses__c) on the Nutshell Deal, and the expense line items are preserved as a formatted Note attached to the Deal for audit trail purposes. Detailed expense reporting is better handled in a dedicated legal billing tool post-migration.
Legal Case Tracker
Custom Field (Case-level)
Nutshell
Custom Field (Deal-level)
1:1Legal Case Tracker custom fields on cases — such as Jurisdiction__c, Court__c, Case_Type__c, or Judge__c — require corresponding Nutshell custom fields on the Deal object. We create each custom field in Nutshell with the appropriate type (text, pick-list, date, currency) before the migration run. Pick-list custom fields require value-by-value mapping if the source uses a controlled vocabulary.
Legal Case Tracker
Custom Field (Party-level)
Nutshell
Custom Field (Person-level)
1:1Party-level custom fields (e.g., Bar_Number__c for opposing counsel, Billing_Rate__c for contract attorneys) migrate as Nutshell custom fields on the Person object. We create these via the Nutshell API before the migration and map values directly from the source. Any restricted pick-list values require value-mapping review.
Legal Case Tracker
Reminder / Alert
Nutshell
Activity (Task)
1:1Automated reminders and deadline alerts in Legal Case Tracker have no direct equivalent in Nutshell. We preserve reminder text as Notes on the relevant Deal for manual rebuild. Nutshell's automation rules can replicate basic reminder logic (e.g., create a Task 3 days before a court date), but legal-specific SLA rules must be rebuilt in Nutshell's workflow engine post-migration.
Legal Case Tracker
Integration (Outlook / SharePoint)
Nutshell
Integration (Manual rebuild required)
1:1Legal Case Tracker's native Outlook and SharePoint integrations do not transfer. Email-to-case linking, calendar sync, and SharePoint document library references must be reconfigured in Nutshell's integration settings or via Zapier after migration. Nutshell supports Gmail, Google Calendar, Outlook via plugin, and Slack natively.
Legal Case Tracker
User / Assigned Attorney
Nutshell
Nutshell User
1:1Legal Case Tracker user accounts (attorneys, paralegals, admins) are matched to Nutshell users by email address. If a Legal Case Tracker user has no corresponding Nutshell account, their name is stored as a custom field (Original_Assigned_To__c) on the Deal and records are assigned to a designated fallback Nutshell user during migration.
Legal Case Tracker
Case Notes / History Log
Nutshell
Note on Deal
1:1Case notes and chronological history entries in Legal Case Tracker migrate as Nutshell Notes attached to the corresponding Deal. Timestamps and author attribution are preserved in the Note body. For high-volume history logs, we batch-convert entries into a single formatted Note to avoid creating hundreds of separate note records.
| Legal Case Tracker | Nutshell | Compatibility | |
|---|---|---|---|
| Case / Matter | Deal1:1 | Fully supported | |
| Party / Contact | Person1:1 | Fully supported | |
| Organization / Client Company | Company1:1 | Fully supported | |
| Document / File | Deal File Attachment1:1 | Fully supported | |
| Calendar / Court Date | Activity (Task / Event)1:1 | Fully supported | |
| Expense | Activity Note / Custom Field on Deal1:many | Fully supported | |
| Custom Field (Case-level) | Custom Field (Deal-level)1:1 | Fully supported | |
| Custom Field (Party-level) | Custom Field (Person-level)1:1 | Fully supported | |
| Reminder / Alert | Activity (Task)1:1 | Fully supported | |
| Integration (Outlook / SharePoint) | Integration (Manual rebuild required)1:1 | Fully supported | |
| User / Assigned Attorney | Nutshell User1:1 | Fully supported | |
| Case Notes / History Log | Note on Deal1: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 Case Tracker gotchas
Time entries may use non-standard duration formats
No native document export endpoint exists
Role-based access flags may disrupt user assignment after migration
Calendar events without a parent-case link import as orphaned records
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
Discover Legal Case Tracker data inventory and schema
We export a full data inventory from Legal Case Tracker — cases, parties, companies, documents, calendar entries, notes, and all custom fields — using the available API or structured CSV export. We document every custom field name, type, and pick-list value, and flag any fields that have no natural Nutshell equivalent. We also enumerate active automation rules and reminders so your team knows what must be rebuilt post-migration. The output is a Data Inventory Report used to build the field mapping plan.
Create Nutshell custom fields and configure Deal pipeline
Before data moves, we create all required Nutshell custom fields on the Deal and Person objects using the Nutshell API: Status__c (case status pick-list), Case_Type__c, Court__c, Jurisdiction__c, Judge__c, Filed_Date__c, Total_Expenses__c, Role__c on Person, Bar_Number__c, and any other custom fields identified in the discovery step. We also configure the Nutshell pipeline name and stage labels to align with your case type groupings. This step requires a Nutshell admin to provide API credentials with field creation rights.
Map parties to Nutshell People and Companies first
Nutshell requires Companies to exist before People can be linked (via company_id), and People to exist before Deals can reference them. We sequence the migration so Companies are created first, then People with party roles and custom Person fields, then Deals (cases) with all case-level custom fields and party associations. Owner assignment is resolved by email matching against Nutshell users; unmatched owners are flagged and assigned to a fallback user or left for manual reassignment. Documents are downloaded and staged for bulk re-upload after Deals are created.
Run sample migration with field-level diff
We migrate a representative sample — typically 50–100 cases across different case types and statuses — and generate a field-level diff report showing every mapped field, the source value, the destination value, and any transformation applied. You review the diff to verify that case status mapping, party role labels, court/judge fields, and document attachments are correct. Any mapping errors are corrected before the full run. This step also surfaces any Legal Case Tracker records with malformed data (e.g., special characters in party names, missing required Nutshell fields) that need pre-migration sanitization.
Execute full migration with delta-pickup window
The full migration ingests all remaining records — cases, parties, companies, activities, notes, and documents — into Nutshell. A delta-pickup window of 24–48 hours captures any new cases, party updates, or document additions made in Legal Case Tracker during the cutover period. All operations are logged in a migration audit file. After the delta window closes, we run a reconciliation check comparing record counts by entity type and flag any discrepancies. One-click rollback is available if the reconciliation fails and your team decides to revert before going live on Nutshell.
Post-migration validation and rebuild handoff
We deliver a Migration Summary Report with record counts, mapping logs, and any unmapped or partially migrated records requiring manual review. We provide an export of your Legal Case Tracker automation rules as a written reference document your legal operations team can use to rebuild reminders and deadline alerts in Nutshell's automation rules. We also provide a list of Nutshell custom fields created and their source counterparts so your admin can manage field settings going forward. Post-migration support is available for 5 business days for any data corrections.
Platform deep dives
Legal Case Tracker
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 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 Case Tracker and Nutshell.
Object compatibility
1 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 Case Tracker: Not publicly documented.
Data volume sensitivity
Legal Case Tracker 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 Case Tracker to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Legal Case Tracker 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 Case Tracker
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.