MerusCase to Filevine or Litify, with the workers comp history intact.
MerusCase runs a lot of California practices, workers compensation above all, and its database carries the EAMS filing history, the lien records and the body-part and injury detail those firms live on. We read all of it, map it in writing and prove the counts on the other side.
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 MerusCase, and how
Every item mapped to a real field on the new platform, or listed as dropped with a reason.
Cases and case types
Every case with its history, workers comp, personal injury and general matters mapped to project types on the new platform.
Contacts and roles
Applicants, employers, carriers, adjusters, physicians and attorneys with their roles on each case, duplicates resolved.
Injury and claim detail
Dates of injury, body parts, claim numbers, ADJ numbers and disability ratings become real fields, not a pasted summary.
Calendar, tasks and deadlines
Hearings, depositions, QME appointments and statutory deadlines still linked to the case.
Documents and filings
The document store moved with the folder tree intact, EAMS filing confirmations and served documents included.
Billing, liens and settlements
Time, costs, lien records and settlement or award records line by line, tied to the case.
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 MerusCase migration
Every MerusCase database carries years of habits. These are the ones we plan for on day one, so they do not surface on go-live day.
- Case types that grew apart between offices and need one set of fields
- Contacts entered once per case rather than once per person
- Body-part and injury detail typed into notes instead of fields
- Documents attached to emails but never filed to the case
- Closed cases the firm must keep searchable for lien and audit reasons
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.
MerusCase migration questions
Does the EAMS filing history come across?
Yes. Filing confirmations, served documents and the case numbers they reference are mapped to the case on the new platform so the record is complete. Filing itself continues through whichever EAMS path the destination supports; we say on the first call how that works for the platform you choose.
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.
Which destination fits a MerusCase firm?
Workers compensation and personal injury firms usually land on Filevine or Litify. We implement both and will say on the first call which one fits the way your firm runs a case, including how California workers comp practice is configured on each.
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 MerusCase export
An export is enough to start. You get back a written field-by-field map of what moves, what needs cleanup and what will not come across, before anything is quoted.