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

Data migration route

Google Drive to iManage Cloud migration

Google Drive 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.

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

What moves

What moves from Google Drive to iManage Cloud

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

Records in Google Drive and their place in iManage Cloud
RecordIn Google DriveIn iManage CloudWhat is planned
DocumentsFiles stored in or linked from the systemHeldUploaded files plus Google Docs, Sheets and Slides, which are not files until exported.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 to Drive as files; mail itself is in Gmail.Has a placeLoaded as email documents into the workspace’s email folders.Carried across
TemplatesPrecedents, document templates and automationHeld in partPrecedents kept as files or as Google Docs that staff copy.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 Google Drive.
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 Google Drive, 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 Google Drive 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 Google Drive is kept running until the checks on iManage Cloud are finished.

Where the data is now

Two things set a move off Google Drive apart from a move off any other drive. Much of the content is in Google’s own formats and has to be converted on the way out. And ownership is personal unless the firm used shared drives, so the files for one matter can be scattered across the accounts of everyone who ever worked on it.

  1. Docs, Sheets and Slides convert

    A Google Doc has no file behind it. On the way out it is saved as Word or PDF, a Sheet as Excel. The document’s revision history stays in Google, and links from one Doc to another still point back there. How layout, comments and suggestions come through is checked on a sample. The firm picks the output format per document type.

  2. My Drive files belong to people

    Every file in My Drive has one owner. A matter folder shared across the firm can contain files owned by six different accounts, some of them former staff. An administrator can transfer a user’s files to a new owner, and that is done for leavers before their accounts are touched.

  3. Shortcuts are not the file

    A shortcut in a matter folder points to a file stored somewhere else, often in another person’s drive. Copied naively it arrives as an empty pointer. Shortcuts are resolved to the real document during collection, and where the target can no longer be reached the gap is reported.

  4. Names Windows cannot hold

    Drive lets two files in one folder share a name, and Windows does not. Windows and SharePoint also refuse certain characters in names. Both are looked for in the analysis. Duplicated names are numbered and refused characters replaced by an agreed rule before loading, with the changes listed against the original names.

  5. Old versions of uploads expire

    For an uploaded file such as a PDF or Word document, Drive may delete an earlier version after 30 days or once there are 100 newer ones, unless someone marked it Keep forever. Earlier drafts the firm assumes are there may not be. What exists is counted in the analysis.

More about moving off Google Drive

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

Google Drive to iManage Cloud: what firms ask

What happens to our Google Docs when we move to a system that uses Word?

Each Doc is converted to a Word file, or to PDF where it is a finished document that should not change. Documents with heavy tables, drawings or linked Sheets are the ones checked by eye on a sample. The originals stay in Google, read only, until the firm is satisfied.

Some matter files are owned by people who have left. Are they lost?

Not if the account still exists, even suspended. A Workspace administrator can transfer its files to a current user, and that is done first. Where an account was deleted some time ago its My Drive files are gone, and the analysis will show the affected matters by the gaps in their folders.

Do we move Gmail and Calendar as well?

They are separate from Drive and are scoped separately. A firm can keep Google Workspace for mail and calendar and move only its matter files into a practice or document system. If emails need to sit on matters, the question is which mailboxes and labels are filed, and that is answered in the analysis.

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

On paper, yes: each kind of record Google Drive 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 Google Drive data is loaded into iManage Cloud?

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

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

Moving from Google Drive 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.