ProLaw to Filevine or Litify, read straight from the database.
ProLaw firms tend to have long histories, a deep docket and a ledger that has to reconcile to the penny. We read the SQL Server database directly, map every table in writing and prove the counts before your team signs off.
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 ProLaw, and how
Every item mapped to a real field on the new platform, or listed as dropped with a reason.
Matters
Every matter with its history, area of law and custom fields, mapped to project types.
Contacts and parties
Clients, related parties and their roles on each matter, duplicates resolved.
Docket and calendar
Docket entries, deadlines and events, still linked to the matter.
Notes and documents
Notes in context, and documents moved with the folder tree intact.
Ledger and trust
Time, costs, billing and trust records line by line, for the audit trail.
Users and security
Roles, groups and access rebuilt on the new platform.
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 ProLaw migration
Every ProLaw 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 tables and fields added by an integrator years ago, with no documentation
- Document links that point to paths that have since moved
- Matters with several areas of law that map to more than one project type
- Contacts stored as free text on the matter
- Ledger entries that never balanced in the source and must be flagged, not fixed silently
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.
ProLaw migration questions
Do you need database access to migrate from ProLaw?
A SQL Server backup or read access is the cleanest path, and it is how we get everything rather than what the reports expose. If the firm can only provide exports, we work from those and say what that leaves out.
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.
How do you handle the ledger?
Time, costs, billing and trust are moved line by line and reconciled to totals. Anything that does not balance in the source is listed as an exception with a reason, never adjusted quietly.
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 ProLaw backup
A database backup or a schema is enough. You get back a written map of what moves, what needs cleanup and what will not come across.