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

Data migration route

iManage Cloud data to Full data export

iManage Cloud is a cloud document management system, and Full data export is a store of data kept as files the firm holds. What lands in Full data export is the register: every file’s name, place, dates and details, with the files themselves stored beside it.

FromiManage CloudCloud
  1. Matters: Exported in full
  2. Documents: Exported in full
  3. Tasks: Exported in full
  4. Emails: Exported with mapping
  5. Custom fields: Exported with mapping
  6. Templates: Exported with mapping
ToFull data exportFiles
  • 3 carried
  • 3 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from iManage Cloud to Full data export

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

Records in iManage Cloud and their place in Full data export
RecordIn iManage CloudIn Full data exportWhat 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 placeA matters table keyed by the original matter number.Exported in full
DocumentsFiles stored in or linked from the systemHeldProfiled, numbered and versioned, and always filed inside a workspace.Has a placeFiles under their original names, in client and matter folders.Exported in full
EmailsEmails saved to matters or to the storeHeldFiled from Outlook and held as documents with sender, recipients and sent date.Has a place in partFiled emails as message files in the matter’s folder, if the source exposes them.Exported with mapping
TasksTo-dos and workflow steps assigned to peopleHeld in partThrough iManage Tracker, which is sold separately and integrates with Work.Has a placeA table of tasks with assignee, due date and status.Exported in full
Custom fieldsFields and record types the firm added itselfHeldCustom1 to custom12, custom29 and custom30 hold validated lists the firm captions itself.Has a placeExtra columns under their original field names.Exported with mapping
TemplatesPrecedents, document templates and automationHeld in partPrecedents are stored as ordinary documents, wherever the firm chose to keep them.Has a place in partTemplate files only; the merge fields in them will not run.Exported with mapping

What the plans mean

Exported in full
Full data export has a place for this kind of record. It is loaded there and checked against iManage Cloud.
Exported with mapping
Full data export 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

The files, and a register of what each one is.

A database is a poor place to keep documents and a good place to keep facts about them. On this route the files from iManage Cloud are exported to storage the firm controls, and Full data export receives the register: one row per file, with its path, size, dates, author and whatever profile or folder details existed. That register is what makes a large export searchable. It also proves completeness, since the row count and total size can be agreed to the source.

How useful the register is depends on how much iManage Cloud knows about each file. A document management system has a profile to carry. A plain folder has only a path and dates, and the client or matter has to be read out of folder names. Where versions or an audit history exist, each becomes a table of its own. The export is checked by picking documents at random in the source, finding them through Full data export, and opening the file to confirm it is the same one.

iManage Cloud is hosted by its maker and Full data export sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What iManage Cloud will release depends on its export tools, and that is confirmed in the analysis.

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

A full export is judged by whether a stranger can use it. In five years the question will be something like: what was the trust balance on this matter the day it closed, and where is the signed agreement. The export is planned backwards from questions of that kind, and it is checked against the live system while the live system can still be opened.

  1. Tables that still join up

    Each kind of record becomes its own table: matters, contacts, time entries, invoices, trust transactions. The identifiers that link them are kept in every table, so a time entry can still be traced to its matter and its fee earner. An export that keeps the rows and drops the keys cannot be rejoined later.

  2. Documents with an index

    Documents are written to folders by client and matter under their original names. On their own they can be found only by name. An index listing each file with its matter number, title, author, dates and path is what lets someone find the right version of a lease among forty thousand files without the old system’s search. What the index records is settled in the analysis.

  3. Reports a person can read

    Raw tables do not satisfy an auditor or a former client. The firm decides which reports are also printed to PDF from the old system as at the final date: trust ledgers, matter ledgers, debtor lists and issued invoices are the usual candidates. They cannot be regenerated once the licence ends.

  4. What an export does not keep

    Screens, workflows, document automation, saved searches and user permissions belong to the software and stay with it. Figures the system calculated on the fly, such as a matter’s unbilled total, exist in an export only if they were captured as a report. The firm is told which of these are being let go.

  5. Checked while the source is open

    Record counts and financial totals in the export are reconciled to the live system: number of matters, sum of trust balances, total debtors, document count per matter on a sample. This is done before the subscription lapses or the server is turned off, because afterwards there is nothing left to compare against.

More about moving into Full data export

How NewLaw runs it

Four steps, in this order.

This route produces an archive, not a working system, so the steps are about completeness and proof.

  1. Analysis

    We read what iManage Cloud holds, table by table, and agree with you what the copy in Full data export must be able to answer later. Everything iManage Cloud holds is in scope unless you take it out.

  2. Clean-up, if you want it

    An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.

  3. Trial export

    The data is written to Full data export as a trial and checked against iManage Cloud: record counts, totals where iManage Cloud holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in iManage Cloud, the export is run a final time and checked again. There is nothing to go live. iManage Cloud is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.

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 toFull data export

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 Full data export. 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

Structure, permissions and handover

Full data export is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.

With no product to configure, the set-up is custody, and the decisions are the firm’s. Someone there owns the export, knows where it is kept and can open it. Access needs restricting, because it contains every client’s affairs in one place with none of the old system’s security. The firm sets a destruction date from its retention obligations and decides how the next custodian will learn to use it.

What is agreed and set up

  • Folder layout for tables, documents and reports
  • What the key to tables, columns and identifiers records
  • Where the copies are stored and who is custodian
  • Who may open it, as approved by a partner
  • Which look-ups staff must be able to do unaided
  • Retention period and the date it is next reviewed

Questions

iManage Cloud to Full data export: 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.

Does the copy in Full data export hold documents from iManage Cloud?

Yes. Files under their original names, in client and matter folders. Documents are written out with the rest, and counts and totals are agreed to the reports in iManage Cloud as at the export date.

Does everything in iManage Cloud have a place in Full data export?

On paper, yes: each kind of record iManage Cloud holds has a place in Full data export. 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 is written out to Full data export?

Emails, custom fields and templates are exported with mapping, so each mapping is agreed with you first. The firm also decides who may open the archive and how long it is kept.

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 Full data export are the names and marks of their owners, used here only to identify the two systems.

Moving from iManage Cloud to Full data export?

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

We reply within one business day.