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

Data migration route

Doc.It Suite to Clio Manage migration

Doc.It Suite is a document management system for accounting firms, 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.

FromDoc.It SuiteDocument management
  1. Matters: Carried across
  2. Documents: Carried across
  3. Tasks: Carried across
  4. Contacts: Confirmed in the analysis
  5. Emails: Confirmed in the analysis
  6. Notes: Confirmed in the analysis
  7. Calendar: Confirmed in the analysis
  8. Custom fields: Confirmed in the analysis
  9. Templates: Confirmed in the analysis
ToClio ManageCloud
  • 3 carried
  • 6 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Doc.It Suite to Clio Manage

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

Records in Doc.It Suite and their place in Clio Manage
RecordIn Doc.It SuiteIn Clio ManageWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partEngagements are organised as client Work Binders, not as legal matters.Has a placeImported from a matters template, after contacts.Carried across
ContactsClients, other parties and referrersTo be confirmedHas a placePeople and companies, with related contacts linked to matters by a separate template.Confirmed in the analysis
DocumentsFiles stored in or linked from the systemHeldHeld in the Inbox, in Work Binders and in the Archive, named by the firm’s policy.Has a placeFiled under the matter; Clio scopes document migration separately from data.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a placeHeld as communications on the matter, with phone logs.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeMatter notes and contact notes each have a template.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeCalendar events have a migration template.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeld in partWork Binders carry status, due dates and routing between staff.Has a placeTasks have a migration template.Carried across
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeCreated first, then filled from the custom field templates.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a placeRebuilt as Clio document templates with its merge fields.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 Doc.It Suite.
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 Doc.It Suite to Clio Manage is a translation from one to the other, and it depends on the client and matter numbers in Doc.It Suite 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 Doc.It Suite 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. Doc.It Suite 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. Clio Manage 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

Doc.It was designed around the way an accounting engagement runs, so its content is in one of three states: waiting in the Inbox, live in a Work Binder, or filed in the Archive. A move has to collect all three. For binders it also has to settle whether work in progress is finished first or carried across part-way through, with its status.

  1. Inbox, binders and archive

    Documents in the Inbox have not been filed yet and may belong to nobody. Work Binders hold current engagements with status and routing. The Archive holds the settled record. Each is exported and counted on its own. The Inbox is best emptied by the firm before the freeze, because unrouted scans have no client attached.

  2. Policy Manager names the files

    File names and storage locations follow a firm-wide policy applied as documents are gathered. That helps: the client, year and document type can often be read back out of the name and path. The policy is obtained first and tested against real files, since it may have been revised more than once.

  3. Engagements are not matters

    Accounting work recurs by client and year: a tax return for one year, an audit for the next. A legal system expects matters. The mapping decides whether each client becomes one continuing matter with year folders, or one matter per engagement. That choice changes the matter count considerably and is agreed before the trial load.

  4. Files from other programs

    The Inbox can pass documents on to other binder systems such as CaseWare, and Doc.It works beside tax and practice software. Files produced by those programs open only in them. They are carried across as they are, and the firm confirms it will keep the software needed to read them.

  5. Where it is installed

    The suite has been offered on-premise, hosted and as a hybrid of the two, so the documents may be on the firm’s own server or with a provider. Finding out which, and who can give read access, is the first practical step, ahead of any discussion about mapping.

More about moving off Doc.It Suite

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 Doc.It Suite 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 Doc.It Suite: 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 Doc.It Suite, a final pass over a weekend picks up what changed since the trial. Doc.It Suite 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 Doc.It Suite 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 fromDoc.It Suite
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 Doc.It Suite 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

Doc.It Suite to Clio Manage: what firms ask

Is Doc.It Suite still a current product now that IRIS owns it?

IRIS acquired Doc.It in 2021 and its website still refers to existing IRIS Doc.It customers. It also sells a newer cloud product, IRIS Document Management, which it says is available to those customers. Whether to stay, take that, or go elsewhere is the firm’s decision. The extraction approach does not change.

Can archived client files go into a legal document system?

Yes, as documents filed under a client and a matter. The Archive’s structure, whatever the firm’s policy made it, is mapped to the destination’s folders or profile fields. What will not carry over is workflow status. Open work is either completed before cutover or listed for the firm to set up again as tasks.

Do documents from Doc.It Suite 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 Doc.It Suite have a place in Clio Manage?

Most of it does on paper. Contacts, emails, notes, calendar entries, custom fields and templates 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 Doc.It Suite data is loaded into Clio Manage?

Contacts, emails, notes, calendar entries, custom fields and templates 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

Doc.It Suite and Clio Manage are the names and marks of their owners, used here only to identify the two systems.

Moving from Doc.It Suite 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.