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

Data migration route

DocuWare to Clio Manage migration

DocuWare is a document management system, and Clio Manage is a cloud practice management system. Documents and email move out of a store organised by profile and onto the matters they belong to.

FromDocuWareDocument management
  1. Documents: Carried across
  2. Emails: Carried across
  3. Notes: Carried across
  4. Custom fields: Carried with mapping
  5. Tasks: Confirmed in the analysis
  6. Templates: Confirmed in the analysis
  7. Intake: Confirmed in the analysis
ToClio ManageCloud
  • 3 carried
  • 1 mapped
  • 3 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from DocuWare to Clio Manage

Each row is a kind of record DocuWare holds, whether Clio Manage has a place for it, and what is planned. On this route three kinds of record carry across, one kind needs mapping and three kinds are confirmed in the analysis.

Records in DocuWare and their place in Clio Manage
RecordIn DocuWareIn Clio ManageWhat is planned
DocumentsFiles stored in or linked from the systemHeldIn file cabinets, found by index fields. One document may contain several files.Has a placeFiled under the matter; Clio scopes document migration separately from data.Carried across
EmailsEmails saved to matters or to the storeHeld in partAn email can be stored with its attachments as one document.Has a placeHeld as communications on the matter, with phone logs.Carried across
NotesFile notes, matter notes and contact notesHeld in partAnnotations and stamps are stored with the document, on layers over the file.Has a placeMatter notes and contact notes each have a template.Carried across
TasksTo-dos and workflow steps assigned to peopleTo be confirmedWorkflow tasks exist where workflow has been configured.Has a placeTasks have a migration template.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldIndex fields are defined separately for each file cabinet.Has a placeCreated first, then filled from the custom field templates.Carried with mapping
TemplatesPrecedents, document templates and automationTo be confirmedHas a placeRebuilt as Clio document templates with its merge fields.Confirmed in the analysis
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedNo placeLeads and intake forms belong in Clio Grow.Confirmed in the analysis

What the plans mean

Carried across
Clio Manage has a place for this kind of record. It is loaded there and checked against DocuWare.
Carried with mapping
Clio Manage 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

Profiled documents become matter documents.

A document management system files by profile: client, matter, author, document type, version. A practice management system files by matter. The move from DocuWare to Clio Manage is a translation from one to the other, and it depends on the client and matter numbers in DocuWare matching matters that exist in Clio Manage. Where they do not match, documents have nowhere to land. So the matter list is settled first and the documents follow it.

Versions and security each need a decision. Some practice systems keep every version of a document, others keep the latest and treat the rest as separate files. A restricted workspace has to become a restricted matter, or the restriction is lost on the way. Filed email comes across as message files against the matter. A document store holds no ledgers, so this route has no financial cutover.

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 Clio Manage 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

Clio Manage is loaded through its migration templates, one spreadsheet per kind of record, imported in a fixed order with contacts first. Clio’s own migration guide is plain about the limit: balances come across, financial history does not. So a load into Clio is planned as records plus opening positions, with the old system kept for the history behind them.

  1. Matters link by client name

    The matters template ties each matter to its client by an exact match on first name, last name or company name. A client spelt two ways in the old system becomes two contacts, or a matter assigned to an unknown client. This is why contact clean-up is finished before the first trial load, not after it.

  2. Decide the numbering scheme first

    Clio numbers imported matters itself unless the account is set to manual numbering, in which case the old number is supplied in the template. That setting and the firm’s preferred scheme are decided before any matter is loaded. The Client Reference field is available for an old file number the firm still wants to see.

  3. Balances, one line each

    Under Clio’s standard migration, an outstanding balance arrives as one line per matter and a trust balance as one line per matter or contact. Past invoices, billed time, payments and trust transactions are listed as data that cannot be migrated. The trust total is reconciled against the old system’s closing report on the trial load.

  4. Custom fields must exist

    Matter and contact custom fields are created in Clio before their values are imported, each with a field type. Accounts set up for a particular practice area come with preconfigured fields and matter templates, which affects the mapping. We compare those with the old system’s fields and add only what is missing.

  5. Rates and permissions by hand

    Billable rates for users, clients and matters are not part of an import. Neither are user permissions or settings. They are entered in Clio during set-up from a schedule the firm confirms, and a sample of imported unbilled time is checked against that schedule before the trial load is signed off.

More about moving into Clio Manage

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Clio Manage 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 Clio Manage. 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 Clio Manage 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 toClio Manage

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 Clio Manage. 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 Clio Manage

Loaded data is not yet a working system. This is what NewLaw sets up in Clio Manage, beyond the migration, so that people can work in it from the first day.

Much of a Clio Manage set-up is firm-wide settings. The numbering scheme, practice areas, matter stages, billing preferences and trust accounts apply to everyone, so they are agreed once and early. Trust and accounting features are not the same in every country Clio sells in, so the firm’s own region is checked first. Document templates and custom fields follow. Email and document integrations are then installed for each user and tested on a real matter.

Set-up decisions in Clio Manage

  • Matter numbering scheme, practice areas and matter stages
  • Custom fields for matters and contacts, by practice area
  • Document templates with merge fields, uploaded from Word or PDF
  • Billing settings, user and client rates, and trust accounts
  • Roles and permissions for each user
  • Outlook add-in, Clio Drive and the accounting connection

Questions

DocuWare to Clio Manage: 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 Clio Manage?

Clio Manage stores documents. Filed under the matter; Clio scopes document migration separately from data. 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 DocuWare have a place in Clio Manage?

Most of it does on paper. Tasks, templates and intake records 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 Clio Manage is kept as a readable archive, and you see which before the move.

What has to be decided before DocuWare data is loaded into Clio Manage?

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 Clio Manage are the names and marks of their owners, used here only to identify the two systems.

Moving from DocuWare to Clio Manage?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.