CRM migration

Migrate from Legal Case Tracker to Nutshell

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 logo

Legal Case Tracker

Source

Nutshell

Destination

Nutshell logo

Compatibility

92%

11 of 12

objects map 1:1 between Legal Case Tracker and Nutshell.

Complexity

BStandard

Timeline

24–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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 Case Tracker logo

Legal Case Tracker

What's pushing teams away

  • Limited advanced features as firms scale — analytics, AI automation, and workflow customisation are minimal compared to mid-market alternatives, prompting migration when firms grow beyond basic case tracking.
  • Reporting and customisation gaps frustrate users who need firm-wide dashboards, custom fields, or deeper customisation; some resort to third-party tools that the platform does not integrate with cleanly.
  • Customer support responsiveness is inconsistent according to user reports, with some issues requiring extended ticket queues rather than direct resolution.
  • Document export and API access are restricted on lower tiers, limiting data portability and making migrations harder when firms decide to switch platforms.

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 Case Tracker objects map to Nutshell

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

maps to

Nutshell

Deal

1:1
Fully supported

Cases 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

maps to

Nutshell

Person

1:1
Fully supported

Parties 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

maps to

Nutshell

Company

1:1
Fully supported

Client 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

maps to

Nutshell

Deal File Attachment

1:1
Fully supported

Documents 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

maps to

Nutshell

Activity (Task / Event)

1:1
Fully supported

Court 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

maps to

Nutshell

Activity Note / Custom Field on Deal

1:many
Fully supported

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

maps to

Nutshell

Custom Field (Deal-level)

1:1
Fully supported

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

maps to

Nutshell

Custom Field (Person-level)

1:1
Fully supported

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

maps to

Nutshell

Activity (Task)

1:1
Fully supported

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

maps to

Nutshell

Integration (Manual rebuild required)

1:1
Fully supported

Legal 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

maps to

Nutshell

Nutshell User

1:1
Fully supported

Legal 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

maps to

Nutshell

Note on Deal

1:1
Fully supported

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

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 Case Tracker logo

Legal Case Tracker gotchas

High

Time entries may use non-standard duration formats

High

No native document export endpoint exists

Medium

Role-based access flags may disrupt user assignment after migration

Medium

Calendar events without a parent-case link import as orphaned records

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

  • No native case object means case status requires a custom field with value-by-value mapping

    Nutshell has no equivalent of a legal case or matter object — cases must become Deals. Legal Case Tracker's case status pick-list values (e.g., Filed, Discovery, Motion Pending, Trial, Closed) have no direct Nutshell Deal Stage equivalents because Nutshell stages are tied to a sales pipeline model. We create a custom pick-list field (Status__c) on the Deal and map each source status value individually. If Legal Case Tracker uses custom status values that your team created, those must be enumerated during discovery and explicitly mapped — unmapped values default to the Nutshell stage field or are stored as text, which limits filtering in Nutshell's pipeline view.

  • Document re-attachment is not a direct file migration — it requires download and re-upload

    Legal Case Tracker stores documents inside the case record, often with version control and role-based access rules. Nutshell attaches files directly to a Deal or Person record with a 25MB per-file limit and no native version history. We download all documents from Legal Case Tracker, map them to the corresponding Nutshell Deal, and re-upload them via Nutshell's file attachment API. Documents exceeding 25MB are flagged for manual handling — typically linked via an external URL reference in a Note. Nutshell's sharing model applies to the entire Deal, not per-document — any document-level role restrictions from Legal Case Tracker are lost unless recreated manually per Nutshell's access controls.

  • Automated reminders and deadline alerts have no Nutshell equivalent and must be rebuilt

    Legal Case Tracker's automated reminders (e.g., 'notify paralegal 5 days before hearing date', 'send client update 30 days after filing') are built on Legal Case Tracker's workflow engine and do not export as data. Nutshell's automation rules can trigger Tasks based on Deal stage changes or date fields, but they cannot replicate the granular legal deadline logic (e.g., court-specific response windows, statutory filing deadlines). We preserve reminder text as Notes on the relevant Deal so your team can manually create Nutshell automation rules post-migration. The legal operations team should audit all active reminders before migration and plan a rebuild session in Nutshell's automation UI.

  • Party-to-organization linking may collapse in Nutshell's 1:N model

    Legal Case Tracker allows multiple organizations per party (e.g., an attorney who works at two firms simultaneously). Nutshell's Person record links to a single primary Company via the company_id field. If a party in Legal Case Tracker has more than one associated organization, we link to the primary company and store secondary organizations as a comma-separated list in a custom field (Other_Organizations__c) on the Person record. This is a data loss point that should be reviewed during the sample migration — your team may decide to create separate Person records per organization to preserve full context.

  • API token scope and impersonation settings affect migration access

    Nutshell's API uses Basic authentication with a domain/username and API token. API keys can be configured with impersonation enabled, which allows actions to be logged under a specific user's name, or disabled, which logs all API actions under the key owner. If impersonation is not enabled, migration operations are attributed to the API key owner rather than the original Legal Case Tracker user who created the record. We recommend enabling impersonation on the migration API key before the migration run so that audit trails in Nutshell reflect the original case owner, not the service account.

Migration approach

Six steps for a successful Legal Case Tracker to Nutshell data migration

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

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

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

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

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

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

Context on both ends of the pair

Legal Case Tracker logo

Legal Case Tracker

Source

Strengths

  • Dynamic dashboard provides at-a-glance view of active cases, pending tasks, and upcoming hearings for daily practice management.
  • Time tracking and expense logging are natively integrated, keeping billable hours and cost records attached to the relevant matter.
  • Role-based access control enables basic confidentiality by restricting sensitive case information to authorised users.
  • Document hub centralises case-related files with contacts and calendar integration to Outlook for email attachment linking.
  • Low-friction onboarding for small teams with straightforward interface and no enterprise configuration overhead.

Weaknesses

  • Minimal analytics and reporting beyond standard dashboards limits data-driven insights for firm growth and performance review.
  • API documentation is not publicly available, restricting programmatic access and custom integrations.
  • Advanced AI automation and workflow features are absent or limited compared to mid-market legal CRM alternatives.
  • Document export capabilities are restricted, making bulk data portability difficult when migrating off the platform.
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. 1 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 Case Tracker and Nutshell.

  • Object compatibility

    B

    1 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 Case Tracker: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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 consultation

Most Legal Case Tracker to Nutshell migrations complete in 24–72 hours of clock time for under 10,000 records (cases, parties, companies, and associated documents). Larger setups with 10,000+ records or high document volume extend to 5–10 business days. The longest single step is usually creating Nutshell custom fields and validating the case-status value mapping before the full run — plan 2–3 days for that review if you have more than 10 custom fields on the case object.

Adjacent paths

Related migrations to explore

Ready when you are

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