Data migration route
iManage Work to NetDocuments migration
iManage Work is a server-based document management system, and NetDocuments is a cloud one. The test of this move is whether profiles, versions and access rules survive it.
iManage WorkServer- Documents: Carried across
- Emails: Carried across
- Matters: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Tasks: Confirmed in the analysis
NetDocumentsCloud- 2 carried
- 3 mapped
- 1 to confirm
What moves
What moves from iManage Work to NetDocuments
Each row is a kind of record iManage Work holds, whether NetDocuments has a place for it, and what is planned. On this route two kinds of record carry across, three 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 partA workspace usually stands for a matter, with client and matter held as custom1 and custom2. | Has a place in partAs a client and matter value with its workspace. Other matter details stay in practice management. | Carried with mapping |
| DocumentsFiles stored in or linked from the system | HeldEach is identified by its library name, a document number and a version number. | Has a placeImported with profile values, folder, dates and access set per document. | Carried across |
| EmailsEmails saved to matters or to the store | HeldFiled emails are stored as documents, usually in email folders inside the workspace. | Has a placeLoaded as email items profiled to the matter. | Carried across |
| TasksTo-dos and workflow steps assigned to people | Held in partTask lists are kept in iManage Tracker, a separate product. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldCustom profile fields with validated lists, captioned by the firm, such as practice area. | Has a placeAs custom profile attributes, created in the repository before the load. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held in partPrecedents are held as documents. Workspace templates only set folder structure. | Has a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh. | Carried with mapping |
What the plans mean
- Carried across
- NetDocuments has a place for this kind of record. It is loaded there and checked against iManage Work.
- Carried with mapping
- NetDocuments 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
Profiles, versions and security, kept intact.
Between two document management systems the files are the easy part. What a firm has built in iManage Work is everything around them: the profile on each document, its version history, who can open it, which workspace it sits in. NetDocuments 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 NetDocuments 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.
iManage Work 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. NetDocuments 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 iManage Work
Moving off an on-premises library starts with access to its database and its file store, because the profiles, security and version history are read from the database. The stored files on their own are not usable: each one has to be matched to its profile. Most of the planning goes into client and matter numbers, security, and which versions come across.
The database carries the meaning
The title, author, client, matter, class and folder location of every document are rows in the library database, not properties of the stored file. An extraction that copies only the file store brings none of that with it. The database and the files therefore have to be collected together, at the same point in time.
Client and matter are custom fields
Custom1 and custom2 are a parent and child pair, normally captioned Client and Matter, and every value has to exist in a validated list. That list is usually fed from the practice management system. The analysis compares it with the destination’s matter list, since closed or renumbered matters often exist in one and not the other.
Document numbers get quoted
A document is identified by library, number and version, and lawyers quote those numbers in emails, footers and other documents. The firm decides whether every version moves or only the latest, and whether the old number is kept as a searchable field or in the document name so an old reference can still be traced.
Security is layered
Each workspace, folder and document has a default security of private, view, public or inherited, and users or groups can be granted or denied access on top of that. Private documents and walled-off matters are either reproduced in the destination or deliberately opened up. That is decided group by group before the trial load.
Emails are documents here
A filed email is stored as a document in its own right, often in an email folder inside the workspace, and the same message may have been filed by several people. Volumes are large. The trial load reports how many emails each matter holds and how repeated copies were treated.
Where it is going
Arriving in NetDocuments
Loading into NetDocuments means every document arrives with a profile. The cabinet, its profile attributes and the client and matter lookup tables are built first. Documents are then imported with an instruction file that says, line by line, which file gets which client, matter, author, document type, folder and access. Preparing that file from the old system’s data is most of the work.
Lookup tables before documents
Client and matter are validated attributes, with matter the child of client. A value missing from the lookup table cannot be used to profile a document. The tables are loaded from the practice management system first, closed matters included, and each matter is flagged open or closed so old ones stay out of pick lists.
Workspaces come from the profile
A workspace shows whatever is profiled to its matter. So the question is not where to put a folder tree but how to profile each file. Old folder names are often turned into a document type attribute, or kept as a workspace folder, and the mapping decides which for each one.
Import files are unforgiving
The import file is comma-separated text, and NetDocuments itself warns that opening one in Excel can strip leading zeros from numbers and alter dates. A matter number of 00123 that becomes 123 will not match its lookup value. The files are kept as plain text from start to finish and are not opened in a spreadsheet.
Folder limits and depth
A folder can hold any number of documents but no more than 500 subfolders. Deep trees copied from a file server also work against the way the system is searched. Where a matter arrives with hundreds of nested folders, the plan flattens them and keeps the lost path in the document name or an attribute.
Security at the right level
Access can be set on the cabinet, by profile value, on a workspace or on a single document. Restricted matters are best carried as workspace or profile-based security, so that new documents pick it up. Document-by-document access lists copied from an old system are loaded only where the restriction was real.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in NetDocuments on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what iManage Work holds and how it is organised, then agree with you where each kind of record will sit in NetDocuments. 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 NetDocuments and checked against iManage Work: 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 Work, a final pass over a weekend picks up what changed since the trial. iManage Work 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 Work 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 Work holds
What is in it, how its records link, and where each piece would sit in NetDocuments. 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 NetDocuments
Loaded data is not yet a working system. This is what NewLaw sets up in NetDocuments, beyond the migration, so that people can work in it from the first day.
Beyond the load, NetDocuments has to be designed: how many cabinets the firm needs, which profile attributes every document must carry, and what a new matter’s workspace looks like on its first day. After that it is connected to the practice management system so client and matter lists stay current, and ndOffice and the email filing tools are set up for each person, with training on profiling.
Set-up decisions in NetDocuments
- Cabinet design: one for the firm, or several by purpose
- Profile attributes, lookup tables and the client and matter hierarchy
- Workspace layout with default folders, filters and saved searches
- User groups, cabinet membership and security for restricted matters
- A feed of new clients and matters from practice management
- ndOffice, ndMail and Outlook filing on every desk, with training
Questions
iManage Work to NetDocuments: what firms ask
Can we keep our iManage document numbers?
The number is assigned by the library, so the new system will issue its own. What can be kept is the old number as a reference: in a custom field, in the document name, or in a lookup list. Which is possible depends on the destination, and it is settled in the analysis because footers and old emails quote the numbers.
Do all versions of a document come across?
They can be extracted, since each version has its own profile. Whether the destination keeps them as versions of one document or as separate documents depends on that system. A common choice is every version for open matters and the latest version only for matters that closed some years ago.
Is moving to iManage Cloud the same job as moving to another product?
No. Going to iManage’s own cloud keeps the same structure of libraries, workspaces, profiles and security, and iManage publishes its own resources for that move. Moving to a different product means mapping each of those concepts onto something else, which is where the analysis time goes.
Do documents from iManage Work keep their folders and dates in NetDocuments?
NetDocuments stores documents. Imported with profile values, folder, dates and access set per document. 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 Work have a place in NetDocuments?
Most of it does on paper. Tasks 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 NetDocuments is kept as a readable archive, and you see which before the move.
What has to be decided before iManage Work data is loaded into NetDocuments?
Matters, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Tasks 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 Work and into NetDocuments
Other destinations from iManage Work
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 Work and NetDocuments are the names and marks of their owners, used here only to identify the two systems.
Moving from iManage Work to NetDocuments?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.