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

Data migration route

iManage Cloud to Clio Manage migration

iManage Cloud is a cloud document management system, and Clio Manage is a cloud practice management system. Documents and email move out of a store organised by profile and onto the matters they belong to.

FromiManage CloudCloud
  1. Matters: Carried across
  2. Documents: Carried across
  3. Emails: Carried across
  4. Tasks: Carried across
  5. Custom fields: Carried with mapping
  6. Templates: Carried with mapping
ToClio ManageCloud
  • 4 carried
  • 2 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from iManage Cloud to Clio Manage

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

Records in iManage Cloud and their place in Clio Manage
RecordIn iManage CloudIn Clio ManageWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partOne workspace per matter is the norm. It carries client and matter values, not parties or status.Has a placeImported from a matters template, after contacts.Carried across
DocumentsFiles stored in or linked from the systemHeldProfiled, numbered and versioned, and always filed inside a workspace.Has a placeFiled under the matter; Clio scopes document migration separately from data.Carried across
EmailsEmails saved to matters or to the storeHeldFiled from Outlook and held as documents with sender, recipients and sent date.Has a placeHeld as communications on the matter, with phone logs.Carried across
TasksTo-dos and workflow steps assigned to peopleHeld in partThrough iManage Tracker, which is sold separately and integrates with Work.Has a placeTasks have a migration template.Carried across
Custom fieldsFields and record types the firm added itselfHeldCustom1 to custom12, custom29 and custom30 hold validated lists the firm captions itself.Has a placeCreated first, then filled from the custom field templates.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partPrecedents are stored as ordinary documents, wherever the firm chose to keep them.Has a placeRebuilt as Clio document templates with its merge fields.Carried with mapping

What the plans mean

Carried across
Clio Manage has a place for this kind of record. It is loaded there and checked against iManage Cloud.
Carried with mapping
Clio Manage 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

Profiled documents become matter documents.

A document management system files by profile: client, matter, author, document type, version. A practice management system files by matter. The move from iManage Cloud to Clio Manage is a translation from one to the other, and it depends on the client and matter numbers in iManage Cloud matching matters that exist in Clio Manage. Where they do not match, documents have nowhere to land. So the matter list is settled first and the documents follow it.

Versions and security each need a decision. Some practice systems keep every version of a document, others keep the latest and treat the rest as separate files. A restricted workspace has to become a restricted matter, or the restriction is lost on the way. Filed email comes across as message files against the matter. A document store holds no ledgers, so this route has no financial cutover.

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

Where the data is now

Administrators of a cloud library have API access and no SQL access, so documents, versions, profiles and permissions are read out through the API. That makes extraction slower to plan than on a server the firm owns. The trial load matters more than usual, because it is the first time the counts can be checked against what Control Center reports.

  1. Extraction runs through the API

    With no database to query, every document, version, profile and permission is requested through the REST API. A large library takes planning: which libraries go first, how long a full pass takes, and how the changes made since that pass are collected before cutover.

  2. Trash and Journal content

    On cloudimanage.com, the newer of the two cloud platforms, Trash and Journal are always enabled. They are not part of the live matter file. The firm decides whether deleted items and journal content are in scope. If nothing is said, they stay behind.

  3. Workspaces follow a template

    Workspaces are created from templates, and with Flexible Folders switched on the template controls which folders may exist at each level. That gives a cloud library a regular shape, with the same folder names recurring across thousands of matters. A mapping written once per template covers most content, and custom folders are handled as exceptions.

  4. Two cloud platforms exist

    iManage runs an earlier cloud platform at imanage.work and a newer one at cloudimanage.com. They differ in details such as maximum file size, email duplicate detection and whether Trash and Journal are always on. Which one the firm is on is established first, because it affects what comes back from the service and how the extraction is tested.

  5. Companion products hold data too

    Firms on the cloud often run other iManage products beside Work: Share folders for clients, Records Manager, Security Policy Manager for walls. Each holds information that is not in the document library itself. The analysis lists which are in use and what is to happen to their content.

More about moving off iManage Cloud

Where it is going

Clio Manage is loaded through its migration templates, one spreadsheet per kind of record, imported in a fixed order with contacts first. Clio’s own migration guide is plain about the limit: balances come across, financial history does not. So a load into Clio is planned as records plus opening positions, with the old system kept for the history behind them.

  1. Matters link by client name

    The matters template ties each matter to its client by an exact match on first name, last name or company name. A client spelt two ways in the old system becomes two contacts, or a matter assigned to an unknown client. This is why contact clean-up is finished before the first trial load, not after it.

  2. Decide the numbering scheme first

    Clio numbers imported matters itself unless the account is set to manual numbering, in which case the old number is supplied in the template. That setting and the firm’s preferred scheme are decided before any matter is loaded. The Client Reference field is available for an old file number the firm still wants to see.

  3. Balances, one line each

    Under Clio’s standard migration, an outstanding balance arrives as one line per matter and a trust balance as one line per matter or contact. Past invoices, billed time, payments and trust transactions are listed as data that cannot be migrated. The trust total is reconciled against the old system’s closing report on the trial load.

  4. Custom fields must exist

    Matter and contact custom fields are created in Clio before their values are imported, each with a field type. Accounts set up for a particular practice area come with preconfigured fields and matter templates, which affects the mapping. We compare those with the old system’s fields and add only what is missing.

  5. Rates and permissions by hand

    Billable rates for users, clients and matters are not part of an import. Neither are user permissions or settings. They are entered in Clio during set-up from a schedule the firm confirms, and a sample of imported unbilled time is checked against that schedule before the trial load is signed off.

More about moving into Clio Manage

How NewLaw runs it

Four steps, in this order.

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

  1. Analysis

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

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 iManage Cloud holds

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

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

Much of a Clio Manage set-up is firm-wide settings. The numbering scheme, practice areas, matter stages, billing preferences and trust accounts apply to everyone, so they are agreed once and early. Trust and accounting features are not the same in every country Clio sells in, so the firm’s own region is checked first. Document templates and custom fields follow. Email and document integrations are then installed for each user and tested on a real matter.

Set-up decisions in Clio Manage

  • Matter numbering scheme, practice areas and matter stages
  • Custom fields for matters and contacts, by practice area
  • Document templates with merge fields, uploaded from Word or PDF
  • Billing settings, user and client rates, and trust accounts
  • Roles and permissions for each user
  • Outlook add-in, Clio Drive and the accounting connection

Questions

iManage Cloud to Clio Manage: what firms ask

Can we get our documents out of iManage Cloud with their profiles?

Yes. Documents, versions, profile fields, folder locations and permissions can all be read through the API. They arrive as files plus a table of metadata. How much of that metadata the next system can hold, and under what field names, is worked out field by field in the analysis.

We are changing practice management systems. Does iManage have to change too?

No. The document system can stay where it is. What changes is the feed of clients and matters into it and the integration that opens a workspace from a matter. If matter numbers change in the new practice management system, the workspaces need renumbering or a cross-reference so the two still line up.

What happens to emails filed in workspaces?

They are stored as documents with sender, recipients and sent date in the profile, so they move like any other document. One email filed by three people can exist three times. The trial load reports how many there are per matter, and the firm chooses whether repeated copies are merged.

Do documents from iManage Cloud keep their folders and dates in Clio Manage?

Clio Manage stores documents. Filed under the matter; Clio scopes document migration separately from data. 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 iManage Cloud have a place in Clio Manage?

On paper, yes: each kind of record iManage Cloud holds has a place in Clio Manage. 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 iManage Cloud data is loaded into Clio Manage?

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

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

Moving from iManage Cloud to Clio Manage?

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

We reply within one business day.