Docketwise to Filevine, with every form answer landing in a field.
Docketwise is built around immigration forms, and that is where the value in its database sits: the answers your team has collected for every applicant and beneficiary. A migration that drops those to a PDF pile loses years of work. We map them to fields on the destination so the next form is prefilled the same way.
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 Docketwise, 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 by visa or petition type, with its status and history, mapped to project types on the new platform.
Clients, beneficiaries and petitioners
People and companies with their roles on each case, family relationships preserved, duplicates resolved.
Form data
The questionnaire and form answers behind each case become fields on the destination, so prefill keeps working.
Deadlines and reminders
Priority dates, RFE deadlines, expirations and reminders still linked to the case.
Documents
Uploaded evidence, generated forms and correspondence moved with the folder tree intact.
Billing and payment plans
Invoices, payments and installment plans 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 Docketwise migration
Every Docketwise database carries years of habits. These are the ones we plan for on day one, so they do not surface on go-live day.
- Cases opened per family member rather than per petition, or the reverse
- Form answers updated on the PDF but not in the questionnaire
- Contacts duplicated between the client portal and the staff record
- Documents in the portal that were never attached to a case
- Closed cases that must stay searchable for renewals and follow-on petitions
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.
Docketwise migration questions
Why Filevine for an immigration firm?
Micronetbd runs an immigration template for Filevine that carries the case types, intake questionnaires, deadline logic and document sets an immigration practice needs, so the destination is configured for the work before the data lands, not after.
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.
What happens to the client portal?
Client-facing intake continues on the destination's portal or on the firm's website through Workup Agent. Portal accounts themselves are not migrated; the people and their cases are, and clients are invited fresh.
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 Docketwise 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.