Migrate your MyCase data
Practice management CRM for small and solo law firms with built-in client billing, texting, and document management—now under the AffiniPay umbrella alongside LawPay.
In its favor
Why people choose MyCase
The signal that keeps MyCase on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Lowest all-in-one price point among legal CRMs targeting small firms—many solo practitioners cite the $39/user/month starting tier as the validation point before committing to a bigger platform.
Built-in client portal, text messaging, and e-signature mean small firms avoid stacking three separate tools, which reviewers on G2 and Capterra repeatedly highlight as a primary draw.
Workflow automation with auto-calendaring of deadlines gives solo attorneys a structured case framework without manual setup on every new matter, per G2 reviews.
Affinity Pay acquisition in 2022 brought LawPay's payment infrastructure closer to the practice management layer, giving firms a tighter payments-to-matters financial loop.
10-day free trial with no credit card required lets firms migrate a handful of real matters before committing, which several Capterra reviewers mention as their evaluation method.
QuickBooks integration syncs one direction only—deleting a transaction in MyCase does not remove it in QuickBooks, and the sync can get stuck, forcing manual reconciliation that solo practitioners find disruptive.
Users report missing billing features that mid-size firms require: inability to bulk-update rates on past time entries, limited flat-fee case management, and manual invoice adjustments across multiple sections.
UI changes between releases (especially around notifications and client message navigation) create friction for staff trained on earlier layouts, per Capterra and G2 reviews.
Advanced features including the open API are gated behind the $109/user/month Advanced tier, so growing firms hit feature ceilings on lower plans and face a pricing cliff.
Firms outgrowing the platform report that Clio's integration marketplace and enterprise features better support scaling case volume, which drives switchers toward larger legal CRMs.
Reasons to switch
Why people leave MyCase
The recurring reasons buyers give for replacing MyCase. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where MyCase 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
MyCase pricing overview
MyCase uses a per-user, per-month subscription model across three named tiers. The entry Basic tier starts at $39/user/month, the Advanced tier is $109/user/month billed annually, and the Pro tier pricing is not publicly disclosed—firms must contact sales. All tiers include the client portal and basic integrations; the open API is locked behind Advanced.
Basic
Tier 1 of 3
$39/user/month
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on MyCase's schedule — see our quote-based pricing →
What gets migrated
MyCase object support
Object-by-object support for MyCase migrations. Per-pair details surface during scoping.
Cases
Fully supportedCases are the primary work unit in MyCase. Every case has a type, status, assigned attorney, client link, and a Time & Billing tab. We map case records 1:1 and preserve the case-to-contact role assignments during import.
Contacts
Fully supportedContacts are flat records with name, email, phone, address, and role assignment to cases. We import contacts from CSV or API and link them to their associated cases via role entries.
Companies
Fully supportedCompanies represent law firm clients as organisations and can have multiple Contacts linked to them. We map Company records and their associated Contact relationships in a single pass.
Time Entries
Mapping requiredTime entries carry billable hours tied to a case and an assigned rate. MyCase does not allow bulk rate updates on historical entries—each must be edited individually. We import all entries but flag any that reference rates which differ from destination billing templates.
Invoices
Mapping requiredInvoices are generated from a case's Time & Billing tab and support sections for Flat Fees, Time Entries, Expenses, and Adjustments. Invoice numbers and AR status are preserved; IOLTA trust-account associations require manual verification post-migration.
Documents
Mapping requiredMyCase Drive stores documents inside case folders. The platform supports drag-and-drop upload from local folders. We transfer documents by downloading from Drive via the API (Advanced tier) or via the Full Data Backup export, then re-uploading to the destination case folders, preserving folder structure.
Custom Fields
Mapping requiredCustom fields extend Case, Contact, and Company objects and are created by the firm. Their field types, options, and defaults vary. We read the custom field schema during discovery and map values to destination fields, flagging any that have no direct equivalent.
Tasks
Fully supportedTasks are attached to cases and can be grouped into Workflows. We map task records including due dates, assignees, and completion status. Workflow templates are not transferred—they are recreated at the destination.
Workflows
Mapping requiredWorkflows in MyCase are template sequences that auto-create tasks and calendar events when a new case opens. Workflow definitions are not exported via the standard export tools; we recommend rebuilding them at the destination using the firm's workflow documentation.
Calendar Events
Mapping requiredCalendar events (deadlines, hearings, appointments) are linked to cases. We import events as tasks or calendar entries depending on the destination system's object model, preserving date, time, and case association.
Client Portal Users
Mapping requiredThe client portal grants clients read and document-upload access to their linked cases. Portal user accounts and their case access lists are imported, though client-side login credentials cannot be transferred—clients receive fresh portal invitations at the destination.
Advanced Document Automation Templates
Not in this platformDocument automation templates are built inside the Microsoft Word add-in and stored per-user on the originating machine. There is no export pathway for ADA templates; firms must rebuild templates at the destination using their source documents and the destination system's template builder.
| Object | Support | Notes |
|---|---|---|
| Cases | Fully supported | Cases are the primary work unit in MyCase. Every case has a type, status, assigned attorney, client link, and a Time & Billing tab. We map case records 1:1 and preserve the case-to-contact role assignments during import. |
| Contacts | Fully supported | Contacts are flat records with name, email, phone, address, and role assignment to cases. We import contacts from CSV or API and link them to their associated cases via role entries. |
| Companies | Fully supported | Companies represent law firm clients as organisations and can have multiple Contacts linked to them. We map Company records and their associated Contact relationships in a single pass. |
| Time Entries | Mapping required | Time entries carry billable hours tied to a case and an assigned rate. MyCase does not allow bulk rate updates on historical entries—each must be edited individually. We import all entries but flag any that reference rates which differ from destination billing templates. |
| Invoices | Mapping required | Invoices are generated from a case's Time & Billing tab and support sections for Flat Fees, Time Entries, Expenses, and Adjustments. Invoice numbers and AR status are preserved; IOLTA trust-account associations require manual verification post-migration. |
| Documents | Mapping required | MyCase Drive stores documents inside case folders. The platform supports drag-and-drop upload from local folders. We transfer documents by downloading from Drive via the API (Advanced tier) or via the Full Data Backup export, then re-uploading to the destination case folders, preserving folder structure. |
| Custom Fields | Mapping required | Custom fields extend Case, Contact, and Company objects and are created by the firm. Their field types, options, and defaults vary. We read the custom field schema during discovery and map values to destination fields, flagging any that have no direct equivalent. |
| Tasks | Fully supported | Tasks are attached to cases and can be grouped into Workflows. We map task records including due dates, assignees, and completion status. Workflow templates are not transferred—they are recreated at the destination. |
| Workflows | Mapping required | Workflows in MyCase are template sequences that auto-create tasks and calendar events when a new case opens. Workflow definitions are not exported via the standard export tools; we recommend rebuilding them at the destination using the firm's workflow documentation. |
| Calendar Events | Mapping required | Calendar events (deadlines, hearings, appointments) are linked to cases. We import events as tasks or calendar entries depending on the destination system's object model, preserving date, time, and case association. |
| Client Portal Users | Mapping required | The client portal grants clients read and document-upload access to their linked cases. Portal user accounts and their case access lists are imported, though client-side login credentials cannot be transferred—clients receive fresh portal invitations at the destination. |
| Advanced Document Automation Templates | Not in this platform | Document automation templates are built inside the Microsoft Word add-in and stored per-user on the originating machine. There is no export pathway for ADA templates; firms must rebuild templates at the destination using their source documents and the destination system's template builder. |
Gotchas
What to watch for in MyCase migrations
Issues we've hit on past MyCase migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
QuickBooks sync is strictly one-directional
Advanced API access is tier-gated
Document migration requires offline file transfer
Bulk rate updates on historical time entries are not supported
| Severity | Issue |
|---|---|
| High | QuickBooks sync is strictly one-directional |
| High | Advanced API access is tier-gated |
| Medium | Document migration requires offline file transfer |
| Medium | Bulk rate updates on historical time entries are not supported |
Leaving MyCase?
Where MyCase customers move next
12 destinations MyCase can migrate to.
How a MyCase migration works
Four steps, MyCase-specific
Connect
OAuth 2.0 with refresh tokens into MyCase. Scopes limited to read-only on the data we move.
Map
We translate MyCase-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate MyCase quirks before production.
Migrate
Full migration with MyCase rate-limit handling. Rollback available throughout.
FAQ
MyCase migration FAQ
Answers to the questions buyers ask most during MyCase migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your MyCase migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate MyCase.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your MyCase setup and destination — written quote back within a business day.