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

Data migration route

BillQuick to Clio Manage migration

BillQuick is a desktop accounting and billing system, and Clio Manage is a cloud practice management system. The financial records lead: balances and open items move, and the matters in Clio Manage are built around them.

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

What moves

What moves from BillQuick to Clio Manage

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

Records in BillQuick and their place in Clio Manage
RecordIn BillQuickIn Clio ManageWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partWork is tracked as projects under clients; there is no matter record as such.Has a placeImported from a matters template, after contacts.Carried across
ContactsClients, other parties and referrersHeldClients with a contact each, employees and vendors.Has a placePeople and companies, with related contacts linked to matters by a separate template.Carried across
DocumentsFiles stored in or linked from the systemTo be confirmedHas a placeFiled under the matter; Clio scopes document migration separately from data.Confirmed in the analysis
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 partTask allocation, forecasting and Gantt charts on projects.Has a placeTasks have a migration template.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldTime cards, timesheets, timers and expense sheets, with submit and approve.Has a place in partUnbilled time entries load; billed time entries do not, by Clio’s migration guide.Carried with mapping
BillingInvoices, payments and debtor balancesHeldManual, batch and joint invoices, statements, payments and credit memos.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 balancesHeld in partRetainers are tracked against clients; no trust ledger appears in BQE’s feature list.Has 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 payablesHeldChart of accounts, vendor bills, checks, general journal and reconciliation.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 itselfHeld in partCustom labels, plus custom report and invoice templates.Has a placeCreated first, then filled from the custom field templates.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partInvoice and report templates only.Has a placeRebuilt as Clio document templates with its merge fields.Carried with mapping

What the plans mean

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

Time, bills and balances move. How much history is a decision.

Coming from an accounting or billing system, the records that count are balances: unbilled time, unpaid invoices, client funds, the ledger. A practice management system takes these as opening positions on a matter. So every client and job in BillQuick needs a matter to land on, and the first piece of work is building that matter list, often from client and project codes that were never meant to be matter numbers.

How much history to bring is the main choice. Paid invoices from years ago can be loaded as records, kept as PDF copies on the matter, or left in a read-only copy of BillQuick. Most firms bring open items and a period of history, and keep the rest as reports. Opening balances in Clio Manage are agreed to the trial balance and aged debtors from BillQuick as at the cutover date, and that load is rehearsed before it is done for real.

BillQuick 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

BillQuick has no matters. A law office that used it has been treating projects as matters, with its own habits about how they were named and numbered. Moving to a legal practice system means turning each client and project into a client and matter, and deciding what to do with the accounting that BillQuick may also have been doing.

  1. One project, one matter

    Every time entry and invoice hangs off a project under a client. Project names and IDs follow whatever convention the firm adopted, so some will carry a matter number, some a description, and a few will cover several pieces of work. Each project is mapped to one matter before any time or billing is loaded.

  2. Activity and expense items

    Time is recorded against activity items and costs against expense items, each with its own tax setting. A legal system expects activity codes or task codes in their place. The item list is usually longer than anyone remembers, so it is cut down and mapped before the trial load.

  3. Contract types and fee schedules

    BillQuick bills a project according to its contract type and can apply a fee schedule, a budget and a billing schedule. Hourly work is the simple case. Fixed fee and recurring arrangements need a matching billing set-up in the destination, or the next invoice will be calculated differently from the last.

  4. Retainers and retainage

    Client retainers are held as retainer balances, and some firms also used retainage on invoices. Neither is a trust ledger. Where retainer money is in fact client money, each balance is reconciled to the bank account that holds it before it is opened as trust in the new system.

  5. Was it the firm’s ledger?

    The program has a chart of accounts, vendor bills, cheque writing and bank reconciliation, and it can also pass data to QuickBooks Desktop or Sage 50. Which of those the firm relied on decides where the general ledger history is taken from. That is checked in the data, not assumed.

More about moving off BillQuick

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 BillQuick 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 BillQuick, 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 BillQuick: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in BillQuick 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. BillQuick 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 BillQuick 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 fromBillQuick
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 BillQuick 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

BillQuick to Clio Manage: what firms ask

We used BillQuick projects as matters. Will that carry over?

It will, as long as each project maps to one matter. The client stays the client, the project becomes the matter, and the project ID is kept as the matter number or as a reference. Projects that held several pieces of work under one name are split during clean-up, before extraction.

Can unbilled time come across?

Unbilled time and expenses can be read with their dates, staff member, hours and description. Whether they arrive as live unbilled entries depends on the destination accepting time at the original rates. The alternative is to bill everything possible before cutover and bring the remainder across as a short list.

Is BillQuick still supported?

BQE counts BillQuick among its legacy products and describes BQE CORE as the next step for existing users. Whether BillQuick itself is still supported should be confirmed with BQE. For a firm moving to a legal system the practical point is to keep the BillQuick company file and a working installation as the read only record.

Do trust balances in BillQuick 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. They are exported from BillQuick 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 BillQuick 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. Documents, emails, notes and calendar entries are confirmed in the analysis. 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

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

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