Data migration route
Document Locator to iManage Cloud migration
Document Locator is a server-based document management system, and iManage Cloud is a cloud one. The test of this move is whether profiles, versions and access rules survive it.
Document LocatorServer- Documents: Carried across
- Emails: Carried across
- Custom fields: Carried with mapping
- Notes: Confirmed in the analysis
- Templates: Confirmed in the analysis
iManage CloudCloud- Tasks: Kept as a readable archive
- 2 carried
- 1 mapped
- 2 to confirm
- 1 archived
What moves
What moves from Document Locator to iManage Cloud
Each row is a kind of record Document Locator 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, one kind has no place in iManage Cloud and is archived and two kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldIn repository folders, with automatic versions, profiles and an audit log. | 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 partEmails and attachments can be captured and managed with the documents. | Has a placeLoaded as email documents into the workspace’s email folders. | Carried across |
| NotesFile notes, matter notes and contact notes | To be confirmed | No placeFile notes can be loaded as documents on the matter. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | Held in partWorkflow and approval steps routed to people. | No placeiManage Tracker is a separate product with its own set-up. | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | HeldMetadata is applied through profiles the administrator defines. | Has a place in partA fixed number of custom profile fields, each a validated list. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a place in partPrecedents load as documents. Automation is rebuilt in the firm’s drafting tools. | Confirmed in the analysis |
What the plans mean
- Carried across
- iManage Cloud has a place for this kind of record. It is loaded there and checked against Document Locator.
- 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.
- 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.
- Kept as a readable archive
- iManage Cloud has no place for it. It is exported in a format that opens without Document Locator 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, versions and security, kept intact.
Between two document management systems the files are the easy part. What a firm has built in Document Locator is everything around them: the profile on each document, its version history, who can open it, which workspace it sits in. iManage Cloud has its own model for each. Document types and custom profile fields are mapped one to one where they can be. Versions are loaded in order, so the latest in the old system is the latest in the new one.
Security is checked on its own. A restricted client or an information barrier must arrive restricted, so access groups are created in iManage Cloud before any document is loaded, and a sample of restricted workspaces is tested with a user who should not see them. Document numbers are worth keeping, since they appear in footers and old emails. Where the new system assigns its own, the old number is stored as a searchable field.
Document Locator runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. iManage Cloud is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.
Where the data is now
Leaving Document Locator
Because Document Locator presents itself as folders in Windows, people assume the documents can be dragged out like files on a drive. They are in a SQL Server repository. A copy made that way should not be expected to bring versions, profile values or permissions with it. A planned extraction reads the repository for those, and for check-out state as well.
A repository, not a share
The folder tree users see is drawn from a Microsoft SQL Server repository. On-premises, that database is on the firm’s server and can be backed up and read. In the hosted service it is on Azure and access is arranged with ColumbiaSoft. Which of the two applies shapes how the work begins.
Folders stand in for matters
There is no client or matter record, so firms build the equivalent with a folder convention, sometimes created automatically by a project-folder rule. The convention is read off the tree and tested: how many top-level folders match a client in the practice management system, and how many are something else.
Version numbers and notes
Every check-in adds a version with an incrementing number, users can add a version note, and prior versions can be promoted. For controlled documents such as policies and precedents, that history is the point of the system. The firm decides folder by folder whether history comes across or only the current version.
Workflow and required reading
Approvals in progress, review reminders and acknowledgements that staff have read a policy are records of process. A legal document system will usually have nowhere to put them. Reports are run from Document Locator before cutover and saved as documents, so the evidence is kept even though the workflow is not.
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 Document Locator 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 Document Locator: 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 Document Locator, a final pass over a weekend picks up what changed since the trial. Document Locator 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 Document Locator 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 Document Locator 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
Document Locator to iManage Cloud: what firms ask
Can we simply copy the folders out through Windows?
It will produce files, and for a small set that may be all that is needed. It should not be relied on for a whole repository, because versions, profile metadata, permissions and audit history are in the database. The analysis establishes what the repository records about a document beyond the file itself.
How do documents get matched to matters when there is no matter record?
By the folder path or a profile field, whichever the firm used consistently. A matter list from the practice management system is matched against folder names, and the matches, near-matches and orphans are reported. Near-matches are confirmed by someone at the firm who knows the files.
Do documents from Document Locator 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 tasks. They are exported from Document Locator 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 Document Locator data is loaded into iManage Cloud?
Custom fields are carried with mapping, so each mapping is agreed with you first. Notes and templates 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 Document Locator 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.
Document Locator and iManage Cloud are the names and marks of their owners, used here only to identify the two systems.
Moving from Document Locator 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.