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

Data migration route

Legal Files to Filevine migration

Legal Files are a server-based case management system, and Filevine is a cloud one. The records line up case for case, and the detail is in the fields and stages.

FromLegal FilesServer
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Emails: Carried across
  5. Notes: Carried across
  6. Calendar: Carried across
  7. Tasks: Carried across
  8. Billing: Carried with mapping
  9. Custom fields: Carried with mapping
  10. Templates: Carried with mapping
  11. Intake: Carried with mapping
  12. Time and expenses: Confirmed in the analysis
  13. Trust money: Confirmed in the analysis
  14. Firm accounts: Confirmed in the analysis
ToFilevineCloud
  • 7 carried
  • 4 mapped
  • 3 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Legal Files to Filevine

Each row is a kind of record Legal Files hold, whether Filevine has a place for it, and what is planned. On this route seven kinds of record carry across, four kinds need mapping and three kinds are confirmed in the analysis.

Records in Legal Files and their place in Filevine
RecordIn Legal FilesIn FilevineWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldAny type of case or matter, as configured by the organisation.Has a placeLoaded as projects of a defined project type.Carried across
ContactsClients, other parties and referrersHeldContact management with checks for duplicate entries.Has a placeContact cards, linked to projects.Carried across
DocumentsFiles stored in or linked from the systemHeldDocument management with text searching.Has a placeDocs section with folders. Templated project folders can be set per type.Carried across
EmailsEmails saved to matters or to the storeHeldTwo-way integration with Outlook and Gmail saves emails and attachments.Has a placeHeld in the activity feed of the project.Carried across
NotesFile notes, matter notes and contact notesHeldNotes, mail logs and phone logs.Has a placeHeld as notes in the activity feed.Carried across
CalendarAppointments, court dates and deadlinesHeldCalendaring with deadline tracking.Has a placeDeadlines and calendar events.Carried across
TasksTo-dos and workflow steps assigned to peopleHeld in partWorkflows, alerts and follow-ups.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledTo be confirmedHas a place in partNeeds the Billing product enabled.Confirmed in the analysis
BillingInvoices, payments and debtor balancesHeld in partThe vendor lists eBilling among its functions.Has a place in partNeeds the Billing product enabled.Carried with mapping
Trust moneyTrust or client account ledgers and balancesTo be confirmedHas a place in partTrust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis.Confirmed in the analysis
Firm accountsGeneral ledger, office account and payablesTo be confirmedTo be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustomers add and change fields and screens without programming.Has a placeCustom sections and fields per project type.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument assembly.Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partLegal aid intake is among the uses the vendor describes.Has a place in partLeads belong in Lead Docket, which passes signed clients to Filevine.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 Legal Files.
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

Case to case, field by field.

Two case management systems look alike from a distance and differ in almost every detail. Each has its own idea of a case type, a stage, a party role and a deadline. Legal Files and Filevine may both hold a limitation date, yet one calculates it and the other stores what was typed. The mapping goes field by field and status by status, and the trial load is checked by opening real cases in both systems side by side.

Custom fields hold most of what the firm has built up. Years of intake answers, injury details or visa histories sit in fields the firm added itself. Each is matched to a field in Filevine, and anything unmatched is kept as a note on the case so that it can still be searched. Workflows and document templates are rebuilt in the new system’s own tools. Open tasks come across with their owners and due dates.

Legal Files run 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

Each office configured its own file types, fields and workflows, so one Legal Files system does not look like the next. The move starts with an inventory of that configuration. Then come the files, the people on them, documents and saved emails. Where the office is part of a government body or a company, retention rules and access restrictions on certain files have to survive the move as well.

  1. Configuration is the data model

    File types, screens and fields were set up by the office’s own administrator, often over many years. The field list has to be taken from that system, not assumed. Every custom field is reported with how many files use it, and the office picks the ones that deserve a place in the new system.

  2. Not built around billing

    Many of its users are in-house and government teams, which do not bill clients or hold trust money. If the destination is a law firm practice system, billing fields will be empty on every migrated matter. Where the office does record time or outside counsel spend, that is found in the analysis and mapped separately.

  3. Mail and phone logs

    Besides documents and emails, a file keeps logs of mail and of phone calls. Offices that answer to the public rely on these as the record of who was told what. They come across as dated notes on the matter with the log type kept, so they can still be filtered.

  4. Restricted files

    Investigations and other sensitive files are kept under controlled access. Those restrictions are extracted as a list of files and the users allowed to see them. The destination’s permissions are set from that list before the trial load is opened to staff, so restricted files are locked down before anyone else looks.

  5. On your servers or hosted

    The route to a copy of the data depends on where Legal Files runs. An on-premises site works through its own IT team. A hosted site works through the vendor. Government sites often need a security review before data leaves the building, and that review goes in the timetable.

More about moving off Legal Files

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.

Financial records move on this route, so the balances are rehearsed before the real cutover.

  1. Analysis

    We read what Legal Files hold and how its records link, then agree with you, field by field, where each piece will sit in Filevine. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  2. Clean-up

    Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Legal Files, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into Filevine as a trial and checked against Legal Files: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Legal Files are frozen for an agreed window, the data is collected a final time and Filevine goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in Legal Files as at the cutover date. Legal Files 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 Legal Files 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 fromLegal Files
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 Legal Files 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

Legal Files to Filevine: what firms ask

Our system has been heavily customised. Does everything have to be rebuilt?

No. Custom fields that are still filled in are recreated. Ones that were abandoned years ago are reported and usually left behind. Workflows and document templates do not transfer between products, so the ones in regular use are rebuilt in the new system and the rest are retired.

Can saved emails stay attached to the right file?

Emails saved into Legal Files through its Outlook or Gmail integration are stored against the file, with attachments. They are loaded to the same matter in the destination with their sent date and sender kept. Counts are run per file, because saved emails are easy to lose in a move without anyone noticing.

What about records we are required to retain?

Retention obligations travel with the records, not the software. Files due to be kept are either loaded as closed matters or held in a read-only copy of Legal Files for the retention period. The choice is written down with the office’s records officer, along with who can reach the copy.

Do trust balances in Legal Files have a place in Filevine?

That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in Legal Files before the plan is fixed. If Filevine turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

Does everything in Legal Files have a place in Filevine?

Most of it does on paper. Time entries, trust ledgers and the firm’s accounts 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 Legal Files data is loaded into Filevine?

Billing records, custom fields, templates and intake records are carried with mapping, so each mapping is agreed with you first. Time entries, trust ledgers and the firm’s accounts are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.

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

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

Moving from Legal Files 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.