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

Data migration route

Bill4Time to Clio Manage migration

Bill4Time is a cloud 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.

FromBill4TimeCloud
  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 with mapping
  8. Billing: Carried with mapping
  9. Trust money: Carried with mapping
  10. Templates: Carried with mapping
  11. Emails: Confirmed in the analysis
  12. Custom fields: Confirmed in the analysis
  13. Intake: Confirmed in the analysis
ToClio ManageCloud
  • 6 carried
  • 4 mapped
  • 3 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Bill4Time to Clio Manage

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

Records in Bill4Time and their place in Clio Manage
RecordIn Bill4TimeIn Clio ManageWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldThe level under a client; firms may label it matter, case, project or engagement.Has a placeImported from a matters template, after contacts.Carried across
ContactsClients, other parties and referrersHeldClients, with the contacts recorded under each.Has a placePeople and companies, with related contacts linked to matters by a separate template.Carried across
DocumentsFiles stored in or linked from the systemHeldFiles stored against contacts and matters; Box and NetDocuments can be connected.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 notesHeldHas a placeMatter notes and contact notes each have a template.Carried across
CalendarAppointments, court dates and deadlinesHeld in partScheduled items sync with Google Calendar or Outlook Calendar.Has 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 unbilledHeldTime and expenses with custom rates, expense categories and billing codes.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 balancesHeldBatch invoicing, LEDES, payment plans and write-offs.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 balancesHeldOperating and trust funds are kept apart on invoices and reports.Has a place in partA trust balance loads as one line per matter or contact; past transactions do not.Carried with mapping
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 automationHeld in partInvoice templates; document templates were not confirmed.Has a placeRebuilt as Clio document templates with its merge fields.Carried with mapping
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 Bill4Time.
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

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 Bill4Time 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 Bill4Time. 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 Bill4Time as at the cutover date, and that load is rehearsed before it is done for real.

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

Where the data is now

Most of what a firm has built up in Bill4Time is financial: years of time entries, invoices, payments and trust movements, coded the way its clients require. A move off it is judged by whether those figures arrive intact and still add up by client and matter. The practice management records around them are usually thinner and take less of the effort.

  1. Billing codes clients expect

    Firms that bill insurers or corporate clients set up billing codes and expense categories so that LEDES invoices are accepted. Those code lists are the firm’s own. They are extracted as reference data and matched to the destination’s codes before any time entry is loaded, since an unmatched code can cause an e-billing rejection later.

  2. QuickBooks already has copies

    The connector has been sending invoices and payments to QuickBooks, where clients appear as customers. If the new system also posts to that QuickBooks file, it must be told about the existing customers and open invoices. Otherwise the first sync creates a second set. The accountant agrees the mapping before go-live.

  3. Client first, then matter

    Everything is filed under a client and then a matter, and firms rename that second level to suit themselves. A consultancy arm may call it a project. The analysis records the label in use and checks whether non-legal projects are mixed in with matters, because they may not belong in a legal system.

  4. Calendars synced with Outlook

    Where the Google Calendar or Outlook Calendar connection is switched on, scheduled meetings, tasks and time entries pass between the two. Those appointments already exist in the mail system, which is not changing, so they are not loaded twice. Deadlines kept only as Bill4Time tasks are the items that need to be carried across.

  5. Rates for past and future

    Bill4Time lets a firm set its own rates alongside its expense categories and billing codes. When time is loaded into a new system the historic entries keep the rate they were billed at. The rate tables for future work are a separate job, rebuilt in the destination and tested by raising a draft invoice on a known matter.

More about moving off Bill4Time

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

  4. Cutover

    Changes in Bill4Time 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. Bill4Time 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 Bill4Time 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 fromBill4Time
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 Bill4Time 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

Bill4Time to Clio Manage: what firms ask

Can we bring all our old invoices, or only what is still owed?

That depends on the destination. Some systems load paid invoices as history. Others accept open balances only, with the old invoices saved as PDFs on each matter. In both cases the debtor total in the new system is checked against the Bill4Time aged receivables report on the cutover date.

We keep documents in NetDocuments, connected to Bill4Time. Do they move?

They can stay where they are. NetDocuments holds the files and Bill4Time only links matters to them. If the new practice system also connects to NetDocuments, the links are re-made matter by matter. Files uploaded directly into Bill4Time are a different case and are extracted with the matter.

How are trust balances moved?

As an opening balance for each client and matter, agreed with the trust bank statement on the day. The transaction history behind each balance moves too where the destination accepts it. A full trial load is done beforehand as a dress rehearsal, because a trust cutover cannot be re-run the way a document load can.

Do trust balances in Bill4Time 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.

Does everything in Bill4Time have a place in Clio Manage?

Most of it does on paper. Emails, custom fields 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 Bill4Time data is loaded into Clio Manage?

Time entries, billing records, trust ledgers and templates are carried with mapping, so each mapping is agreed with you first. Emails, custom fields and intake records 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

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

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