Data migration route
iManage Cloud to SimpleLaw migration
iManage Cloud is a cloud document management system, and SimpleLaw is a cloud practice management system. Documents and email move out of a store organised by profile and onto the matters they belong to.
iManage CloudCloud- Matters: Carried across
- Documents: Carried across
- Tasks: Carried across
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
SimpleLawCloud- 3 carried
- 2 mapped
- 1 to confirm
What moves
What moves from iManage Cloud to SimpleLaw
Each row is a kind of record iManage Cloud holds, whether SimpleLaw has a place for it, and what is planned. On this route three kinds of record carry across, two kinds need mapping and one kind is confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partOne workspace per matter is the norm. It carries client and matter values, not parties or status. | Has a place | Carried across |
| DocumentsFiles stored in or linked from the system | HeldProfiled, numbered and versioned, and always filed inside a workspace. | Has a placeUploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive. | Carried across |
| EmailsEmails saved to matters or to the store | HeldFiled from Outlook and held as documents with sender, recipients and sent date. | To be confirmed | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | Held in partThrough iManage Tracker, which is sold separately and integrates with Work. | Has a place | Carried across |
| Custom fieldsFields and record types the firm added itself | HeldCustom1 to custom12, custom29 and custom30 hold validated lists the firm captions itself. | Has a place | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held in partPrecedents are stored as ordinary documents, wherever the firm chose to keep them. | Has a place in partTemplates are rebuilt using SimpleLaw’s own automation. | Carried with mapping |
What the plans mean
- Carried across
- SimpleLaw has a place for this kind of record. It is loaded there and checked against iManage Cloud.
- Carried with mapping
- SimpleLaw holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
- Confirmed in the analysis
- We could not confirm this from the two products’ own material, so it is checked against your data before the plan is fixed.
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 SimpleLaw 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 SimpleLaw. 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 SimpleLaw are finished.
Where the data is now
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.
Where it is going
Arriving in SimpleLaw
Loading a firm into SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.
Lead, client or contact
A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.
Billing type on each matter
Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.
Storage chosen before loading
If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.
Custom fields named for templates
Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.
Portal access client by client
The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in SimpleLaw on this route, 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 SimpleLaw. 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 SimpleLaw 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
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
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 SimpleLaw. 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.
Beyond the data
Setting up SimpleLaw
Loaded data is not yet a working system. This is what NewLaw sets up in SimpleLaw, beyond the migration, so that people can work in it from the first day.
The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.
Set-up decisions in SimpleLaw
- Labels for documents, activities, expenses and contact IDs
- Custom fields and intake forms for each practice area
- Document templates and the attorney-client agreement
- Workflows for case types that follow a standard process
- User permission sets and client portal visibility
- QuickBooks connection and the online payment processor
Questions
iManage Cloud to SimpleLaw: 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 SimpleLaw?
SimpleLaw stores documents. Uploaded to SimpleLaw storage or held in a linked Dropbox, Google Drive or OneDrive. 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 SimpleLaw?
Most of it does on paper. Emails could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in SimpleLaw is kept as a readable archive, and you see which before the move.
What has to be decided before iManage Cloud data is loaded into SimpleLaw?
Custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from iManage Cloud and into SimpleLaw
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.
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 SimpleLaw are the names and marks of their owners, used here only to identify the two systems.
Moving from iManage Cloud to SimpleLaw?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.