Data migration route
Dropbox to iManage Cloud migration
Dropbox is cloud file storage, and iManage Cloud is a cloud document management system. The move adds structure the folders never had: a client, a matter and a document type for every file.
DropboxCloud- Documents: Carried across
- Emails: Carried across
- Templates: Carried with mapping
iManage CloudCloud- Notes: Kept as a readable archive
- 2 carried
- 1 mapped
- 1 archived
What moves
What moves from Dropbox to iManage Cloud
Each row is a kind of record Dropbox holds, whether iManage Cloud has a place for it, and what is planned. On this route two kinds of record carry across, one kind needs mapping and one kind has no place in iManage Cloud and is archived.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldFiles in folders, synced to desktops, with version history for a set number of days. | Has a placeEach needs a workspace and valid client and matter values; its class sets default security. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partOnly where messages were saved into a folder as .msg or .eml files. | Has a placeLoaded as email documents into the workspace’s email folders. | Carried across |
| NotesFile notes, matter notes and contact notes | Held in partDropbox Paper documents, where staff used them for notes. | No placeFile notes can be loaded as documents on the matter. | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | Held in partPrecedents are kept as ordinary files in a folder. | Has a place in partPrecedents load as documents. Automation is rebuilt in the firm’s drafting tools. | Carried with mapping |
What the plans mean
- Carried across
- iManage Cloud has a place for this kind of record. It is loaded there and checked against Dropbox.
- Carried with mapping
- iManage Cloud 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
- iManage Cloud has no place for it. It is exported in a format that opens without Dropbox 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
Folders go in. Profiled workspaces come out.
A document management system asks questions of every file that a folder never did: which client, which matter, what type of document, who wrote it. Coming from Dropbox, the answers have to be worked out from where a file sits and what it is called. The analysis reads the folder tree, proposes how its levels map to client, matter and folder in iManage Cloud, and lists what does not fit. Those exceptions go to the firm as a spreadsheet to correct.
Not everything should move. Shared drives collect installers, duplicates, personal files and working copies ten versions deep. The firm decides what is in scope by folder, by age or by file type, and the rest is left where it is or archived. File dates are preserved. Paths too long for iManage Cloud, characters it does not allow and files that will not open are reported before the load. The copy can be repeated, so the final pass picks up only what changed.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Dropbox 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 Dropbox is kept running until the checks on iManage Cloud are finished.
Where the data is now
Leaving Dropbox
Moving off Dropbox begins with a simple question that often has an awkward answer: whose account are the files in. A team space is one thing. Personal accounts sharing folders with each other are another, and the firm’s matter files may sit partly in an account that belongs to someone who has left.
Team space or personal accounts
On a team plan, team folders belong to the firm and an administrator can see them all. Outside one, each folder belongs to the person who created it and the others only have it shared to them. The analysis lists every account that owns matter folders, so that none is left behind when subscriptions are cancelled.
Collect from the account itself
Files marked online-only show in Explorer but are not on the disk. Copying the Dropbox folder from one computer can produce a tree that looks whole and is missing its contents. The files are taken from the Dropbox account itself, and one PC’s folder is used only to check the result.
Conflicted copies
When two people save the same file at once, Dropbox keeps both and adds the editor’s name and the words conflicted copy to one of them. Years of this leaves matter folders with near-duplicates. They are reported in the clean-up, and the firm decides whether to keep the later file, both, or review them by hand.
Paper docs need exporting
Dropbox Paper documents are not Word files. Each can be exported to .docx, Markdown or PDF, and on the current release of Paper that is done one document at a time. Where a firm kept file notes or checklists in Paper, they are counted early because the export is manual work.
Version history is a time window
Dropbox keeps earlier versions for a number of days set by the plan, not for a number of versions. Anything older has already gone. If earlier drafts matter for particular matters, they are pulled out while the window still covers them and before the plan is downgraded or cancelled.
Where it is going
Arriving in iManage Cloud
Administrators of an iManage Cloud library have API access only, so nothing is loaded by writing to a database. For cloudimanage.com, the newer of its two cloud platforms, iManage lists a supervised import API, sync APIs and a metadata loader. Nothing can be filed loose: every document goes into a workspace, with valid client and matter values. So the client and matter lists, the workspace template and the security groups are built first.
Client and matter lists first
Custom1 and custom2 are validated lists, with each matter a child of its client. A value that is not already in the list cannot be assigned to a document. The lists are loaded from the practice management system or the old document store before any content, closed matters with documents included.
One workspace per matter
Each matter gets a workspace generated from a template, so the template is designed before migration: its tabs, its folders, which are created up front and which on demand. Old folder trees rarely match it. The mapping says where each old folder lands and what happens to folders with no equivalent.
Authors must be known users
Author and operator are profile fields tied to users of the library. Documents written by people who left years ago need a decision: recreate those people as inactive users, or assign a placeholder author. That choice affects searching by author for as long as the firm uses the system.
Hybrid security
iManage calls its security model hybrid: where a user’s groups disagree, the most permissive access applies unless one of them is denied. On cloudimanage.com that model cannot be changed. Default security is normally set on the workspace and inherited below it. Restricted matters from the old system are loaded with their access list already in place.
New numbers, original dates
Documents are numbered by iManage as they are loaded, so old numbers do not carry over as numbers. On cloudimanage.com the file date setting is fixed to the file’s own date, and on imanage.work it can be set either way. Which dates display is checked on the trial load. The old reference can be carried in a custom field or the description where the firm wants to search by it.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in iManage Cloud on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what Dropbox holds and how it is organised, then agree with you where each kind of record will sit in iManage Cloud. 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 iManage Cloud and checked against Dropbox: 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 Dropbox, a final pass over a weekend picks up what changed since the trial. Dropbox 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 Dropbox 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 Dropbox holds
What is in it, how its records link, and where each piece would sit in iManage Cloud. 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 iManage Cloud
Loaded data is not yet a working system. This is what NewLaw sets up in iManage Cloud, beyond the migration, so that people can work in it from the first day.
Setting up iManage Cloud is mostly design work done before any user logs in: how many libraries, what a workspace looks like, which profile fields are captioned for what, and who can see which matters. Then come the links that keep it running day to day, such as creating a workspace when a matter is opened in the practice management system, and the add-ins on each desk.
Set-up decisions in iManage Cloud
- Library structure and captions for client, matter and other fields
- Workspace templates, folder names and Flexible Folders rules by practice area
- Document classes, subclasses and the profile fields each one requires
- Roles, groups, default security and walls for restricted matters
- Workspace creation fed from the practice management system’s matter list
- Work Desktop, Outlook email filing and Mobility on each device, with training
Questions
Dropbox to iManage Cloud: what firms ask
Our files are in a partner’s personal Dropbox. Can they still be moved?
Yes, with the partner’s consent and access to that account. The shared folders are collected from the account that owns them, so nothing depends on what happens to be synced to one laptop. Personal folders mixed in with client folders are marked by the partner beforehand and left out.
Will the dates on our documents change?
The modified date of each file is recorded when it is collected and written to the destination where the destination allows it to be set. Some systems stamp every loaded document with the load date as its created date. The trial load shows which dates the new system displays, checked against a sample of old matters.
What about links we have sent to clients?
Shared links point at files in Dropbox, so they cannot be relied on once those files are removed or the account is closed. A list of active links and shared folders is produced before cutover. The firm then tells the clients concerned where their documents will be available afterwards.
Do documents from Dropbox keep their folders and dates in iManage Cloud?
iManage Cloud stores documents. Each needs a workspace and valid client and matter values; its class sets default security. 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 iManage Cloud has no place for?
On this route that is notes. They are exported from Dropbox 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 Dropbox data is loaded into iManage Cloud?
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 Dropbox and into iManage Cloud
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.
Dropbox and iManage Cloud are the names and marks of their owners, used here only to identify the two systems.
Moving from Dropbox to 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.