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

Data migration route

DocuWare to iManage Cloud migration

DocuWare is a document management system, and iManage Cloud is a cloud one. The test of this move is whether profiles, versions and access rules survive it.

FromDocuWareDocument management
  1. Documents: Carried across
  2. Emails: Carried across
  3. Custom fields: Carried with mapping
  4. Tasks: Confirmed in the analysis
  5. Templates: Confirmed in the analysis
  6. Intake: Confirmed in the analysis
ToiManage CloudCloud
  1. Notes: Kept as a readable archive
Readable archiveNo place in iManage Cloud
  • 2 carried
  • 1 mapped
  • 3 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from DocuWare to iManage Cloud

Each row is a kind of record DocuWare 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 three kinds are confirmed in the analysis.

Records in DocuWare and their place in iManage Cloud
RecordIn DocuWareIn iManage CloudWhat is planned
DocumentsFiles stored in or linked from the systemHeldIn file cabinets, found by index fields. One document may contain several files.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 partAn email can be stored with its attachments as one document.Has a placeLoaded as email documents into the workspace’s email folders.Carried across
NotesFile notes, matter notes and contact notesHeld in partAnnotations and stamps are stored with the document, on layers over the file.No placeFile notes can be loaded as documents on the matter.Kept as a readable archive
TasksTo-dos and workflow steps assigned to peopleTo be confirmedWorkflow tasks exist where workflow has been configured.No placeiManage Tracker is a separate product with its own set-up.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldIndex fields are defined separately for each file cabinet.Has a place in partA fixed number of custom profile fields, each a validated list.Carried with mapping
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partPrecedents load as documents. Automation is rebuilt in the firm’s drafting tools.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedNo placeConfirmed 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 DocuWare.
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 DocuWare 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 DocuWare 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.

How DocuWare is run at the firm is settled at the start of the analysis, because its maker’s own material does not settle it. The usual arrangement is assumed here. Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of DocuWare 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 DocuWare is kept running until the checks on iManage Cloud are finished.

Where the data is now

DocuWare is organised for retrieval by index, so an export is a set of documents plus a table of index values, one table per file cabinet. There may be no folder structure at all. The move turns index fields into whatever the destination files by, which for a legal system means deriving a client and matter for every document from fields that were designed for something else.

  1. Each file cabinet stands alone

    Every file cabinet has its own index fields. An invoices cabinet might have supplier, date and amount, while a correspondence cabinet has a matter number and document type. Each is mapped separately, and some, such as supplier invoices, may belong with the accounts system’s records and not in the matter files at all.

  2. One document, several files

    A DocuWare document can hold up to 999 files clipped together: a scanned letter, a Word reply, an email with attachments. Most destinations store one file per document. The plan says whether a clipped set becomes one merged PDF, a group of related documents or a folder.

  3. Scans are PDF/A, the rest native

    Paper scanned through DocuWare is stored as PDF/A, while Office and PDF files are kept in their original format. Scanned items depend on a full-text index to be searchable. If the destination will not run its own text recognition, the text has to travel with the file, which is checked on a sample.

  4. Storage changed at version 7

    On-premises systems that began on version 6 or earlier have documents in two layouts: older ones with an XML header file and numbered file names, newer ones with index data in the database and file names that are GUIDs. The route for extraction is chosen in the analysis with both layouts in mind, so that nothing depends on guessing which one a document uses.

  5. Document trays

    Items that were scanned or imported but never indexed sit in users’ document trays, outside every file cabinet. Users are asked to store or delete them before the freeze. Whatever is left is listed by user, so nothing is lost by oversight.

More about moving off DocuWare

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

  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 DocuWare: 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 DocuWare, a final pass over a weekend picks up what changed since the trial. DocuWare 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 DocuWare 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 fromDocuWare
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 DocuWare 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

DocuWare to iManage Cloud: what firms ask

Our DocuWare has no folders. How will documents be filed in the new system?

From the index. If a file cabinet has a matter or client number field, documents are filed by it. If it has only names or dates, the values are matched to the matter list and the unmatched are reported. Document type fields usually become folders or categories in the destination.

Can stamps and annotations be kept?

DocuWare keeps annotations and stamps as layers over the file, not inside it. To keep an approval stamp visible elsewhere, it has to become part of a PDF copy, and whether DocuWare can produce that copy in bulk is confirmed in the analysis. The firm chooses, for each file cabinet, whether to take the original, the stamped copy, or both.

Do documents from DocuWare 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 DocuWare 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 DocuWare data is loaded into iManage Cloud?

Custom fields are carried with mapping, so each mapping is agreed with you first. Tasks, templates and intake records are confirmed in the analysis. 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

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

Moving from DocuWare 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.