Migrate your The Case File data
Cloud-based legal practice management software for small and mid-size firms. Handles cases, contacts, billing, and documents with an emphasis on ease of use and client intake workflows.
In its favor
Why people choose The Case File
The signal that keeps The Case File on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Small-firm friendly pricing and straightforward case management without the complexity of enterprise legal platforms.
Good client intake and lead tracking built into the same platform as active case management.
Native Full Data Backup and export spreadsheets make raw data extraction possible without a formal API.
Strong reputation for intuitive UI that attorneys and paralegals can adopt without formal training.
Integrated time tracking and billing directly linked to open cases simplifies law firm accounting.
Document management limitations make handling extremely large or complex litigation document sets difficult.
The platform lacks depth for multi-party or high-volume matters that require advanced workflow automation.
Reporting and analytics are basic compared to purpose-built litigation analytics platforms.
Limited API documentation and third-party integration ecosystem makes automation difficult.
Some firms outgrow the platform as they scale and need more robust matter-level permissions controls.
Reasons to switch
Why people leave The Case File
The recurring reasons buyers give for replacing The Case File. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where The Case File fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
The Case File pricing overview
MyCase pricing is not publicly disclosed on their website. Prospective customers must contact sales for a quote. Plans appear to scale by user count and feature tier, with add-ons available for document e-signature and payment processing.
Starter
Tier 1 of 3
Not publicly listed
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on The Case File's schedule — see our quote-based pricing →
What gets migrated
The Case File object support
Object-by-object support for The Case File migrations. Per-pair details surface during scoping.
Cases
Fully supportedCases is the central object in MyCase. Each case carries status, assigned attorney, client contact, opposing parties, and case number. We preserve the full case record including dates, staff assignments, and related contacts during migration.
Contacts
Fully supportedMyCase stores contacts with name, email, phone, address, and firm association. We export via the contact spreadsheet and land records 1:1 into the destination CRM Contacts or equivalent objects.
Companies
Fully supportedCompanies represent opposing counsel, insurance carriers, and other organizational entities. We map Company records to the destination's Account or Organization object, preserving relationships to linked Contacts.
Documents
Mapping requiredMyCase attaches documents to cases. We export file metadata and binary blobs together and reconstruct the folder structure in the destination, though original naming conventions may vary depending on export format.
Time Entries
Mapping requiredBillable time entries are linked to Cases and Contacts. We preserve the hours, date, description, and billing rate. Where the destination uses a different time-tracking schema, we map entries to the nearest equivalent structure.
Billing Records
Mapping requiredInvoices and payments are generated from time entries and expense records. We export invoice headers, line items, and payment status. Recurring billing configurations may not transfer automatically.
Calendar Events
Mapping requiredMyCase calendars include court dates, deadlines, and appointments linked to Cases or Contacts. We map events with title, start/end times, and case associations, though attendee-level detail may require manual reconciliation.
Trust Accounts
Mapping requiredTrust account balances and transaction history are stored against Cases or Contacts. We export ledger entries and current balances; however, regulatory compliance requirements mean trust records often require manual verification at the destination.
Custom Fields
Mapping requiredMyCase allows custom fields on Cases and Contacts. We identify all custom field definitions during scoping, map values by type (text, date, dropdown), and flag any that lack a clear destination equivalent.
Tasks
Mapping requiredTasks are associated with Cases and carry assignee, due date, and completion status. We export tasks and map them to the destination task management system, though checklist hierarchy may flatten during transfer.
Communications
Mapping requiredEmails and notes logged against Cases or Contacts are exported as text records with timestamps. Thread associations may not transfer if the destination lacks a linked communication model.
| Object | Support | Notes |
|---|---|---|
| Cases | Fully supported | Cases is the central object in MyCase. Each case carries status, assigned attorney, client contact, opposing parties, and case number. We preserve the full case record including dates, staff assignments, and related contacts during migration. |
| Contacts | Fully supported | MyCase stores contacts with name, email, phone, address, and firm association. We export via the contact spreadsheet and land records 1:1 into the destination CRM Contacts or equivalent objects. |
| Companies | Fully supported | Companies represent opposing counsel, insurance carriers, and other organizational entities. We map Company records to the destination's Account or Organization object, preserving relationships to linked Contacts. |
| Documents | Mapping required | MyCase attaches documents to cases. We export file metadata and binary blobs together and reconstruct the folder structure in the destination, though original naming conventions may vary depending on export format. |
| Time Entries | Mapping required | Billable time entries are linked to Cases and Contacts. We preserve the hours, date, description, and billing rate. Where the destination uses a different time-tracking schema, we map entries to the nearest equivalent structure. |
| Billing Records | Mapping required | Invoices and payments are generated from time entries and expense records. We export invoice headers, line items, and payment status. Recurring billing configurations may not transfer automatically. |
| Calendar Events | Mapping required | MyCase calendars include court dates, deadlines, and appointments linked to Cases or Contacts. We map events with title, start/end times, and case associations, though attendee-level detail may require manual reconciliation. |
| Trust Accounts | Mapping required | Trust account balances and transaction history are stored against Cases or Contacts. We export ledger entries and current balances; however, regulatory compliance requirements mean trust records often require manual verification at the destination. |
| Custom Fields | Mapping required | MyCase allows custom fields on Cases and Contacts. We identify all custom field definitions during scoping, map values by type (text, date, dropdown), and flag any that lack a clear destination equivalent. |
| Tasks | Mapping required | Tasks are associated with Cases and carry assignee, due date, and completion status. We export tasks and map them to the destination task management system, though checklist hierarchy may flatten during transfer. |
| Communications | Mapping required | Emails and notes logged against Cases or Contacts are exported as text records with timestamps. Thread associations may not transfer if the destination lacks a linked communication model. |
Gotchas
What to watch for in The Case File migrations
Issues we've hit on past The Case File migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
No publicly documented API for programmatic data extraction
Trust account ledger balances require manual verification
Custom fields lack a documented export schema
Document folder structure does not export flatly
| Severity | Issue |
|---|---|
| High | No publicly documented API for programmatic data extraction |
| High | Trust account ledger balances require manual verification |
| Medium | Custom fields lack a documented export schema |
| Medium | Document folder structure does not export flatly |
Leaving The Case File?
Where The Case File customers move next
12 destinations The Case File can migrate to.
How a The Case File migration works
Four steps, The Case File-specific
Connect
Not publicly documented into The Case File. Scopes limited to read-only on the data we move.
Map
We translate The Case File-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate The Case File quirks before production.
Migrate
Full migration with The Case File rate-limit handling. Rollback available throughout.
FAQ
The Case File migration FAQ
Answers to the questions buyers ask most during The Case File migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your The Case File migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate The Case File.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your The Case File setup and destination — written quote back within a business day.