Moving off a system
Migrating from iManage Cloud
The service in which iManage hosts iManage Work: document and email management with matter workspaces, profiles, versions and need-to-know security. This page sets out what iManage Cloud holds, what moving off it involves and where its records can go.
Where it can go
Routes from iManage Cloud
Each route has a page of its own: what moves, what has no place in the destination and how the move is run.
Practice management systems
Actionstep6 of 6 kinds of record have a place
Centerbase6 of 6 kinds of record have a place
Clio Manage6 of 6 kinds of record have a place
MyCase6 of 6 kinds of record have a place
Rocket Matter6 of 6 kinds of record have a place
SimpleLaw5 of 6 kinds of record have a place
Smokeball6 of 6 kinds of record have a place
SurePoint Finance Enterprise1 of 6 kinds of record has a place
Case management systems
Document management systems
Accounting and billing systems
CRM and intake systems
File storage
Box4 of 6 kinds of record have a place
Dropbox3 of 6 kinds of record have a place
Google Drive3 of 6 kinds of record have a place
OneDrive3 of 6 kinds of record have a place
Server drives3 of 6 kinds of record have a place
SharePoint6 of 6 kinds of record have a place
Sync.com3 of 6 kinds of record have a place
What it holds
The records iManage Cloud keeps
Fourteen kinds of record matter to a move. iManage Cloud keeps six of them, three in part.
- MattersIn partOne workspace per matter is the norm. It carries client and matter values, not parties or status.
- ContactsNoA client is an entry in a validated list, with a code and a description.
- DocumentsYesProfiled, numbered and versioned, and always filed inside a workspace.
- EmailsYesFiled from Outlook and held as documents with sender, recipients and sent date.
- NotesNoFile notes, matter notes and contact notes
- CalendarNoAppointments, court dates and deadlines
- TasksIn partThrough iManage Tracker, which is sold separately and integrates with Work.
- Time and expensesNoTime and expense entries, billed and unbilled
- BillingNoInvoices, payments and debtor balances
- Trust moneyNoTrust or client account ledgers and balances
- Firm accountsNoGeneral ledger, office account and payables
- Custom fieldsYesCustom1 to custom12, custom29 and custom30 hold validated lists the firm captions itself.
- TemplatesIn partPrecedents are stored as ordinary documents, wherever the firm chose to keep them.
- IntakeNoLeads, enquiries, intake forms and pipelines
Moving off it
Leaving iManage Cloud
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.
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.
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.
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.
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.
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.
The system
What iManage Cloud is
iManage Cloud is the service in which iManage hosts and runs iManage Work for the firm. The platform is built on Microsoft Azure and is used through Work 10 in a browser, desktop and Outlook add-ins on Windows and Mac, and the Mobility app on a phone. It is sold to law firms of every size, and to accounting firms and corporate legal teams.
Content sits in libraries. Within a library each matter normally has a workspace, created from a template, that holds tabs, folders and search folders. Documents and filed emails carry a profile of client, matter, class, author and other fields, plus a document number and version. Administration is done in the web-based Control Center. Administrators have API access to a cloud library, not SQL access.
- Kind
- Document management
- Runs as
- Cloud, hosted by its maker
- Made by
- iManage
- Mainly used in
- Worldwide
- Also known as
- iManage Work in the Cloud, iManage Work 10, cloudimanage.com, imanage.work
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in the new system on most routes, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what iManage Cloud holds and how it is organised, then agree with you where each kind of record will sit in the new system. Anything with no place there stays behind or is archived, and you see which before the move.
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.
Trial load
A trial is loaded into the new system 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.
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
Choose where the iManage Cloud data is going, or tell us you have not decided. The first step is the analysis, and the price is fixed once it is done.
Step 1 of 5
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what iManage Cloud holds
What is in it, how its records link, and where each piece would sit in the new system. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- A fixed price in writing
Set after the analysis, so it reflects what is in your data. You have it before any work starts.
After the move
Setting up the system you move to
A migration ends with data in a new system. Whether people can work in it on the first day depends on how that system was set up: matter types, templates, billing, permissions. NewLaw does that work as well, and each destination’s page says what its set-up involves.
Set-up, by destination
Questions
Moving off iManage Cloud: 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.
Where to start
Still deciding where to move?
Choose the system before you plan the move, and see where AI fits once your data is in it.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
iManage Cloud and the other product names and logos on this page belong to their owners and are used only to identify the systems.
Moving off 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.