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

Data migration route

NetDocuments to Neos migration

NetDocuments is a cloud document management system, and Neos is a cloud case management system for personal injury work. The move is matching each file in NetDocuments to its case in Neos.

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

What moves

What moves from NetDocuments to Neos

Each row is a kind of record NetDocuments holds, whether Neos has a place for it, and what is planned. On this route two kinds of record carry across, three kinds need mapping and two kinds are confirmed in the analysis.

Records in NetDocuments and their place in Neos
RecordIn NetDocumentsIn NeosWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partA matter is a profile value, normally with a workspace, and can be marked closed.Has a placeCases by case type.Carried across
DocumentsFiles stored in or linked from the systemHeldEach has a unique document ID, a profile and numbered versions, one marked official.Has a placeCase Docs tab, organised in sub-tabs.Carried across
EmailsEmails saved to matters or to the storeHeldFiled from Outlook through ndMail or the Outlook add-in into the matter workspace.Has a place in partEmails tagged to a case are held. Loading old mail is scoped in the analysis.Carried with mapping
NotesFile notes, matter notes and contact notesTo be confirmedndThread holds team conversations. Whether a firm uses it is checked in the analysis.Has a placeConfirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeLoaded as checklist items.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom profile attributes, with lookup tables and parent and child links between them.Has a placeUser-defined fields are created on the relevant tab first.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partPrecedents are stored as documents. PatternBuilder automation is a separate product.Has a place in partTemplates are rebuilt for Neos document generation.Carried with mapping

What the plans mean

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

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

Where the data is now

Everything in NetDocuments is reached through the service, so a move off it is an export: documents and their versions are downloaded, and the profile values, folder paths and access lists are collected alongside as data. The files mean little without that data. A document’s place in a matter comes from its client and matter attributes, not from a folder on a disk.

  1. Profile first, folder second

    A document belongs to a matter because its client and matter attributes say so. Folders inside the workspace are optional, and many documents sit in none. An export that walks folders will miss those. The extraction is driven from the profile, cabinet by cabinet, and folder paths are added where they exist.

  2. Filters and saved searches

    Much of what users see in a workspace is not a folder at all. A filter shows documents with a given attribute, such as document type, and a saved search shows results from anywhere in the cabinet. Neither contains files. The analysis works out which of these views need a real folder in the destination.

  3. The official version

    One version of each document is marked official, and it is not always the latest. Version numbers are never reused, so a document can have versions 1 and 3 with no 2. The firm chooses between taking every version or the official one only, and the choice can differ for open and closed matters.

  4. Document IDs appear in footers

    Every document has a unique document ID that firms stamp into footers and quote in correspondence. The destination will number documents its own way. Carrying the old ID across as a field the new system can search, or as part of the name, lets someone holding a five-year-old letter still find the document it refers to.

  5. Access lists and external users

    Access is set per item as view, edit, share and administer rights for users and groups, and cabinets can include external members and CollabSpaces shared with clients. Internal restrictions are mapped to the destination’s security. What outside parties could see is listed separately, because that sharing ends when the cabinet does.

More about moving off NetDocuments

Where it is going

Neos expects personal injury data in its own tab structure, so loading a firm means deciding which tab each old record belongs on. Parties, insurance and counsel map directly from most injury systems. Money maps to value items. Anything the standard tabs lack becomes a user-defined field, which has to be created before the load.

  1. Every figure needs a value code

    Costs, medical bills, fees and settlement amounts are loaded as value items, and each carries a value code. The code list is agreed with the firm’s accounts staff first. A figure loaded under the wrong code is reported in the wrong place, so the list is tested on real cases before the bulk load.

  2. Lists are set up first

    Cases are loaded against case types, statuses and staff assignments that already exist in Neos. Those lists are set up, and the old system’s values tidied to match, before the trial load. Misspelt attorney names and unused case types in the source are cleaned out at the same stage.

  3. Documents go to sub-tabs

    Files land on the Case Docs tab under sub-tabs, which staff can view as a list or as folders. The old system’s folders or categories are mapped to a fixed set of sub-tabs. Without that, every personal habit of naming folders is reproduced and the folder view becomes hard to read.

  4. Reminders split two ways

    Neos fills its dashboards from checklists and case calendars. Old diary entries and tasks are sorted between them: dated appointments and court events to the calendar, and to-dos to the checklist. An item assigned to several people in the old system may need one named owner, and the firm chooses who.

  5. Assembly runs its own conversions

    Assembly migrates firms into Neos with its own team and tooling, and offers routes from self-service templates to a full conversion. Where the firm uses that service, outside help goes on the work around it: cleaning the source, checking the converted cases against the old system, and listing exceptions.

More about moving into Neos

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Neos on this route, which makes it repeatable: a load can be run again until it is right. The maker of Neos 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 NetDocuments and checking each trial against NetDocuments.

  1. Analysis

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

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

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

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

Neos comes set up for injury work, so implementation is mostly choosing among its options and connecting the firm’s other tools. The lists that drive reporting are decided first, then checklists, then documents. Assembly provides its own implementation team, and the firm’s internal lead still has to make the decisions listed below.

Set-up decisions in Neos

  • Set case types, statuses and staff roles
  • Agree the value code list with accounts staff
  • Build checklists for each case type and stage
  • Create user-defined fields for data the tabs lack
  • Prepare document templates for the generation wizard
  • Connect Microsoft 365, QuickBooks and the phone system

Questions

NetDocuments to Neos: what firms ask

Can we export everything from NetDocuments ourselves?

Partly. NetDocuments provides ndWeb Export, which lets authorised users export documents to a location an administrator has approved. That suits a matter or a client. A whole cabinet with versions, profile data and access lists needs a planned extraction, and the counts are checked against the cabinet afterwards.

Will our document IDs survive the move?

Not as live identifiers. The document ID belongs to NetDocuments and the next system numbers documents its own way. The old ID can be carried as a field or in the document name, so that references in footers, emails and bundles can still be looked up. Links pasted into documents point at NetDocuments, not at the new system.

What happens to documents nobody profiled properly?

They are found in the analysis: documents with no matter, or filed to a general or miscellaneous matter. The firm gets a list with counts by author and date. Some can be assigned by rule, for example from the folder they sit in. The rest are loaded to a holding area or left in the read-only copy.

Do documents from NetDocuments keep their folders and dates in Neos?

Neos stores documents. Case Docs tab, organised in sub-tabs. 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 NetDocuments have a place in Neos?

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

What has to be decided before NetDocuments data is loaded into Neos?

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

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

Moving from NetDocuments to Neos?

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

We reply within one business day.