Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

Document Locator to Filevine migration

Document Locator is a server-based document management system, and Filevine is a cloud case management system. The move is matching each file in Document Locator to its case in Filevine.

FromDocument LocatorServer
  1. Documents: Carried across
  2. Emails: Carried across
  3. Tasks: Carried across
  4. Custom fields: Carried with mapping
  5. Notes: Confirmed in the analysis
  6. Templates: Confirmed in the analysis
ToFilevineCloud
  • 3 carried
  • 1 mapped
  • 2 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Document Locator to Filevine

Each row is a kind of record Document Locator holds, 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.

Records in Document Locator and their place in Filevine
RecordIn Document LocatorIn FilevineWhat is planned
DocumentsFiles stored in or linked from the systemHeldIn repository folders, with automatic versions, profiles and an audit log.Has a placeDocs section with folders. Templated project folders can be set per type.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails and attachments can be captured and managed with the documents.Has a placeHeld in the activity feed of the project.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeHeld as notes in the activity feed.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeld in partWorkflow and approval steps routed to people.Has a placeCarried across
Custom fieldsFields and record types the firm added itselfHeldMetadata is applied through profiles the administrator defines.Has a placeCustom sections and fields per project type.Carried with mapping
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partTemplates are rebuilt as Filevine document templates. They are not converted.Confirmed in the analysis

What the plans mean

Carried across
Filevine has a place for this kind of record. It is loaded there and checked against Document Locator.
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. Document Locator organises 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.

Document Locator runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Filevine is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.

Where the data is now

Because Document Locator presents itself as folders in Windows, people assume the documents can be dragged out like files on a drive. They are in a SQL Server repository. A copy made that way should not be expected to bring versions, profile values or permissions with it. A planned extraction reads the repository for those, and for check-out state as well.

  1. A repository, not a share

    The folder tree users see is drawn from a Microsoft SQL Server repository. On-premises, that database is on the firm’s server and can be backed up and read. In the hosted service it is on Azure and access is arranged with ColumbiaSoft. Which of the two applies shapes how the work begins.

  2. Folders stand in for matters

    There is no client or matter record, so firms build the equivalent with a folder convention, sometimes created automatically by a project-folder rule. The convention is read off the tree and tested: how many top-level folders match a client in the practice management system, and how many are something else.

  3. Version numbers and notes

    Every check-in adds a version with an incrementing number, users can add a version note, and prior versions can be promoted. For controlled documents such as policies and precedents, that history is the point of the system. The firm decides folder by folder whether history comes across or only the current version.

  4. Workflow and required reading

    Approvals in progress, review reminders and acknowledgements that staff have read a policy are records of process. A legal document system will usually have nowhere to put them. Reports are run from Document Locator before cutover and saved as documents, so the evidence is kept even though the workflow is not.

More about moving off Document Locator

Where it is going

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving into Filevine

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Filevine on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what Document Locator holds 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.

  2. 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.

  3. Trial load

    A trial is loaded into Filevine and checked against Document Locator: 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.

  4. Cutover

    There is no financial cutover on this route. After a short freeze on changes in Document Locator, a final pass over a weekend picks up what changed since the trial. Document Locator is 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 Document Locator 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

Step 1 of 5: Start with the route

Moving fromDocument Locator
Moving toFilevine

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what Document Locator 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.

  3. 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

Document Locator to Filevine: what firms ask

Can we simply copy the folders out through Windows?

It will produce files, and for a small set that may be all that is needed. It should not be relied on for a whole repository, because versions, profile metadata, permissions and audit history are in the database. The analysis establishes what the repository records about a document beyond the file itself.

How do documents get matched to matters when there is no matter record?

By the folder path or a profile field, whichever the firm used consistently. A matter list from the practice management system is matched against folder names, and the matches, near-matches and orphans are reported. Near-matches are confirmed by someone at the firm who knows the files.

Do documents from Document Locator 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 Document Locator have a place in Filevine?

Most of it does on paper. Notes and templates 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 Document Locator data is loaded into Filevine?

Custom fields are carried with mapping, so each mapping is agreed with you first. Notes and templates are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.

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.

How we do itDiscovery to rollout, step by step

Document Locator and Filevine are the names and marks of their owners, used here only to identify the two systems.

Moving from Document Locator 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.