Data migration route
iManage Cloud to OneDrive migration
iManage Cloud is a cloud document management system, and OneDrive is cloud file storage. Storage only has folders, so the move decides what of each document’s profile is kept in names and what in an index.
iManage CloudCloud- Documents: Carried across
- Emails: Carried with mapping
- Templates: Carried with mapping
OneDriveCloud- Matters: Kept as a readable archive
- Tasks: Kept as a readable archive
- Custom fields: Kept as a readable archive
- 1 carried
- 2 mapped
- 3 archived
What moves
What moves from iManage Cloud to OneDrive
Each row is a kind of record iManage Cloud holds, whether OneDrive has a place for it, and what is planned. On this route one kind of record carries across, two kinds need mapping and three kinds have no place in OneDrive and are archived.
| 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. | No placeA matter is a folder in one user’s drive. | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldProfiled, numbered and versioned, and always filed inside a workspace. | Has a placeFiles and folders up to the service’s size and path limits. | Carried across |
| EmailsEmails saved to matters or to the store | HeldFiled from Outlook and held as documents with sender, recipients and sent date. | Has a place in partSaved message files (.msg or .eml) beside the matter’s documents. | Carried with mapping |
| TasksTo-dos and workflow steps assigned to people | Held in partThrough iManage Tracker, which is sold separately and integrates with Work. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | HeldCustom1 to custom12, custom29 and custom30 hold validated lists the firm captions itself. | No place | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | Held in partPrecedents are stored as ordinary documents, wherever the firm chose to keep them. | Has a place in partPrecedents load as ordinary Word files. | Carried with mapping |
What the plans mean
- Carried across
- OneDrive has a place for this kind of record. It is loaded there and checked against iManage Cloud.
- Carried with mapping
- OneDrive holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
- Kept as a readable archive
- OneDrive has no place for it. It is exported in a format that opens without iManage Cloud and handed to the firm as a read-only archive.
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
Profiles flatten into folders and an index.
A document management system knows things about a file that a folder cannot hold: its profile, its versions, who may open it. Moving from iManage Cloud to OneDrive flattens that. Client and matter become folder levels. Document type may become a subfolder. Versions become separate files with a suffix, or only the latest is kept. Each of these is a choice the firm makes before the export, and the result is tested on a sample of real matters.
What the folders cannot carry goes into an index: a spreadsheet listing every exported file with its document number, author, dates, type and original location. With it, a document cited by number in an old email can still be found. Access restrictions do not transfer by themselves. Restricted workspaces are exported to separate folders, and permissions are set on those in OneDrive before anyone else is given access.
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 OneDrive 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 OneDrive
Before anything is loaded into OneDrive, the firm has to say whose OneDrive it is. Every drive has one owner and disappears with that person’s account unless someone acts. That suits an individual’s working papers. For the firm’s shared matter files the same question usually leads to a SharePoint library with OneDrive as the way people sync it.
Whose drive holds the files
Loading the Clients folder into the principal’s OneDrive ties every matter to that one account. If the firm wants that, the owner’s manager and a secondary owner are set in Microsoft 365 so access is not lost on a departure. Otherwise the files go to a SharePoint library and each person syncs it.
A 400 character path limit
The full path, folders and file name together, cannot exceed 400 characters in OneDrive. Document systems that file by client, matter, category and long descriptive titles produce paths over that. Each one is flagged before loading, and the firm approves how it will be abbreviated.
Characters and names that fail
OneDrive refuses names containing " * : < > ? / \ or |, names with leading or trailing spaces, and files beginning with ~$. Emails saved with their subject as the file name are worth checking first, because subjects often contain colons. Names are cleaned before loading and logged.
Do not sync the whole archive
Microsoft recommends syncing no more than 300,000 items in total and warns that performance suffers beyond it. A firm’s full matter history is often larger. Open matters are set to sync and closed ones are left in the cloud, reachable from the browser when someone needs an old file.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in OneDrive 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 OneDrive. 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 OneDrive 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 OneDrive. 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
Structure, permissions and handover
OneDrive is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.
OneDrive needs little building and a fair amount of policy. The settings that matter to a law firm are in the SharePoint and Microsoft 365 admin centres: who may share outside the firm, how long a leaver’s drive is kept, and what syncs to laptops. Staff are shown the difference between their own drive and the firm’s shared libraries.
What is agreed and set up
- External sharing limits for OneDrive set by an administrator
- Retention period and secondary owner for leavers’ drives
- Known folder redirection decided for Desktop and Documents
- Sync app deployed with Files On-Demand turned on
- Version history limits set for all users’ drives
- Guidance on what belongs in OneDrive and what in SharePoint
Questions
iManage Cloud to OneDrive: 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 OneDrive?
OneDrive stores documents. Files and folders up to the service’s size and path limits. 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.
What happens to records OneDrive has no place for?
On this route that is matters, tasks and custom fields. They are exported from iManage Cloud in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.
What has to be decided before iManage Cloud data is loaded into OneDrive?
Emails 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.
Other routes
Other routes from iManage Cloud and into OneDrive
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 OneDrive are the names and marks of their owners, used here only to identify the two systems.
Moving from iManage Cloud to OneDrive?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.