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

Data migration route

Clio Manage to Centerbase migration

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

FromClio ManageCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Notes: Carried across
  5. Calendar: Carried across
  6. Tasks: Carried across
  7. Time and expenses: Carried across
  8. Billing: Carried across
  9. Trust money: Carried across
  10. Firm accounts: Carried across
  11. Intake: Carried across
  12. Emails: Carried with mapping
  13. Custom fields: Carried with mapping
  14. Templates: Carried with mapping
ToCenterbaseCloud
  • 11 carried
  • 3 mapped
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Clio Manage to Centerbase

Each row is a kind of record Clio Manage holds, whether Centerbase has a place for it, and what is planned. On this route eleven kinds of record carry across and three kinds need mapping.

Records in Clio Manage and their place in Centerbase
RecordIn Clio ManageIn CenterbaseWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldOpen, Pending or Closed, with a display number built from a firm-wide numbering scheme.Has a placeLoaded under their client, with practice-specific custom fields.Carried across
ContactsClients, other parties and referrersHeldPerson and company contacts; related contacts link other parties to a matter.Has a placeClients, related parties and prospects.Carried across
DocumentsFiles stored in or linked from the systemHeldStored under contacts and matters in folders, with version history.Has a placeInto Document Storage, or left in a connected NetDocuments, iManage or SharePoint store.Carried across
EmailsEmails saved to matters or to the storeHeldFiled from Outlook as email logs, or forwarded to a matter and stored as EML files.Has a place in partEmails saved to matters; mailboxes stay in Microsoft 365.Carried with mapping
NotesFile notes, matter notes and contact notesHeldMatter notes and contact notes.Has a placeCarried across
CalendarAppointments, court dates and deadlinesHeldHas a placeCarried across
TasksTo-dos and workflow steps assigned to peopleHeldHas a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldTime entries and expense entries are both called activities.Has a placeCarried across
BillingInvoices, payments and debtor balancesHeldBills move from draft through approval to unpaid and paid.Has a placeThe vendor says billing history can be migrated; the depth is set in the analysis.Carried across
Trust moneyTrust or client account ledgers and balancesHeldTrust funds can be held at client level or matter level.Has a placeMultiple trust and retainer accounts per matter or client.Carried across
Firm accountsGeneral ledger, office account and payablesHeld in partClio Accounting is a separate Clio product, documented for the US and Canada.Has a placeGeneral ledger with chart of accounts; opening trial balance agreed with the accountant.Carried across
Custom fieldsFields and record types the firm added itselfHeldMatter and contact custom fields, shared with Clio Grow.Has a placeCreated and placed on page layouts before records are loaded.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument templates with merge fields, made from Word, Excel, PowerPoint and PDF files.Has a place in partTemplates are rebuilt to merge Centerbase client and matter data.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partLead pipeline and intake forms are in Clio Grow, a companion product.Has a placeEnquiries are held as Potential New Client records; loading open ones is confirmed in the analysis.Carried across

What the plans mean

Carried across
Centerbase has a place for this kind of record. It is loaded there and checked against Clio Manage.
Carried with mapping
Centerbase holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.

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. Clio Manage and Centerbase 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 Clio Manage’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 Clio Manage 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 Clio Manage is kept running until the checks on Centerbase are finished.

Where the data is now

Leaving Clio Manage is mostly a question of what comes out and in what form. Clio’s export page produces spreadsheets of contacts, matters, notes, tasks, calendar entries and time, and balances come from reports. Documents and billing history are not in those spreadsheets, so they are collected separately and joined back to the right matters.

  1. The display number can change

    A matter’s display number is built from a firm-wide scheme: matter number, client name, year and other parts in a chosen order. An administrator can change the scheme and apply it to every existing matter. The number in the export may therefore differ from the one on older letters. We check the Client Reference field as well.

  2. Trust held at client level

    Clio lets a firm hold trust funds against the client as a whole, not only against a matter. Many trust ledgers elsewhere are strictly per matter. Each client-level balance then has to be allocated to a matter before cutover, and the accounts team makes that allocation in Clio so the closing report already shows it.

  3. Activities and communications

    Time entries and expense entries are both called activities and export as separate lists. Filed emails and phone logs are communications. An email forwarded to a matter’s Maildrop address is stored as an EML file, while one filed from Outlook is an email log. The analysis counts each kind, since they land in different places.

  4. Documents may sit outside Clio

    Files can be stored in Clio itself or in a connected service. With the OneDrive for Business integration, for example, Clio creates a root folder with a subfolder for every client and matter. Before planning the document move we establish which store each office has been saving to, and whether both hold files.

  5. Draft bills at cutover

    A bill in Clio is a draft, pending approval, unpaid or paid, and a draft does not yet count towards the client’s balance. Before the final collection the accounts team approves or discards every draft. The debtor figure taken across is then the one on Clio’s accounts receivable report, with no half-finished bills behind it.

More about moving off Clio Manage

Where it is going

Centerbase takes practice, billing, trust and accounting data together, so loading a firm into it is a finance project as much as a matter load. Clients come first because matters inherit from them. The chart of accounts, bank accounts and accounting basis are fixed before balances go in. Because the product is configured per firm, the fields and layouts are designed before the trial load, not after.

  1. Clients carry the billing rules

    Billing arrangements, rates and accounting preferences are held on the client and passed to its matters. Source systems that create a fresh client for every matter leave duplicates behind. Those are merged during clean-up, so that each real client exists once and its terms are set in one place.

  2. The ledger comes too

    Centerbase has a full general ledger and runs on a cash or accrual basis. A firm arriving from a billing system with QuickBooks beside it is consolidating two sets of records. The accountant decides the basis and the opening date, and the trial balance loaded is agreed to the old books.

  3. Trust and retainers are separate

    A matter can hold multiple trust and retainer accounts. Source systems often blur the two, recording an advance on fees as trust or the reverse. Each balance is classified before loading, and client-level funds that were never tied to a matter are assigned to one or held at client level.

  4. Decide the document home

    Documents can go into built-in Document Storage, or stay in NetDocuments, iManage or SharePoint and be connected. Centerbase can create a standard folder structure when a matter is opened. That structure is agreed first, so migrated documents are filed into the same folders that new matters will get.

  5. Fields are designed, not assumed

    With unlimited custom fields, nearly every source field can have a home. That is a reason for restraint. Each one must be created and placed on a layout, and a page crowded with unused fields slows people down. The firm chooses which fields earn a place and which become a note.

More about moving into Centerbase

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 Clio Manage holds and how its records link, then agree with you, field by field, where each piece will sit in Centerbase. 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 Clio Manage, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

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

  4. Cutover

    Changes in Clio Manage are frozen for an agreed window, the data is collected a final time and Centerbase 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. Clio Manage 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 Clio Manage 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 fromClio Manage
Moving toCenterbase

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

    What is in it, how its records link, and where each piece would sit in Centerbase. 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 Centerbase

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

Setting up Centerbase is largely configuration. Bill templates, rate tables and the pre-bill approval chain have to match how the firm bills today, or the first billing cycle exposes the gaps. The chart of accounts and bank accounts are built with the finance team. Workflows that open matters, create folders and assign first tasks are written last, once the fields they depend on are settled.

Set-up decisions in Centerbase

  • Bill templates and billing arrangements for each client type
  • Rate tables, timekeepers and the pre-bill approval chain
  • Chart of accounts, bank accounts and cash or accrual basis
  • Custom fields, page layouts and automated workflows by practice
  • Document storage choice and the standard matter folder structure
  • Outlook and Microsoft 365 connection for email and calendar

Questions

Clio Manage to Centerbase: what firms ask

Can our matter numbers stay the same when we leave Clio?

The destination decides. If it accepts a supplied matter number, the Clio display number is loaded as it stands. Because Clio’s scheme can include the client’s name, some firms take the chance to shorten it. Where the new system insists on its own numbering, the Clio number is kept in a reference field.

Does our billing history come out of Clio?

Time and expense entries export as lists, and outstanding balances come from the accounts receivable report. Whether the new system can hold past invoices as invoices depends on that system. Where it cannot, we agree with the firm how the history is kept: as PDF copies on each matter, or in the archived Clio data.

We also use Clio Grow. Is that a separate job?

It is a separate product with its own data, so it is scoped separately. Matters already converted from Grow exist in Clio Manage and move with it. What remains in Grow is the pipeline: leads not yet hired, intake forms and signed engagement documents. The analysis shows how much of that the firm still needs.

Do trust balances in Clio Manage have a place in Centerbase?

Yes. Centerbase keeps trust ledgers. Multiple trust and retainer accounts per matter or client. Balances are loaded by matter and agreed to the trust report from Clio Manage as at the cutover date. That load cannot be re-run the way a document load can, so it is rehearsed on a full trial load first.

Does everything in Clio Manage have a place in Centerbase?

On paper, yes: each kind of record Clio Manage holds has a place in Centerbase. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.

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

Emails, 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

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

Moving from Clio Manage to Centerbase?

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

We reply within one business day.