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

LEAP to Clio migration

NewLaw moves law firms from LEAP to Clio Manage as a fixed-price service. We analyse your LEAP data, de-duplicate and clean it, map it to Clio, check the result against LEAP and run the cutover.

This page sets out what moves, what does not, what to settle first and how long it takes.

LEAP to Clio migration at a glance

What moves
Contacts, matters, unbilled time and expenses, and a balance per matter for outstanding fees and trust. Documents are scoped by Clio.
What does not
Invoices, billed time and trust transaction history. They stay in your LEAP archive.
What we do
Analysis, de-duplication, clean-up, mapping, a checked trial load and the cutover.
Price
Fixed price, set after a free first call and a look at your data.

What moves and what does not

What moves from LEAP to Clio

Clio's help centre lists what can be migrated from LEAP, and what a Clio Manage migration does and does not include in general. These tables set out both, as Clio gives them.

Clio lists as data that can be migrated
DataDetail
ContactsThe firm's contact records.
MattersThe firm's matter records.
Unbilled time entriesTime not yet billed in LEAP.
Unbilled expense entriesDisbursements not yet billed in LEAP.
Outstanding balancesOne summary line per matter, showing the balance at the time of export.
Trust balancesOne line per matter or contact, showing the balance at the time of export.
DocumentsFrom Clio's general list, not its LEAP list: subject to scoping, with additional fees based on volume.
Clio lists as data that cannot be migrated
DataDetail
Invoices and billed timeInvoices, historical bills, billed time entries and bill payments.
Account transactionsTrust account transactions, requests and payments, operating account transactions and accounts receivable ledgers.
Billable ratesUser, client and matter rates.
Reports, user permissions and settingsEach is on Clio's list of data that cannot be migrated.

In its LEAP list, Clio also says a fee may apply to the data export.

Clio's LEAP list and its migration overview include trust balances. Its article on preparing data says to apply credits and trust payments to outstanding bills before exporting, because credits and trust balances will not be migrated. Confirm with Clio's migrations team how your trust balances will be handled.

Sources: Clio help centre: Migrating data from your current software (opens in a new tab); Clio help centre: Clio Manage data migration overview (opens in a new tab); Clio help centre: Prepare data for migration (opens in a new tab). Clio changes these lists from time to time. Confirm the current one with Clio before you plan around it.

Before anything is imported

Analysis, de-duplication and clean-up come first.

An import brings across the records it is given. Most of the work in a good migration happens before it.

  • What we analyse

    How many contacts, matters and documents there are, and how many matters are open or closed. Which fields and matter types the firm actually uses. Whether every matter has a client and every document belongs to a matter. Whether work in progress, outstanding balances and trust balances in the data agree with LEAP's own reports.

  • What we de-duplicate

    Contacts and matters that were entered more than once: the same person saved as a client on one matter and as the other party on another, or the same company under two spellings. Duplicates are merged in the LEAP data before it is extracted. We aim to remove them all. It is not always possible, so some may still carry across.

  • What we clean

    Inconsistent and legacy-format entries, such as names, addresses and phone numbers stored in different ways. Matter references that documents are matched on, which have to be unique. Old fields that need a place in the new system's structure. Each is fixed or mapped before the trial load.

Clio's help centre says its migrations team does not clean or modify a firm's data, and that any errors or duplicates in the previous system will carry over on import. That preparation is the work NewLaw does. Source: Clio help centre: Prepare data for migration (opens in a new tab)

Why it decides whether the new system is trusted on day one

On the first morning a lawyer searches for a client. If three versions of that client come up, a conflict check can miss a match, the client's matters are split between the records, and nobody knows which one to update.

If a trust balance does not match the day before, the accounts team stops relying on the new system and keeps a spreadsheet beside it.

People decide in the first week whether the new system is the record of the firm. Clean data is what lets them decide yes.

Before the move

What to settle before a LEAP to Clio move

  1. Who runs which part

    Clio says a migration can be done with its self-serve tools and templates, or with the help of its migrations team. Agree at the start which parts of the import Clio's team runs and which NewLaw runs, so nothing falls between the two. The analysis, de-duplication, clean-up, mapping and checking on this page are NewLaw's work. Source: Clio help centre: Clio Manage data migration overview (opens in a new tab)

  2. Where the accounts will be kept

    Decide where the firm's general ledger will live after the move. Clio's Australian website lists trust account management among its features, and its app directory lists a Xero integration as available in Australia. Confirm with Clio what your plan includes, then decide which balances come across.

  3. Matter types and fields

    Decide how each LEAP matter type and each field you rely on will be represented in Clio. Fields with no matching place are generally brought across as a note, so the mapping is agreed before the trial load.

  4. Forms and precedents

    List the court and government forms and the precedents your team uses in LEAP, and decide how each will be produced after the move. Your own precedents come across as base templates and their automation is rebuilt.

  5. Your LEAP agreement and export

    Check your notice date and how the data will come out of LEAP before a cutover is booked. The LEAP migration page lists what to check before you give notice.

What to check in your LEAP agreement

How we run it

LEAP to Clio, in five steps.

  1. Analyse

    We look at what is in your LEAP data and at what the new system can hold, then give you a plan and a fixed price.

  2. De-duplicate and clean

    Duplicates are merged and inconsistent entries fixed in the source data, before it is extracted.

  3. Map

    Each field in the old data is mapped to its place in the new system, including custom fields and the records that do not fit neatly.

  4. Trial load and check

    A full test migration. We check it against LEAP on record counts, financial totals, the links between clients, matters and documents, and document dates. Your people check it too.

  5. Cut over

    A short freeze on changes in LEAP, a final collection of the data, and the move over a weekend: close off on Friday, start in the new system on Monday.

Document and matter migration can be run again, so each trial load is checked until it agrees with LEAP. The trust and financial cutover cannot be re-run in the same way. It gets a rehearsal on a full trial load, a freeze window and a go or no-go decision beforehand.

How long it takes

How long a LEAP to Clio migration takes

Clio publishes no fixed duration. It says processing time varies with the size and complexity of the data, and that its team gives the firm a timeline. Clio also tells firms to stop using the old system once its data has been exported, because anything entered afterwards is not captured and has to be transferred manually. We plan a short freeze and a final collection of the data just before the cutover weekend to keep that gap small. Source: Clio help centre: Clio Manage data migration overview (opens in a new tab)

It depends on five things:

  • how many matters and documents there are
  • how much clean-up the data needs
  • how many trial loads it takes before the checks agree
  • which financial balances move, and when your accounts can close off
  • the new system's own set-up timetable, and your people's time to check the test migration

As a guide to the whole project, setting up a new practice management system typically takes four to eight weeks for a firm of up to 10 users, eight to 16 weeks for 10 to 50 users, and three to six months for a larger or multi-office firm. The cutover itself is planned for a single weekend.

Questions

LEAP to Clio: what firms ask

Something we have not answered?

Email info@newlaw.com +61 1300 495 281

Can NewLaw migrate our firm from LEAP to Clio?

Yes. NewLaw moves law firms from LEAP to Clio Manage, for a fixed price. We analyse the LEAP data, de-duplicate and clean it, map it to Clio, run a trial load that is checked against LEAP, and plan and run the cutover.

What data moves from LEAP to Clio?

Clio's help centre lists contacts, matters, unbilled time entries, unbilled expense entries, outstanding balances as one summary line per matter, and trust balances as one line per matter or contact. Documents can be migrated subject to scoping by Clio, with additional fees based on volume. Confirm the current list with Clio before you plan around it.

What does not move from LEAP to Clio?

Clio's help centre lists accounting and financial history as data that cannot be migrated: invoices, billed time entries, bill payments, historical bills, and trust and operating account transactions. Billable rates, reports, user permissions and settings are on the same list. The history stays in your LEAP archive or in exported reports.

Does our trust accounting history move to Clio?

No. Clio lists trust account transactions as data that cannot be migrated. What its LEAP list includes is a balance: one line per matter or contact for trust and one summary line per matter for outstanding fees, as at the export. Clio's article on preparing data also says credits and trust balances will not be migrated, so confirm with Clio's migrations team how your trust balances will be handled, and keep the LEAP reports your trust records require.

Do our documents and emails move from LEAP to Clio?

Documents can be migrated. Clio treats them as subject to scoping, with additional fees based on volume. Before the move we check the document folders against the matters, so files can be matched to the right matter.

How long does a LEAP to Clio migration take?

It depends on how many matters and documents there are, how much clean-up the data needs, how many trial loads it takes before the checks agree, which balances move and your people's time to check the test migration. As a guide to the whole project, setting up a new practice management system typically takes four to eight weeks for a firm of up to 10 users and eight to 16 weeks for 10 to 50 users. The cutover itself is planned for a single weekend.

Can we keep using LEAP during the migration?

Until the final export, yes. Clio's guidance is to stop using the old system once the data is exported, because anything entered afterwards is not captured and has to be transferred manually. We plan a short freeze and a final collection of the data just before the cutover weekend to keep that gap small.

Will duplicate contacts be cleaned up before the move to Clio?

Yes, that is a core part of our work. An import brings across the records it is given, so duplicate contacts and matters are merged in the LEAP data before it is extracted, and inconsistent entries are fixed. We aim to remove every duplicate. It is not always possible, and some may still carry across.

What does a LEAP to Clio migration cost?

NewLaw's work is fixed price. Every firm's data is different, so the price is set after a free first call and a look at what is in your LEAP data. You get it in writing before any work starts. Separately, ask Clio what its own migration covers for your plan, and ask LEAP whether exporting your data carries a cost.

Two ways to start

Still deciding where to move?

Choose the system before you plan the move, and see where AI fits once your data is in it.

  • Choose your systems

    Technology stack selection

    What you get
    A requirements register, a costed comparison of the shortlisted systems, the vendors' offers in writing and one written recommendation.
    How long
    About four weeks for a firm of about 15 people. 12 to 16 weeks for a larger firm with a separate document system.
    Pricing
    Fixed price. Every firm is different, so the price is set after a free first call.
    What happens next
    A free first call, then a written fixed-price proposal. Work starts on a date agreed when you accept.
    How the service works: Technology stack selection

    How big is your team?

    Step 1 of 6 in the stack builder

    Choosing an answer opens the stack builder at step 2 with your answer kept.

  • Put AI to work

    AI advisory and enablement

    What you get
    Guided working sessions on your real tasks, an AI use policy your firm approves, a register of tested tasks and a reference library you own.
    How long
    Two to four weeks for a small first group. 12 to 16 weeks for a larger firm, alongside technology stack selection.
    Pricing
    Fixed price. Every firm is different, so the price is set after a free first call.
    What happens next
    A free first call, then a written fixed-price proposal. The first session is booked when you accept.

    How is your firm currently using AI?

    Question 1 of 7 in the readiness assessment

    Choosing an answer opens the AI readiness assessment at question 2 with your answer kept.

The two are often run together as one engagement.

Moving from LEAP to Clio?

Tell us where you are moving and roughly how many matters you have. A free first call, then a fixed price in writing.

We reply within one business day.