Data migration route
Egnyte to iManage Cloud migration
Egnyte 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.
EgnyteCloud- Documents: Carried across
- Emails: Carried across
- Custom fields: Carried with mapping
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
iManage CloudCloud- 2 carried
- 1 mapped
- 2 to confirm
What moves
What moves from Egnyte to iManage Cloud
Each row is a kind of record Egnyte 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 two kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| DocumentsFiles stored in or linked from the system | HeldFiles in the Shared folder tree and in users’ Private folders, with versions. | 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 staff saved message files into folders. | 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 | To be confirmed | No placeiManage Tracker is a separate product with its own set-up. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | Held in partMetadata sections and properties, where an administrator has defined them. | Has a place in partA fixed number of custom profile fields, each a validated list. | 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 Egnyte.
- 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.
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 Egnyte, 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 Egnyte 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 Egnyte is kept running until the checks on iManage Cloud are finished.
Where the data is now
Leaving Egnyte
An Egnyte domain is a folder tree, and moving it into a legal system is mostly a matter of teaching that tree which folder is which client and which matter. The files download with their paths and dates. What takes thought is everything the tree does not say: permissions on particular folders, private folders, links shared with clients, and any metadata the firm added.
Shared and Private are separate
Firm files live under the Shared folder. Administrators and power users may each also have a Private folder that colleagues do not see, and files created in draft mode are saved there. Client documents can end up in private folders. They are inventoried per user, and the owner decides what is matter material.
Permissions are per folder
Access is granted folder by folder to users and groups, and a subfolder can differ from its parent. A restricted matter is simply a folder most people are not on. The permissions are exported before extraction, so that restricted folders are known and their security can be reproduced in the destination.
Metadata may or may not exist
Egnyte lets administrators define metadata sections and have values inherit down a folder tree, but a domain can run without any. Where a firm did set client or matter properties on folders, those are a more reliable key than folder names. The analysis checks which the firm has and uses the stronger one.
Versions and Trash
Earlier versions of files are kept, and deleted items wait in Trash until they are purged. Both inflate the apparent volume. The firm chooses whether versions come across, and the counts are reported separately for current files, older versions and Trash.
Links shared outside the firm
Folders and files shared with clients by link, and upload links that clients use to send documents in, depend on the domain staying open. A list of active links and who holds them is produced before cutover, so the people who rely on them can be told where to go instead.
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 Egnyte 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 Egnyte: 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 Egnyte, a final pass over a weekend picks up what changed since the trial. Egnyte 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 Egnyte 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 Egnyte 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
Egnyte to iManage Cloud: what firms ask
Our folders are already by client and matter. Is that enough?
It is a good start. The folder names are matched to the matter list from the practice management system, and whatever does not match is reported: misspelt names, closed matters with no number, general folders. Those are fixed in Egnyte before extraction or mapped by hand, and the trial load shows the result.
Do file dates and authors survive?
Modified dates travel with the files. Who uploaded or last edited a file is recorded by Egnyte, and where it can be exported as data it is loaded as author or kept as a property. Created dates are less reliable in any file store, and document dates are checked on the trial load.
Do documents from Egnyte 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.
Does everything in Egnyte have a place in iManage Cloud?
Most of it does on paper. Notes and 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 iManage Cloud is kept as a readable archive, and you see which before the move.
What has to be decided before Egnyte data is loaded into iManage Cloud?
Custom fields are carried with mapping, so each mapping is agreed with you first. Notes and 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 Egnyte 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.
Egnyte and iManage Cloud are the names and marks of their owners, used here only to identify the two systems.
Moving from Egnyte 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.