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

Data migration route

Box to NetDocuments migration

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

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

What moves

What moves from Box to NetDocuments

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

Records in Box and their place in NetDocuments
RecordIn BoxIn NetDocumentsWhat is planned
DocumentsFiles stored in or linked from the systemHeldFiles in folders, with version history, comments and optional metadata.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 as message files saved or emailed into a folder.Has a placeLoaded as email items profiled to the matter.Carried across
NotesFile notes, matter notes and contact notesHeld in partBox Notes are documents written inside Box, not notes recorded against a matter.No placeFile notes are loaded as documents in the matter workspace.Kept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeld in partTasks can be assigned on a file; they are not matter tasks.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeld in partMetadata templates add fields to files and folders.Has a placeAs custom profile attributes, created in the repository before the load.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partPrecedents are kept as ordinary files; Box Notes has its own note templates.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 Box.
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.
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
NetDocuments has no place for it. It is exported in a format that opens without Box 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 Box, 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 Box 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 Box is kept running until the checks on NetDocuments are finished.

Where the data is now

Leaving Box is mostly a question of ownership and of what is attached to files but not inside them. Folders belong to whoever created them unless the firm set Box up with administrator-owned folders. Comments, tasks, metadata values and earlier versions live in Box beside each file. A plain download brings the current files and none of the rest.

  1. Every top-level folder has an owner

    Box lets either administrators or ordinary users own top-level folders, depending on how the account was set up. Where users own them, matter files are spread across personal accounts, including those of people who have left. The inventory is taken from the administrator’s side so that nobody’s folders are missed.

  2. Each person sees a different tree

    A collaborator invited part-way down sees that folder as their own top level. Two lawyers describing the same matter folder may give different paths to it. The structure that moves is the owner’s full tree, and staff are shown where their familiar folders sit within it before go-live.

  3. Box Notes are not Word files

    Notes written in Box Notes exist only inside Box. They are not files in the usual sense and do not open in Word. Firms that kept file notes or meeting minutes this way need them converted to a document format before the move, and the conversion is checked on a sample in the trial load.

  4. Shared links point at Box

    Clients and other parties may hold links to matter folders or single documents. Those links point at Box and cannot be relied on once the account is closed. A report of links and outside collaborators shows which matters have live external access, so the firm can tell those people where documents will be from cutover.

  5. Versions depend on the plan

    How many earlier versions of a file Box keeps is set by the plan and can be reduced by an administrator. What is not there cannot be moved. Where versions do exist, the destination may take them as true versions or only as separately named copies, which is settled in the analysis.

More about moving off Box

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 Box 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 Box: 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 Box, a final pass over a weekend picks up what changed since the trial. Box 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 Box 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 fromBox
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 Box 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

Box to NetDocuments: what firms ask

Do our document versions come across from Box?

Only versions Box still holds can be moved, and that number depends on the plan. How they arrive depends on the destination: a document management system usually has version slots, a plain drive does not. The trial load can show one sample matter both ways if the firm is undecided.

What happens to folders we shared with clients?

The collaborators and shared links belong to Box and do not transfer. Before cutover the firm gets a list of every folder with outside access. If the new system has a client portal or its own sharing, access is set up there, and clients are told where to find their documents from then on.

Can we move only open matters and leave the rest in Box?

Yes, if the folder names or metadata show which matters are open. Where they do not, the open matter list from the practice management system is matched to folders by client and matter number. Closed folders can stay in Box read only for as long as the firm keeps the subscription.

Do documents from Box 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 Box 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 Box data is loaded into NetDocuments?

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

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

Moving from Box 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.