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

Data migration route

Docrio to LexWorkplace migration

Docrio and LexWorkplace are each a cloud document management system. The test of this move is whether profiles, versions and access rules survive it.

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
ToLexWorkplaceCloud
  • 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 LexWorkplace

Each row is a kind of record Docrio holds, whether LexWorkplace 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 LexWorkplace
RecordIn DocrioIn LexWorkplaceWhat is planned
DocumentsFiles stored in or linked from the systemHeldFiled against Litify matters, with tags and editable file information.Has a placeFiled to a matter or to Firm Documents, in folders.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeOn the matter’s Email tab, in their own folders.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedTasks can be raised against a document; they are Litify records.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a place in partOld categories can become document types, statuses or tags.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeldDocument generation templates with merge fields and conditional logic.Has a place in partStored as files in Firm Documents.Carried with mapping

What the plans mean

Carried across
LexWorkplace has a place for this kind of record. It is loaded there and checked against Docrio.
Carried with mapping
LexWorkplace 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, versions and security, kept intact.

Between two document management systems the files are the easy part. What a firm has built in Docrio is everything around them: the profile on each document, its version history, who can open it, which workspace it sits in. LexWorkplace has its own model for each. Document types and custom profile fields are mapped one to one where they can be. Versions are loaded in order, so the latest in the old system is the latest in the new one.

Security is checked on its own. A restricted client or an information barrier must arrive restricted, so access groups are created in LexWorkplace before any document is loaded, and a sample of restricted workspaces is tested with a user who should not see them. Document numbers are worth keeping, since they appear in footers and old emails. Where the new system assigns its own, the old number is stored as a searchable field.

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 LexWorkplace 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

LexWorkplace expects every document and email to belong to a matter, so loading it starts with the matter list: name, custom ID, client, type and dates. Uptime Legal states that it runs migration and onboarding for its customers itself. The preparation is getting the old system’s content into a clean client and matter structure, with the exceptions resolved, ready for that load.

  1. Matters carry little, by design

    A matter record holds a name, a custom ID, a client, a type, a location, assigned staff, tags and open and close dates. Parties, court details and financial data have no fields. Those stay in the practice management system, and the two are tied together by using the same matter number as the custom ID.

  2. Clients are only containers

    LexWorkplace says plainly that its clients are for grouping matters, not for client management. A client has a name, a status, primary attorneys and tags. Addresses, phone numbers and contact history from the old system are not loaded here. They go to the practice management system or stay behind.

  3. Three tabs per matter

    Content arrives as documents, emails or notes, each on its own tab with its own folders. Emails held as message files in an old folder tree have to be recognised and loaded as emails, not as documents, or they will not appear where lawyers look for correspondence.

  4. Closed matters and archive

    A matter is closed by giving it a close date, and closed matters can be moved to archive storage, where they keep their place but are not searched or indexed until un-archived. Old matters can therefore be loaded and archived straight away. The firm sets the cut-off year.

  5. Profiling is optional unless enforced

    Document type, status and tags are not required by default, though a firm can switch on mandatory profiling for matters. If the old system had document types, they are mapped to LexWorkplace types during the load. If it had none, the firm chooses between loading unprofiled and assigning types by folder name.

More about moving into LexWorkplace

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in LexWorkplace on this route, which makes it repeatable: a load can be run again until it is right. The maker of LexWorkplace says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in Docrio and checking each trial against Docrio.

  1. Analysis

    We read what Docrio holds and how it is organised, then agree with you where each kind of record will sit in LexWorkplace. 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 LexWorkplace 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 toLexWorkplace

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

Loaded data is not yet a working system. The maker of LexWorkplace runs or arranges the set-up of its product, so this is what has to be decided and put in place in LexWorkplace, whoever does the work, before people rely on it from the first day.

Setting LexWorkplace up for a firm is a short list of decisions made in its settings, plus software on each computer. The decisions are what the firm calls its matter types, document types and statuses, who can open which matters by default, and whether versioning is automatic or manual. The Launcher and the Outlook add-in are then installed for every user.

Set-up decisions in LexWorkplace

  • Matter types, document types, statuses and tag conventions
  • Groups, rights and default permissions for new matters
  • Automatic or manual versioning, and whether profiling is mandatory
  • Linking matters to Clio Manage where the firm uses it
  • Launcher, Office and Outlook add-ins on each Windows or Mac computer
  • A Firm Documents structure for templates, policies and internal files

Questions

Docrio to LexWorkplace: 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 LexWorkplace?

LexWorkplace stores documents. Filed to a matter or to Firm Documents, in folders. 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 LexWorkplace?

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 LexWorkplace is kept as a readable archive, and you see which before the move.

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

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 LexWorkplace are the names and marks of their owners, used here only to identify the two systems.

Moving from Docrio to LexWorkplace?

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

We reply within one business day.