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

Data migration route

Filevine to SharePoint migration

Filevine is a cloud case management system, and SharePoint is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.

FromFilevineCloud
  1. Documents: Carried across
  2. Matters: Carried with mapping
  3. Contacts: Carried with mapping
  4. Emails: Carried with mapping
  5. Notes: Carried with mapping
  6. Calendar: Carried with mapping
  7. Tasks: Carried with mapping
  8. Custom fields: Carried with mapping
  9. Templates: Carried with mapping
  10. Firm accounts: Confirmed in the analysis
ToSharePointCloud
  1. Time and expenses: Kept as a readable archive
  2. Billing: Kept as a readable archive
  3. Trust money: Kept as a readable archive
  4. Intake: Kept as a readable archive
Readable archiveNo place in SharePoint
  • 1 carried
  • 8 mapped
  • 1 to confirm
  • 4 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Filevine to SharePoint

Each row is a kind of record Filevine holds, whether SharePoint has a place for it, and what is planned. On this route one kind of record carries across, eight kinds need mapping, four kinds have no place in SharePoint and are archived and one kind is confirmed in the analysis.

Records in Filevine and their place in SharePoint
RecordIn FilevineIn SharePointWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldCalled projects. Each has a project type, a phase and sections.Has a place in partAs a site, library, folder or list row the firm designs; no built-in matter record.Carried with mapping
ContactsClients, other parties and referrersHeldContact cards, collected on each project’s Contacts section.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemHeldDocs section per project, with folders, named versions and searchable text.Has a placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeHeldProject emails are stored in the activity feed.Has a place in partAs .msg or .eml files, with columns for sender and date if set up.Carried with mapping
NotesFile notes, matter notes and contact notesHeldNotes are posted to the activity feed.Has a place in partAs documents, or as rows in a notes list if one is built.Carried with mapping
CalendarAppointments, court dates and deadlinesHeldDeadlines, deadline chains and project calendars.Has a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleHeldTasks in the activity feed. Phases can create auto-tasks.Has a place in partPossible as a list; no legal workflow built in.Carried with mapping
Time and expensesTime and expense entries, billed and unbilledHeld in partTimekeeping is part of Billing, which must be enabled for the firm.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeld in partInvoices and payments through the Billing and Payments products.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeld in partPayments by Filevine includes trust accounts and a trust reconciliation report.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesTo be confirmedNo placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom sections and fields are built in the Customs Editor.Has a placeColumns and content types on libraries and lists.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument generation templates that fill from project data.Has a place in partPrecedents as files; templates can be offered from a library.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partLeads and intake are handled by Lead Docket, a separate Filevine product.No placeKept as a readable archive

What the plans mean

Carried across
SharePoint has a place for this kind of record. It is loaded there and checked against Filevine.
Carried with mapping
SharePoint 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.
Kept as a readable archive
SharePoint has no place for it. It is exported in a format that opens without Filevine and handed to the firm as a read-only archive.

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

Out of the system, into folders the firm can read.

File storage has folders and files and nothing else. Moving from Filevine into SharePoint means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters SharePoint does not allow in a name.

Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in Filevine.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Filevine depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to Filevine is kept running until the checks on SharePoint are finished.

Where the data is now

No two Filevine set-ups are alike, because each firm designs its own project types and sections. A move off it starts by reading that design: every section, every field, and how many projects actually use them. Much of the firm’s history is in the activity feed as a single stream, and the plan has to say what happens to that.

  1. Sections are the data model

    Static sections hold one set of fields per project. Collection sections hold many items, each with its own fields, such as a row per medical provider. They extract as separate tables. Each one is mapped to a destination record, a set of custom fields or a document, and the firm sees which before the trial load.

  2. The activity feed

    Notes, emails, texts, faxes, reminders and tasks all live in one feed per project, and firms tag them with hashtags. Most systems keep those things in different places. Items are split by type on the way out, so emails become emails and tasks become tasks, with the original date and author kept on each.

  3. Phases and auto-tasks

    A project’s phase can trigger automatic tasks through taskflows. The phase itself maps to a status or stage. Automation does not move, and open auto-tasks are loaded as plain tasks so work in progress still shows on someone’s list. Workflows are then rebuilt in the destination from the firm’s own list of what each phase should trigger.

  4. Archived projects still exist

    Projects cannot be deleted, only moved to the Archived phase, where they drop out of searches and reports unless specifically included. An extract that follows the default view will miss them. Archived projects are counted on their own, and the firm decides how many years of them the new system should hold.

  5. Hashtags instead of folders

    Many firms organise documents and notes with hashtags as much as with folders. A destination built on folders or categories has nowhere obvious for a tag. The most used tags are listed with counts, and each becomes a folder, a document category or text in the name, so a search for it still finds the item.

More about moving off Filevine

Where it is going

SharePoint will take a firm’s documents in almost any arrangement, which is the difficulty. The structure has to be chosen before the load: what a client is, what a matter is, and where security is applied. Changing it afterwards means moving every file again. Most of the effort goes into that design and into the columns that describe each document.

  1. Site, library or folder per matter

    A matter can be a site, a library within a client site, or a folder in one large library. Each choice has consequences for permissions, for search and for how a new matter is opened. The firm makes that decision, and the people who open matters every day should be part of it.

  2. Columns are built before content

    If documents are to carry matter number, client, document type or author as columns, those columns and any content types exist before loading, so each file can be tagged as it arrives. Tagging hundreds of thousands of documents afterwards is a second project that seldom gets finished.

  3. The 400 character path

    SharePoint limits the full decoded path, site and library and folders and file name, to 400 characters. A deep tree copied from a server drive under a long site name can cross it. Path lengths are calculated against the planned structure, not the old one, before any file moves.

  4. Large libraries and the view threshold

    A library can hold millions of files, but a view that tries to show more than 5,000 items at once runs into the list view threshold. One flat library with a folder per matter needs indexed columns and filtered views from the start, or views begin to fail as the library fills.

  5. Security by library, not by file

    Microsoft supports up to 50,000 unique permissions in a library and recommends staying under 5,000. Restricting matters one folder at a time reaches that sooner than firms expect. Restricted work is better grouped into its own site or library, so the permission is set once.

More about moving into SharePoint

How NewLaw runs it

Four steps, in this order.

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

  1. Analysis

    We read what Filevine holds and how it is organised, then agree with you where each kind of record will sit in SharePoint. 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 SharePoint and checked against Filevine: 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 Filevine, a final pass over a weekend picks up what changed since the trial. Filevine 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 Filevine 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 fromFilevine
Moving toSharePoint

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 Filevine holds

    What is in it, how its records link, and where each piece would sit in SharePoint. 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

Structure, permissions and handover

SharePoint is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.

Making SharePoint work as a firm’s document store is a design and build job in its own right. The sites, libraries, columns and permission groups are created, a way of opening a new matter is put in place so the structure repeats itself, and the Outlook and Teams habits around it are agreed. Search is tested with real questions from fee earners.

What is agreed and set up

  • Site and library structure for clients and matters
  • Columns and content types for matter number and document type
  • Permission groups, with restricted matters in their own libraries
  • A repeatable way to create each new matter’s workspace
  • Version history limits and retention labels for closed matters
  • Views, indexed columns and search tested on loaded data

Questions

Filevine to SharePoint: what firms ask

Can we take our custom sections with us when we leave?

The data in them, yes. Every static and collection section extracts as fields and rows. The section design itself belongs to Filevine and has to be recreated in whatever the destination offers. Sections that hold only a handful of records are usually better turned into notes than rebuilt.

What happens to everything in the activity feed?

It is separated by type. Notes become file notes, emails become emails where the destination stores them, texts become notes or a transcript, and tasks become tasks. Dates and authors are kept, and hashtags are carried in the text. The count of feed items per project is checked against the load, and any shortfall is listed.

We are moving to Filevine. Do matter numbers carry over?

The old matter number can be kept on the project, in the project name, a number field or both, so that paper files and old correspondence still match. Filevine also gives each project its own ID. Staff are told which number to quote, and searches are tested for the old one.

Do trust balances in Filevine have a place in SharePoint?

No. SharePoint does not keep trust ledgers. Trust records from Filevine are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.

What happens to records SharePoint has no place for?

On this route that is time entries, billing records, trust ledgers and intake records. They are exported from Filevine in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.

What has to be decided before Filevine data is loaded into SharePoint?

Matters, contacts, emails, notes, calendar entries, tasks, custom fields and templates are carried with mapping, so each mapping is agreed with you first. The firm’s accounts 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

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

Moving from Filevine to SharePoint?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.