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

Data migration route

Box to iManage Cloud migration

Box is cloud file storage, and iManage Cloud 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
ToiManage CloudCloud
  1. Notes: Kept as a readable archive
  2. Tasks: Kept as a readable archive
Readable archiveNo place in iManage Cloud
  • 2 carried
  • 2 mapped
  • 2 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Box to iManage Cloud

Each row is a kind of record Box holds, whether iManage Cloud has a place for it, and what is planned. On this route two kinds of record carry across, two kinds need mapping and two kinds have no place in iManage Cloud and are archived.

Records in Box and their place in iManage Cloud
RecordIn BoxIn iManage CloudWhat is planned
DocumentsFiles stored in or linked from the systemHeldFiles in folders, with version history, comments and optional metadata.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 storeHeld in partOnly as message files saved or emailed into a folder.Has a placeLoaded as email documents into the workspace’s email folders.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 can be loaded as documents on the matter.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.No placeiManage Tracker is a separate product with its own set-up.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfHeld in partMetadata templates add fields to files and folders.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 kept as ordinary files; Box Notes has its own note templates.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 Box.
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.
Kept as a readable archive
iManage Cloud 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 iManage Cloud, 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 iManage Cloud, 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 iManage Cloud 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

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

Box to iManage Cloud: 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 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.

What happens to records iManage Cloud has no place for?

On this route that is notes and tasks. 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 iManage Cloud?

Custom fields and 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

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

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