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

Data migration route

OneDrive to NetDocuments migration

OneDrive is cloud file storage, and NetDocuments is a cloud document management system. The move adds structure the folders never had: a client, a matter and a document type for every file.

FromOneDriveCloud
  1. Documents: Carried across
  2. Emails: Carried across
  3. Templates: Carried with mapping
ToNetDocumentsCloud
  1. Notes: Kept as a readable archive
Readable archiveNo place in NetDocuments
  • 2 carried
  • 1 mapped
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from OneDrive to NetDocuments

Each row is a kind of record OneDrive holds, whether NetDocuments has a place for it, and what is planned. On this route two kinds of record carry across, one kind needs mapping and one kind has no place in NetDocuments and is archived.

Records in OneDrive and their place in NetDocuments
RecordIn OneDriveIn NetDocumentsWhat is planned
DocumentsFiles stored in or linked from the systemHeldFiles in one user’s drive, with version history and sharing per file or folder.Has a placeImported with profile values, folder, dates and access set per document.Carried across
EmailsEmails saved to matters or to the storeHeld in partOnly messages saved as .msg or .eml files; mailboxes are in Exchange Online.Has a placeLoaded as email items profiled to the matter.Carried across
NotesFile notes, matter notes and contact notesHeld in partOneNote notebooks stored in OneDrive, which sync by their own mechanism.No placeFile notes are loaded as documents in the matter workspace.Kept as a readable archive
TemplatesPrecedents, document templates and automationHeld in partPrecedents sit in a folder as normal Word files.Has a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh.Carried with mapping

What the plans mean

Carried across
NetDocuments has a place for this kind of record. It is loaded there and checked against OneDrive.
Carried with mapping
NetDocuments holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
Kept as a readable archive
NetDocuments has no place for it. It is exported in a format that opens without OneDrive 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

Folders go in. Profiled workspaces come out.

A document management system asks questions of every file that a folder never did: which client, which matter, what type of document, who wrote it. Coming from OneDrive, the answers have to be worked out from where a file sits and what it is called. The analysis reads the folder tree, proposes how its levels map to client, matter and folder in NetDocuments, and lists what does not fit. Those exceptions go to the firm as a spreadsheet to correct.

Not everything should move. Shared drives collect installers, duplicates, personal files and working copies ten versions deep. The firm decides what is in scope by folder, by age or by file type, and the rest is left where it is or archived. File dates are preserved. Paths too long for NetDocuments, characters it does not allow and files that will not open are reported before the load. The copy can be repeated, so the final pass picks up only what changed.

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

Where the data is now

Firm files in OneDrive are firm files held in personal storage, and that shapes the whole move. There is no single place to collect from. Each person has a drive, arranged the way its owner likes, with folders shared sideways between colleagues. The analysis starts with a plain list of which drives hold matter files.

  1. One drive per person

    A matter may have its pleadings in the partner’s OneDrive, its correspondence in the secretary’s and its research in a clerk’s. Each drive is inventoried separately and the folders are matched to matters by name. Where the same matter turns up in more than one drive, the firm chooses how the copies are combined.

  2. Leavers’ drives are on a timer

    When a user account is deleted, Microsoft keeps that person’s OneDrive for a retention period, 30 days unless the firm changed it, and then removes it. The manager is given access in the meantime. A departed fee earner’s drive is dealt with first, because that timer does not wait for the project.

  3. Desktop and Documents may be inside

    Where known folder redirection is on, a person’s Desktop, Documents and Pictures are in their OneDrive. Collecting the whole drive brings holiday photos and personal paperwork with the matter files. Each person marks what is the firm’s, and private folders are excluded by path before collection.

  4. Shared items live elsewhere

    A folder that appears under Shared in someone’s OneDrive is stored in the drive of the person who shared it. It is collected once, from its owner. Counting it again from every colleague who can see it is how a document total ends up several times too large.

  5. OneNote notebooks are a special case

    A notebook saved in OneDrive syncs through OneNote, not through the sync app, and shows on disk only as a small link file. Lawyers who keep matter notes in OneNote need those notebooks exported from OneNote itself. Copying the folder brings the link and none of the pages.

More about moving off OneDrive

Where it is going

Loading into NetDocuments means every document arrives with a profile. The cabinet, its profile attributes and the client and matter lookup tables are built first. Documents are then imported with an instruction file that says, line by line, which file gets which client, matter, author, document type, folder and access. Preparing that file from the old system’s data is most of the work.

  1. Lookup tables before documents

    Client and matter are validated attributes, with matter the child of client. A value missing from the lookup table cannot be used to profile a document. The tables are loaded from the practice management system first, closed matters included, and each matter is flagged open or closed so old ones stay out of pick lists.

  2. Workspaces come from the profile

    A workspace shows whatever is profiled to its matter. So the question is not where to put a folder tree but how to profile each file. Old folder names are often turned into a document type attribute, or kept as a workspace folder, and the mapping decides which for each one.

  3. Import files are unforgiving

    The import file is comma-separated text, and NetDocuments itself warns that opening one in Excel can strip leading zeros from numbers and alter dates. A matter number of 00123 that becomes 123 will not match its lookup value. The files are kept as plain text from start to finish and are not opened in a spreadsheet.

  4. Folder limits and depth

    A folder can hold any number of documents but no more than 500 subfolders. Deep trees copied from a file server also work against the way the system is searched. Where a matter arrives with hundreds of nested folders, the plan flattens them and keeps the lost path in the document name or an attribute.

  5. Security at the right level

    Access can be set on the cabinet, by profile value, on a workspace or on a single document. Restricted matters are best carried as workspace or profile-based security, so that new documents pick it up. Document-by-document access lists copied from an old system are loaded only where the restriction was real.

More about moving into NetDocuments

How NewLaw runs it

Four steps, in this order.

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

  1. Analysis

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

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

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

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

Beyond the load, NetDocuments has to be designed: how many cabinets the firm needs, which profile attributes every document must carry, and what a new matter’s workspace looks like on its first day. After that it is connected to the practice management system so client and matter lists stay current, and ndOffice and the email filing tools are set up for each person, with training on profiling.

Set-up decisions in NetDocuments

  • Cabinet design: one for the firm, or several by purpose
  • Profile attributes, lookup tables and the client and matter hierarchy
  • Workspace layout with default folders, filters and saved searches
  • User groups, cabinet membership and security for restricted matters
  • A feed of new clients and matters from practice management
  • ndOffice, ndMail and Outlook filing on every desk, with training

Questions

OneDrive to NetDocuments: what firms ask

A solicitor left last month and her matters were in her OneDrive. Is it too late?

Probably not, but it is urgent. After an account is deleted the drive is kept for a retention period, 30 days by default, and then sits in a recycle bin for a further period before it is gone. An administrator can give another user access now. It should be raised in the first conversation, ahead of any other planning.

Will our file names change?

Only where the destination cannot accept them. Moving out of OneDrive, most names are already safe because OneDrive is stricter than a Windows folder. The exceptions are very long paths, which a desktop system or a server drive may not open, and those are listed with the shortened names proposed.

Do earlier versions of documents come with them?

OneDrive keeps version history within limits an administrator sets, so there are often earlier versions to bring. Document management systems can usually receive them as versions. A destination that files plain documents against a matter generally takes the latest only, and the firm decides whether earlier ones are kept as extra files.

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

NetDocuments stores documents. Imported with profile values, folder, dates and access set per document. 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 NetDocuments has no place for?

On this route that is notes. They are exported from OneDrive 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 OneDrive data is loaded into NetDocuments?

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

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

Moving from OneDrive to NetDocuments?

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

We reply within one business day.