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

Data migration route

Zola Suite to Clio Manage migration

Zola Suite and Clio Manage are each a cloud practice management system. Both run a whole practice, so this is a full move, and the financial records set the timetable.

FromZola SuiteCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Emails: Carried across
  5. Notes: Carried across
  6. Calendar: Carried across
  7. Tasks: Carried across
  8. Time and expenses: Carried with mapping
  9. Billing: Carried with mapping
  10. Trust money: Carried with mapping
  11. Custom fields: Carried with mapping
  12. Templates: Carried with mapping
ToClio ManageCloud
  1. Firm accounts: Kept as a readable archive
  2. Intake: Kept as a readable archive
Readable archiveNo place in Clio Manage
  • 7 carried
  • 5 mapped
  • 2 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Zola Suite to Clio Manage

Each row is a kind of record Zola Suite holds, whether Clio Manage has a place for it, and what is planned. On this route seven kinds of record carry across, five kinds need mapping and two kinds have no place in Clio Manage and are archived.

Records in Zola Suite and their place in Clio Manage
RecordIn Zola SuiteIn Clio ManageWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldHas a placeImported from a matters template, after contacts.Carried across
ContactsClients, other parties and referrersHeldHas a placePeople and companies, with related contacts linked to matters by a separate template.Carried across
DocumentsFiles stored in or linked from the systemHeldAny file type, indexed for search, with a new version saved on each edit.Has a placeFiled under the matter; Clio scopes document migration separately from data.Carried across
EmailsEmails saved to matters or to the storeHeldAn email client is part of the product and files messages against matters.Has a placeHeld as communications on the matter, with phone logs.Carried across
NotesFile notes, matter notes and contact notesHeldHas a placeMatter notes and contact notes each have a template.Carried across
CalendarAppointments, court dates and deadlinesHeldHas a placeCalendar events have a migration template.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldHas a placeTasks have a migration template.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldHas a place in partUnbilled time entries load; billed time entries do not, by Clio’s migration guide.Carried with mapping
BillingInvoices, payments and debtor balancesHeldOne matter can be split between several billing clients, each with its own invoice.Has a place in partAn outstanding balance loads as one line per matter; past invoices do not.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldHas a place in partA trust balance loads as one line per matter or contact; past transactions do not.Carried with mapping
Firm accountsGeneral ledger, office account and payablesHeldVendor bills, cheque writing and financial statements sit in the same system.No placeNot in Clio Manage. Books sit in a linked accounting package, or in Clio Accounting where Clio offers it.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfHeldHas a placeCreated first, then filled from the custom field templates.Carried with mapping
TemplatesPrecedents, document templates and automationHeldHas a placeRebuilt as Clio document templates with its merge fields.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldLeads and intake forms are handled in the built-in CRM.No placeLeads and intake forms belong in Clio Grow.Kept as a readable archive

What the plans mean

Carried across
Clio Manage has a place for this kind of record. It is loaded there and checked against Zola Suite.
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.
Kept as a readable archive
Clio Manage has no place for it. It is exported in a format that opens without Zola Suite 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

The whole practice moves, accounts included.

A move between two practice management systems is the widest kind there is. Zola Suite and Clio Manage each keep matters, contacts, documents, time and money in one place, but no two systems link those records the same way. In one, a client is a contact with a role on the matter. In another, every matter carries its own client card. Most of the analysis goes into those links, because a matter that arrives without its client or its documents is the first thing staff find.

The financial side decides the dates. Unbilled time, debtor balances and trust ledgers have to agree with Zola Suite’s own reports as at one day, and a new system usually wants them as opening balances, not as years of transactions. So the firm decides early how much history comes across as live records and how much is kept as reports. Matter and document loads can be repeated until they are right. The money is loaded once.

Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Zola Suite 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 Zola Suite is kept running until the checks on Clio Manage are finished.

Where the data is now

Nobody moves off Zola Suite as such any more. The records are in CARET Legal, and that is the system the data is taken from. Firms that joined in the Zola years tend to have the longest history in it, with billing arrangements and document links set up long ago that current staff may not know about. Finding those early is most of the analysis.

  1. One account, two names

    Staff who say Zola and staff who say CARET are talking about the same login. The vendor announced a new name, not a new system, so there should be no older archive to hunt for. Old bookmarks, saved report names and procedure documents may still carry the Zola name, and it helps to list them before cutover.

  2. Split billing on a matter

    A single matter can be billed to several clients at set percentages, with fees and costs split separately and a distinct invoice number for each payer. Many systems expect one bill-to client per matter. Split matters are listed in the analysis, and the firm chooses between sub-matters and a manual split in the destination.

  3. Payables and cheques

    Vendor bills, outgoing payments and cheque runs are recorded here, along with the costs passed on to matters. When the firm leaves, its unpaid vendor bills and its vendor list need a home in whatever accounting package comes next. That list is reconciled to the payables report on the day of the freeze.

  4. Worldox or NetDocuments links

    Some firms never used the built-in document store. They linked each matter to a Worldox cabinet or a NetDocuments workspace and worked from there. Those documents are not in the practice management database at all. The analysis records which store each matter points to, so no folder is assumed to be empty when it is only held elsewhere.

  5. Every edit kept as a version

    Editing a Word document inside the product saves a new version each time, and any earlier one can be restored. A long-running matter may hold dozens of versions of one agreement. The firm decides whether all of them move or only the current one, and the document count in the trial load is checked against that decision.

More about moving off Zola 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.

Trust money moves on this route, so the trust cutover gets a rehearsal of its own.

  1. Analysis

    We read what Zola Suite holds and how its records link, then agree with you, field by field, where each piece will sit in Clio Manage. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  2. Clean-up

    Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Zola Suite, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into Clio Manage as a trial and checked against Zola Suite: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Zola Suite are frozen for an agreed window, the data is collected a final time and Clio Manage goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. Zola 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 Zola 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 fromZola 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 Zola 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

Zola Suite to Clio Manage: what firms ask

Is Zola Suite still available?

Not under that name. The vendor renamed it CARET Legal after AbacusNext became CARET, and the Zola Suite web address now leads to the CARET Legal site. It was presented as a rebrand, so a firm that never left is simply using CARET Legal.

Our invoices go back to when we started on Zola. Can the full billing history move?

It depends on what the destination will accept. Some systems take historic invoices and payments as records. Others take only open balances, with the old invoices attached as PDFs. Split-billed matters need the closest look, since each payer has its own invoice number.

Do we plan the move as Zola Suite or as CARET Legal?

As CARET Legal, because that is what the firm logs into and what the vendor supports. The planning is the same either way. One extra step for a long-standing Zola firm is checking for features switched on years ago, such as split billing or a Worldox link.

Do trust balances in Zola Suite have a place in Clio Manage?

In part. A trust balance loads as one line per matter or contact; past transactions do not. The analysis sets out which trust records have a place in Clio Manage and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.

What happens to records Clio Manage has no place for?

On this route that is the firm’s accounts and intake records. They are exported from Zola Suite 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 Zola Suite data is loaded into Clio Manage?

Time entries, billing records, trust ledgers, custom fields and templates are carried with mapping, so each mapping is agreed with you first. The firm also sets the cutover date and how much financial history comes across as live records.

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

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

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