MyCase to Filevine or Litify, reconciled before anyone goes live.
MyCase is straightforward, which is why firms pick it and why they eventually outgrow it. When the practice needs structured phases, deadline chains and intake that scales, the move has to carry every case, document and invoice across without a gap. This is how we do it.
Watch
Case management transitions: the Micronetbd and YoCierge webinar
The Micronetbd and YoCierge webinar on case management transitions: what to move, what to clean up, what to leave.
1:01:30 on the Micronetbd channel
More videos on this pageWhat moves from MyCase, and how
Every item mapped to a real field on the new platform, or listed as dropped with a reason.
Cases
Every case with its history and custom fields, mapped to project types and phases.
Contacts
Clients, opposing parties, courts and providers, with roles, duplicates resolved.
Events and tasks
Calendar events, deadlines and tasks, still linked to the case.
Notes and messages
Notes, call logs and client portal messages in context.
Documents
Case documents moved with their folder structure intact.
Invoices and payments
Billing history and trust activity preserved for the audit trail.
Extract, map, load, prove
Nothing is frozen and nothing goes live on trust.
Extract and profile
We read the source, count everything and find what is dirty.
Map in writing
A field-by-field mapping your team approves before a single record moves.
Load to sandbox
You see your own data in the new system before production.
Cut over
Delta pass for anything new, reconciliation signed off, then go live.
What usually needs cleanup in a MyCase migration
Every MyCase database carries years of habits. These are the ones we plan for on day one, so they do not surface on go-live day.
- Custom fields used inconsistently between case types
- Contacts created twice through the client portal
- Documents uploaded without a case
- Closed cases that still need to be searchable
- Intake data living in a separate form tool
Filevine or Litify, with the folder tree intact
Micronetbd is a Filevine certified implementation partner and a Litify consultancy, so the destination is built by the same team that runs the move. Documents keep their folder tree, parties keep their roles, and the reconciliation report is signed off by your team before anyone goes live.
MyCase migration questions
Why do firms move off MyCase?
Usually growth: more matters, more staff, a need for structured phases, deadline chains, document automation and intake that scales. None of that is a criticism of MyCase; it is a sign the firm needs a different shape of platform.
How long does the migration take?
It depends on the size of the database, the document store and how much cleanup the profiling turns up. The written map comes first and the timeline goes in the fixed-scope quote with it, so you know both before anything moves.
Can the firm keep working during the move?
Yes. Nothing is frozen. We load the sandbox from a snapshot, your team tests on real records, and a delta pass at cutover brings across everything that changed in between.
What does the reconciliation report contain?
Source counts against destination counts, field by field and document by document, every exception listed with a reason, and spot checks against the source on real records. Your team signs it off before go-live and it is your audit trail afterwards.
Do client portal messages come across?
Yes, as notes on the case with dates and authors, so the history is readable on the new platform.
After the migration: somebody accountable for the new platform
A migration lands the data; the retainer keeps the platform working afterwards, with a named admin and a flat monthly fee: managed services, Filevine managed services, Litify managed services.
Watch: migrations, explained
The case management transitions webinar and George Ayub on why data fails.
More on the Micronetbd YouTube channel.
Send us a MyCase export
An export is enough to start. You get back a written map of what moves, what needs cleanup and what will not come across.