Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

Server drives to iManage Cloud migration

Server drives are plain files on equipment the firm controls, 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.

FromServer drivesFiles
  1. Documents: Carried across
  2. Emails: Carried across
  3. Templates: Carried with mapping
ToiManage CloudCloud
  1. Notes: Kept as a readable archive
  2. Billing: Kept as a readable archive
Readable archiveNo place in iManage Cloud
  • 2 carried
  • 1 mapped
  • 2 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Server drives to iManage Cloud

Each row is a kind of record Server drives hold, 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 have no place in iManage Cloud and are archived.

Records in Server drives and their place in iManage Cloud
RecordIn Server drivesIn iManage CloudWhat is planned
DocumentsFiles stored in or linked from the systemHeldFiles in folders; path, name and dates are the only description.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 storeHeld in partMessages dragged from Outlook into matter folders as .msg files.Has a placeLoaded as email documents into the workspace’s email folders.Carried across
NotesFile notes, matter notes and contact notesHeld in partFile notes kept as Word documents or text files in the matter folder.No placeFile notes can be loaded as documents on the matter.Kept as a readable archive
BillingInvoices, payments and debtor balancesHeld in partCopies of invoices saved as PDFs; no ledger.No placeKept as a readable archive
TemplatesPrecedents, document templates and automationHeld in partA precedents folder of Word templates, with or without macros.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 Server drives.
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 Server drives 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 Server drives, 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.

With Server drives the files are already on equipment the firm controls, so there is no export step: they are read where they are. Upload speed sets the pace for a large store. The originals stay in place, unchanged, until the firm has checked the copy in iManage Cloud.

Where the data is now

Moving off a server drive is a job of interpretation. The files copy easily. Working out which matter each folder belongs to does not, because the tree was built by many hands over many years and the naming changed with every new secretary. The analysis reads the tree, proposes rules for matching folders to matters, and shows the firm what the rules fail to place.

  1. The folder tree is the index

    Each matter folder is matched to a matter in the new system by the client name and matter number in its path. Some match exactly. Others say only Smith or Old files 2011. The unmatched folders are listed with their size and last-modified date, and the firm assigns them, archives them or leaves them.

  2. Paths past 260 characters

    Windows has long limited a full path to 260 characters, and deep matter trees routinely pass it. Such files exist but Explorer and Word may refuse to open or copy them. They are counted in the analysis and shortened to suit the destination’s own limit.

  3. Permissions do not travel with files

    Who may open the Partners folder or a restricted matter is set in Windows permissions on the server. A copy of the files should not be assumed to carry any of that. The permissions on each top-level and matter folder are reported before the move and rebuilt as groups or matter security in the new system.

  4. Folders another system owns

    The same drive often holds the document store of a practice management or accounting system, in folders with coded names. Those files are indexed in that system’s database and mean little without it. They are moved through the system that owns them, and kept out of the loose-file scan.

  5. What accumulates over twenty years

    Server drives collect shortcuts, temporary Word files, copies named Final v3 and whole duplicated matter folders. Exact duplicates are identified and reported. The firm sets the rule for near-duplicates, since only a person can say whether Final or Final v3 is the one that went to court.

More about moving off Server drives

Where it is going

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving into iManage Cloud

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.

  1. Analysis

    We read what Server drives hold 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.

  2. 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.

  3. Trial load

    A trial is loaded into iManage Cloud and checked against Server drives: 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.

  4. Cutover

    There is no financial cutover on this route. After a short freeze on changes in Server drives, a final pass over a weekend picks up what changed since the trial. Server drives are 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 Server drives 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

Step 1 of 5: Start with the route

Moving fromServer drives
Moving toiManage Cloud

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what Server drives 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.

  3. 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

Server drives to iManage Cloud: what firms ask

Our folders are a mess. Do we have to tidy them before the move?

No, and it is better not to rename things by hand beforehand. The analysis works from the tree as it stands and proposes matching rules. Staff time is better spent on the short list of folders the rules cannot place, and on deciding what is old enough to archive without filing it to a matter.

Will the dates on our documents be kept?

The modified date on each file is read from the server and passed to the new system where it accepts a document date. Created dates on a server are less reliable, because copying files between drives in the past can have changed them. The trial load compares document dates on sample matters against the old folders.

Can staff keep using the S: drive after go-live?

For reading, yes: the drive is kept read only as the fall-back record. Not for filing. If people can still save to the old drive, some will, and within a month the firm has two places to look for every document. The drive is switched to read only at cutover.

Do documents from Server drives 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 and billing records. They are exported from Server drives 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 Server drives 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.

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.

How we do itDiscovery to rollout, step by step

Server drives and iManage Cloud are the names and marks of their owners, used here only to identify the two systems.

Moving from Server drives 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.