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

Data migration route

Zoho WorkDrive to iManage Cloud migration

Zoho WorkDrive 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.

FromZoho WorkDriveCloud
  1. Documents: Carried across
  2. Emails: Carried across
  3. Custom fields: Carried with mapping
  4. Templates: Carried with mapping
ToiManage CloudCloud
  • 2 carried
  • 2 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Zoho WorkDrive to iManage Cloud

Each row is a kind of record Zoho WorkDrive holds, whether iManage Cloud has a place for it, and what is planned. On this route two kinds of record carry across and two kinds need mapping.

Records in Zoho WorkDrive and their place in iManage Cloud
RecordIn Zoho WorkDriveIn iManage CloudWhat is planned
DocumentsFiles stored in or linked from the systemHeldFiles in Team Folders and My Folders, including Zoho Writer, Sheet and Show documents.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 messages saved into a folder as files.Has a placeLoaded as email documents into the workspace’s email folders.Carried across
Custom fieldsFields and record types the firm added itselfHeld in partLabels and Data Templates attach classification fields to files.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 files, often in Zoho Writer format.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 Zoho WorkDrive.
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.

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 Zoho WorkDrive, 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 Zoho WorkDrive 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 Zoho WorkDrive is kept running until the checks on iManage Cloud are finished.

Where the data is now

WorkDrive is rarely a firm’s only Zoho product, and the move off it is cleaner when that is faced at the start. The documents are here. Client and matter records that explain them may be in Zoho CRM or another Zoho app. Collecting the files without the records that give them a matter number leaves a tree of folders to be matched by name.

  1. Team Folders and My Folders

    Team Folders are the firm’s and can be listed by an administrator. My Folders are each person’s private space, and matter drafts end up there more often than anyone admits. Staff are asked to move firm documents into the right Team Folder before collection, or to identify the personal folders that should be taken.

  2. Writer, Sheet and Show documents

    Documents created in Zoho’s editors are in Zoho formats. A destination built around Microsoft Word needs them converted to .docx, .xlsx or PDF on the way out. Merge fields, comments and tracked changes are where conversions go wrong, so a sample of the firm’s real precedents is converted and read before the full run.

  3. Labels and Data Templates

    If the firm classified documents with labels or Data Templates, that classification is stored in WorkDrive and not in the file. It has to be exported alongside each document. Where the destination has document types or profile fields, the values are mapped to them. Otherwise they are written into the file name.

  4. Five roles to translate

    Access in a Team Folder is by role: Admin, Organizer, Editor, Commenter or Viewer. Few destinations have the same five. The firm’s actual need is usually simpler, a list of who may open which matters, and that list is drawn from the role assignments and confirmed with a partner.

  5. Unlimited versions, limited use

    Zoho describes version history in WorkDrive as unlimited, so a long-lived precedent may have hundreds of versions. Bringing them all is seldom useful. The firm sets a rule, such as the latest version only for closed matters and the last few for open ones, before volumes are estimated.

More about moving off Zoho WorkDrive

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

Zoho WorkDrive to iManage Cloud: what firms ask

We also use Zoho CRM for clients. Is that part of the same move?

It should be looked at together even if it is moved separately. The CRM is where client names, contact details and often matter references are held, and WorkDrive folders are usually named after them. Reading both lets each folder be tied to the right client and matter in the new system without guesswork.

Will our Zoho Writer precedents work in Word?

The text and most formatting convert. Automation does not carry over by itself: merge fields that pulled data from Zoho have to be rebuilt against the new system’s fields. Precedents are therefore handled as a small project of their own, starting with the documents the firm uses every week.

Can we keep WorkDrive for closed matters?

Yes, for as long as the subscription runs. The practical points are that at least one current staff member keeps an Admin role on each Team Folder, and that the closed matters are set to view only so nothing is filed there by habit after go-live. Both are checked at handover.

Do documents from Zoho WorkDrive 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 Zoho WorkDrive have a place in iManage Cloud?

On paper, yes: each kind of record Zoho WorkDrive holds has a place in iManage Cloud. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.

What has to be decided before Zoho WorkDrive 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

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

Moving from Zoho WorkDrive 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.