Data migration route
Local folders to Filevine migration
Local folders are plain files on equipment the firm controls, and Filevine is a cloud case management system. The move is matching each file in Local folders to its case in Filevine.
Local foldersFiles- Documents: Carried across
- Emails: Carried across
- Notes: Carried across
- Templates: Carried with mapping
- Time and expenses: Confirmed in the analysis
- Billing: Confirmed in the analysis
FilevineCloud- 3 carried
- 1 mapped
- 2 to confirm
What moves
What moves from Local folders to Filevine
Each row is a kind of record Local folders hold, whether Filevine has a place for it, and what is planned. On this route three kinds of record carry across, one kind needs mapping and two kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldFiles in one user’s folders, with no sharing or versions. | Has a placeDocs section with folders. Templated project folders can be set per type. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partSaved .msg files, and Outlook data files stored under Documents. | Has a placeHeld in the activity feed of the project. | Carried across |
| NotesFile notes, matter notes and contact notes | Held in partFile notes kept as Word documents or text files. | Has a placeHeld as notes in the activity feed. | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | Held in partTimesheets kept as spreadsheets, where a practitioner works that way. | Has a place in partNeeds the Billing product enabled. | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | Held in partInvoices as Word or PDF files; no ledger. | Has a place in partNeeds the Billing product enabled. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | Held in partPersonal precedents and Word templates saved by the user. | Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted. | Carried with mapping |
What the plans mean
- Carried across
- Filevine has a place for this kind of record. It is loaded there and checked against Local folders.
- Carried with mapping
- Filevine holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
- Confirmed in the analysis
- We could not confirm this from the two products’ own material, so it is checked against your data before the plan is fixed.
The table states what the two products hold and what NewLaw plans for. It is not a promise that every record moves: that is settled against your own data in the analysis.
This kind of move
Every document goes to the case it belongs to.
A case management system expects each document to sit on a case, usually in a category such as correspondence, medical records or court documents. Local folders organise files its own way, by profile or by folder. So the move needs two rules: which case a file belongs to, and which category it goes in. The first comes from client and matter references or folder names. The second comes from a document type or a subfolder, and where neither exists the files arrive uncategorised and are marked as such.
Cases must exist in Filevine before documents can be attached to them. If the system is already live, files are matched to its case list and the unmatched ones are reported. If it is new, the case list is created first. Dates, authors and file names are kept. Email comes across as message files. Where several versions of a document exist, the firm chooses between loading the latest and loading them all.
With Local folders the files are already on equipment the firm controls, so there is no export step: they are read where they are. Upload speed sets the pace for a large store. The originals stay in place, unchanged, until the firm has checked the copy in Filevine.
Where the data is now
Leaving Local folders
Collecting from local folders means going machine by machine, and person by person, because nobody else knows what is there. Volumes are small next to a server drive. The value can be high: the only signed copy of a deed, a partner’s twenty years of precedents, the working files of every matter a sole practitioner has open.
An inventory per computer
Every PC, Mac and laptop in scope is scanned for documents outside the system folders, including machines kept at home and the one in the storeroom nobody has started in a year. Each user profile on a shared computer is scanned separately. The result is a list by machine that the firm signs off.
Local drafts against the shared copy
Where the firm also has a server or cloud drive, a local file is often a later draft of something filed there, or an older one. Files are compared by content. Identical copies are dropped, and the differing ones are shown side by side with their dates so the lawyer can say which is current.
Folders that only look local
A OneDrive, Dropbox or Google Drive folder appears in Explorer like any other, but its contents belong to the cloud account and may not be on the disk in full. Those are collected from the service. Scanning them as local folders double counts files and can copy empty placeholders.
Mail archives under Documents
Outlook’s default location for data files is an Outlook Files folder inside Documents. A scan for documents will find them, sometimes many gigabytes each. They are set aside and handled as mail, matched to matters by folder and correspondent, not loaded as single enormous files.
One person’s own system
A lawyer’s local folders follow a private logic: by year, by court, by the other side’s surname. The owner spends half an hour explaining it, and the mapping to matters is written from that conversation. Where the owner has left the firm, folders are matched on client names and dates alone.
Where it is going
Arriving in Filevine
Loading a firm into Filevine depends on the project types being built first. Until the sections and fields exist there is nowhere for the data to go, so configuration and migration are planned together. The old system’s parties, insurers, providers and key dates are mapped to sections, and its notes and emails are loaded into each project’s activity feed.
Project types before data
Each area of practice needs a project type with its sections, fields and phases defined in the Customs Editor. Changes made there apply to every project of that type. The types are drafted from the old system’s data, tested with a few real cases, and only then is the bulk load run.
One contact card per person
Contacts are held as contact cards. A doctor or adjuster who appears on many projects is best loaded as one card, not one for each project. Duplicates in the old system are merged before loading where they can be identified. Loading them as they are produces several cards for the same person, and staff then pick the wrong one when adding a party.
Lists become collection items
Anything the old system held as a list against a matter, such as providers, liens, insurance policies or expenses, is loaded as items in a collection section. Each column needs a matching field. Totals per project are compared with the old system afterwards, since those figures feed the settlement and disbursal sheets.
History goes into the feed
File notes, emails and completed tasks from the old system are loaded into the activity feed with their original dates and authors. Authors must exist as users or be recorded in the text. The feed is long on an old case, so staff are shown how to filter it before go-live.
Billing is a separate switch
The Billing section only appears once Billing is enabled for the firm. Time entries, invoices and trust balances from the old system need that in place before they can be loaded. A firm that leaves it off can still record case costs in a collection section built for the purpose.
How NewLaw runs it
Four steps, in this order.
No financial cutover is planned on this route, so a load can be run again until it is right. If the analysis finds financial records with a place in Filevine, they get a rehearsed cutover of their own.
Analysis
We read what Local folders hold and how it is organised, then agree with you where each kind of record will sit in Filevine. Anything with no place there stays behind or is archived, and you see which before the move.
Clean-up
Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.
Trial load
A trial is loaded into Filevine and checked against Local folders: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.
Cutover
After a short freeze on changes in Local folders, a final pass over a weekend picks up what changed since the trial. If the analysis found financial records to move, their cutover is rehearsed on a full trial load first. Local folders are kept read only as the fall-back record.
Fixed price, agreed after the analysis. How NewLaw moves legal data
Start
Start this migration
Tell us what is in Local folders and roughly how much of it. The first step is the analysis, and the price is fixed once it is done.
Step 1 of 5
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what Local folders holds
What is in it, how its records link, and where each piece would sit in Filevine. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- A fixed price in writing
Set after the analysis, so it reflects what is in your data. You have it before any work starts.
Beyond the data
Setting up Filevine
Loaded data is not yet a working system. This is what NewLaw sets up in Filevine, beyond the migration, so that people can work in it from the first day.
Filevine arrives as a platform to be configured, and most of the implementation is design. Someone has to decide what a project looks like for each kind of work the firm does, what moves it from one phase to the next, and who can see what. Those decisions are made with the people who run the files, then built and tested.
Set-up decisions in Filevine
- Design project types, sections and fields for each practice area
- Define phases and the tasks each phase should trigger
- Build document templates that fill from project fields
- Set teams, permissions and protected sections for restricted matters
- Decide whether Billing and Payments are switched on
- Connect Lead Docket so signed leads become projects
Questions
Local folders to Filevine: what firms ask
I am a sole practitioner and everything is on my laptop. Where do we start?
With a full copy of the laptop’s user folders taken to a second disk, before anything else. Then a list of your open matters, even handwritten. Folders are matched to that list, the rest is treated as closed files, and you check a sample in the new system before the laptop copy is retired.
Do you need to take our computers away?
No. It is the files that are needed, not the machines. Whether they are collected at each desk or remotely with the firm’s IT provider, and at what hours, is agreed in the analysis. A laptop needs to be switched on, signed in and on the office network or a reliable connection for as long as its copy takes.
What about personal files mixed in with work?
They stay where they are. Each person is shown the list of top-level folders found on their machine and marks the ones that are private. Those paths are excluded before any file is copied. Installed programs and system files are left out in any case.
Do documents from Local folders keep their folders and dates in Filevine?
Filevine stores documents. Docs section with folders. Templated project folders can be set per type. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.
Does everything in Local folders have a place in Filevine?
Most of it does on paper. Time entries and billing records could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in Filevine is kept as a readable archive, and you see which before the move.
What has to be decided before Local folders data is loaded into Filevine?
Templates are carried with mapping, so each mapping is agreed with you first. Time entries and billing records are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from Local folders and into Filevine
Where to start
Before and after the move.
Choosing the system comes before a migration. Setting it up and putting AI to work come after.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
Local folders and Filevine are the names and marks of their owners, used here only to identify the two systems.
Moving from Local folders to Filevine?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.