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

Data migration route

Docrio to SharePoint migration

Docrio is a cloud document management system, and SharePoint is cloud file storage. Storage only has folders, so the move decides what of each document’s profile is kept in names and what in an index.

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

What moves

What moves from Docrio to SharePoint

Each row is a kind of record Docrio holds, whether SharePoint has a place for it, and what is planned. On this route one kind of record carries across, one kind needs mapping and three kinds are confirmed in the analysis.

Records in Docrio and their place in SharePoint
RecordIn DocrioIn SharePointWhat is planned
DocumentsFiles stored in or linked from the systemHeldFiled against Litify matters, with tags and editable file information.Has a placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partAs .msg or .eml files, with columns for sender and date if set up.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedTasks can be raised against a document; they are Litify records.Has a place in partPossible as a list; no legal workflow built in.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeColumns and content types on libraries and lists.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldDocument generation templates with merge fields and conditional logic.Has a place in partPrecedents as files; templates can be offered from a library.Carried with mapping

What the plans mean

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

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

Profiles flatten into folders and an index.

A document management system knows things about a file that a folder cannot hold: its profile, its versions, who may open it. Moving from Docrio to SharePoint flattens that. Client and matter become folder levels. Document type may become a subfolder. Versions become separate files with a suffix, or only the latest is kept. Each of these is a choice the firm makes before the export, and the result is tested on a sample of real matters.

What the folders cannot carry goes into an index: a spreadsheet listing every exported file with its document number, author, dates, type and original location. With it, a document cited by number in an old email can still be found. Access restrictions do not transfer by themselves. Restricted workspaces are exported to separate folders, and permissions are set on those in SharePoint before anyone else is given access.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Docrio 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 Docrio is kept running until the checks on SharePoint are finished.

Where the data is now

Docrio cannot be separated from the Litify system it sits in. Each file is tied to a Litify record, and that record supplies the matter number, client and case type. Leaving it means extracting the files together with the identifiers of the records they hang from. Usually it happens as part of moving the whole Litify system, not the documents alone.

  1. Files hang off Litify records

    A document’s context is the record it was saved to, normally a matter. That relationship is how a file finds its matter in the destination. Keeping the record identifier with every file is what allows it to be joined to the matter export and filed under the right matter.

  2. Folders and tags by case type

    Litify firms normally set a standard folder structure for each case type and add tags on top. The structure for a motor vehicle claim differs from the one for a mass tort. Each case type’s folder set is mapped separately, and tags become document categories or are written into the name.

  3. Templates do not travel

    Generation templates read fields from Litify by name. In another system those fields are called something else, or do not exist. The documents already generated move as ordinary files. The templates themselves are rebuilt in the destination’s own automation, starting with the ones the firm uses most.

  4. Confirm where files are stored

    How Docrio stores file content, and the route for exporting it in bulk, is confirmed with the firm’s Litify administrator at the start. Access is given in whatever way the firm decides. Volumes in injury practices are large, with medical records and video, so transfer time is part of the plan.

More about moving off Docrio

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 Docrio 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 Docrio: 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 Docrio, a final pass over a weekend picks up what changed since the trial. Docrio 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 Docrio 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 fromDocrio
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 Docrio 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

Docrio to SharePoint: what firms ask

We are leaving Litify. Are our documents part of that move?

They should be scoped explicitly. A matter export on its own should not be assumed to contain the documents, and the files may come out by a different route from the Litify data. The plan covers both and joins them on the matter, and document counts are checked per matter after the trial load.

Can we keep Litify and move only the documents to iManage or NetDocuments?

Litify publishes integrations with both, so that arrangement exists. The existing files are then moved from Docrio into workspaces that match the Litify matters, and new documents are saved through the integration. The matter number is the join, so it has to be identical on both sides before the load.

Do documents from Docrio keep their folders and dates in SharePoint?

SharePoint stores documents. Files in libraries, with columns and versions. 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 Docrio have a place in SharePoint?

Most of it does on paper. Emails, tasks and custom fields 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 SharePoint is kept as a readable archive, and you see which before the move.

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

Templates are carried with mapping, so each mapping is agreed with you first. Emails, tasks and custom fields 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

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

Moving from Docrio 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.