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

Data migration route

NetDocuments to iManage Cloud migration

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

FromNetDocumentsCloud
  1. Documents: Carried across
  2. Emails: Carried across
  3. Matters: 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
ToiManage CloudCloud
  • 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 iManage Cloud

Each row is a kind of record NetDocuments holds, whether iManage Cloud 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 iManage Cloud
RecordIn NetDocumentsIn iManage CloudWhat 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 place in partAs a workspace with client and matter metadata. Parties and status stay in practice management.Carried with mapping
DocumentsFiles stored in or linked from the systemHeldEach has a unique document ID, a profile and numbered versions, one marked official.Has a placeEach needs a workspace and valid client and matter values; its class sets default security.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 placeLoaded as email documents into the workspace’s email folders.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedndThread holds team conversations. Whether a firm uses it is checked in the analysis.No placeFile notes can be loaded as documents on the matter.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedNo placeiManage Tracker is a separate product with its own set-up.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 place in partA fixed number of custom profile fields, each a validated list.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partPrecedents are stored as documents. PatternBuilder automation is a separate product.Has a place in partPrecedents load as documents. Automation is rebuilt in the firm’s drafting tools.Carried with mapping

What the plans mean

Carried across
iManage Cloud has a place for this kind of record. It is loaded there and checked against NetDocuments.
Carried with mapping
iManage Cloud 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 NetDocuments is everything around them: the profile on each document, its version history, who can open it, which workspace it sits in. iManage Cloud 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 iManage Cloud 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 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 iManage Cloud 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

Administrators of an iManage Cloud library have API access only, so nothing is loaded by writing to a database. For cloudimanage.com, the newer of its two cloud platforms, iManage lists a supervised import API, sync APIs and a metadata loader. Nothing can be filed loose: every document goes into a workspace, with valid client and matter values. So the client and matter lists, the workspace template and the security groups are built first.

  1. Client and matter lists first

    Custom1 and custom2 are validated lists, with each matter a child of its client. A value that is not already in the list cannot be assigned to a document. The lists are loaded from the practice management system or the old document store before any content, closed matters with documents included.

  2. One workspace per matter

    Each matter gets a workspace generated from a template, so the template is designed before migration: its tabs, its folders, which are created up front and which on demand. Old folder trees rarely match it. The mapping says where each old folder lands and what happens to folders with no equivalent.

  3. Authors must be known users

    Author and operator are profile fields tied to users of the library. Documents written by people who left years ago need a decision: recreate those people as inactive users, or assign a placeholder author. That choice affects searching by author for as long as the firm uses the system.

  4. Hybrid security

    iManage calls its security model hybrid: where a user’s groups disagree, the most permissive access applies unless one of them is denied. On cloudimanage.com that model cannot be changed. Default security is normally set on the workspace and inherited below it. Restricted matters from the old system are loaded with their access list already in place.

  5. New numbers, original dates

    Documents are numbered by iManage as they are loaded, so old numbers do not carry over as numbers. On cloudimanage.com the file date setting is fixed to the file’s own date, and on imanage.work it can be set either way. Which dates display is checked on the trial load. The old reference can be carried in a custom field or the description where the firm wants to search by it.

More about moving into iManage Cloud

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in iManage Cloud 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 iManage Cloud. 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 iManage Cloud 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 toiManage Cloud

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 iManage Cloud. 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 iManage Cloud

Loaded data is not yet a working system. This is what NewLaw sets up in iManage Cloud, beyond the migration, so that people can work in it from the first day.

Setting up iManage Cloud is mostly design work done before any user logs in: how many libraries, what a workspace looks like, which profile fields are captioned for what, and who can see which matters. Then come the links that keep it running day to day, such as creating a workspace when a matter is opened in the practice management system, and the add-ins on each desk.

Set-up decisions in iManage Cloud

  • Library structure and captions for client, matter and other fields
  • Workspace templates, folder names and Flexible Folders rules by practice area
  • Document classes, subclasses and the profile fields each one requires
  • Roles, groups, default security and walls for restricted matters
  • Workspace creation fed from the practice management system’s matter list
  • Work Desktop, Outlook email filing and Mobility on each device, with training

Questions

NetDocuments to iManage Cloud: 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 iManage Cloud?

iManage Cloud stores documents. Each needs a workspace and valid client and matter values; its class sets default security. 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 iManage Cloud?

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

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

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

Moving from NetDocuments to iManage Cloud?

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

We reply within one business day.