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

Data migration route

NetDocuments to Server drives migration

NetDocuments is a cloud document management system, and Server drives are plain files on equipment the firm controls. Storage only has folders, so the move decides what of each document’s profile is kept in names and what in an index.

FromNetDocumentsCloud
  1. Documents: Carried across
  2. Emails: Carried with mapping
  3. Templates: Carried with mapping
  4. Notes: Confirmed in the analysis
  5. Tasks: Confirmed in the analysis
ToServer drivesFiles
  1. Matters: Kept as a readable archive
  2. Custom fields: Kept as a readable archive
Readable archiveNo place in Server drives
  • 1 carried
  • 2 mapped
  • 2 to confirm
  • 2 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from NetDocuments to Server drives

Each row is a kind of record NetDocuments holds, whether Server drives have a place for it, and what is planned. On this route one kind of record carries across, two kinds need mapping, two kinds have no place in Server drives and are archived and two kinds are confirmed in the analysis.

Records in NetDocuments and their place in Server drives
RecordIn NetDocumentsIn Server drivesWhat 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.No placeA matter becomes a folder; its details survive only in an index file.Kept as a readable archive
DocumentsFiles stored in or linked from the systemHeldEach has a unique document ID, a profile and numbered versions, one marked official.Has a placeFiles in folders, named and dated during the load.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 partAs .msg or .eml files in each matter’s correspondence folder.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 place in partAs a text or PDF file per matter, not as separate records.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedNo placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldCustom profile attributes, with lookup tables and parent and child links between them.No placeKept as a readable archive
TemplatesPrecedents, document templates and automationHeld in partPrecedents are stored as documents. PatternBuilder automation is a separate product.Has a place in partPrecedents as Word files; merge fields tied to the old system stop working.Carried with mapping

What the plans mean

Carried across
Server drives has a place for this kind of record. It is loaded there and checked against NetDocuments.
Carried with mapping
Server drives 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
Server drives has no place for it. It is exported in a format that opens without NetDocuments 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

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 NetDocuments to Server drives 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 Server drives before anyone else is given access.

NetDocuments is hosted by its maker and Server drives sit on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What NetDocuments will release depends on its export tools, and that is confirmed in the analysis.

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

Some firms leave a practice or document system and keep their documents on a server drive, either as the working store or as the archive of a system being switched off. The files will arrive without the database that described them. Everything the firm wants to keep knowing about a document has to be put into its path, its name or an index file.

  1. Agree the tree and the names

    A fixed pattern is chosen, for example client name and number, then matter number and short description, then a standard set of subfolders. Document titles from the old system become file names. Where two documents share a title, a date or sequence number is added so nothing is overwritten.

  2. Budget the path length

    Share name, client, matter, subfolder and file name all count towards the 260 character limit that many Windows programs still apply. The pattern is tested against the firm’s longest client names and document titles before the load. Descriptions are trimmed by rule, never by cutting off the file extension.

  3. Dates have to be set deliberately

    A file written to the server today is dated today unless its modified date is set from the old system’s record. Document dates are how lawyers find things in a folder. Which date each file is to carry is agreed in the analysis, and the trial load checks a sample.

  4. Emails become message files

    Emails filed to matters in the old system are written out as .msg or .eml files in a correspondence folder, named by date, sender and subject so they sort in order. Attachments stay inside the message. Subjects with characters Windows forbids are cleaned, and long ones cut.

  5. Keep an index beside the files

    A spreadsheet or small database listing every document with its matter, author, original date, document type and new path is the only place the old system’s profile data survives. It lets someone find a document by something other than its name. What the index records, and who keeps it, is decided in the analysis.

More about moving into Server drives

How NewLaw runs it

Four steps, in this order.

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

  1. Analysis

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

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 Server drives. 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

Server drives are 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.

A server drive does only what the firm and its IT provider make it do. Setting one up as a document store means building the share, deciding who can open which folders, and arranging the protections a document system would have supplied: backups, earlier versions and a way to recover a deleted folder. The filing rule is written down and taught.

What is agreed and set up

  • Share and top-level folders for clients, precedents and administration
  • Security groups and folder permissions, with restricted matters separate
  • Drive letter mapped for every user at sign-in
  • Backup schedule and shadow copies for earlier versions
  • Written naming rule for client, matter and document names
  • Read-only area for closed matters and archived system exports

Questions

NetDocuments to Server drives: 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 Server drives?

Server drives store documents. Files in folders, named and dated during the load. 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.

What happens to records Server drives have no place for?

On this route that is matters and custom fields. They are exported from NetDocuments 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 NetDocuments data is loaded into Server drives?

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

Moving from NetDocuments to Server drives?

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

We reply within one business day.