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

Data migration route

LeanLaw to Clio Manage migration

LeanLaw 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.

FromLeanLawCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Time and expenses: Carried with mapping
  4. Billing: Carried with mapping
  5. Trust money: Carried with mapping
  6. Templates: Carried with mapping
  7. Notes: Confirmed in the analysis
  8. Tasks: Confirmed in the analysis
  9. Custom fields: Confirmed in the analysis
  10. Intake: Confirmed in the analysis
ToClio ManageCloud
  • 2 carried
  • 4 mapped
  • 4 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from LeanLaw to Clio Manage

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

Records in LeanLaw and their place in Clio Manage
RecordIn LeanLawIn Clio ManageWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldClients and matters as billing records, with budgets, rates and fee arrangements.Has a placeImported from a matters template, after contacts.Carried across
ContactsClients, other parties and referrersHeld in partClients and billing contacts only.Has a placePeople and companies, with related contacts linked to matters by a separate template.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeMatter notes and contact notes each have a template.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeTasks have a migration template.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTime and expenses tied to client and matter.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 balancesHeldHourly, flat fee and recurring fixed fees; LEDES on some plans.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 balancesHeldClient and matter trust ledgers, with the trust bank account kept in QuickBooks Online.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.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 LeanLaw.
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 LeanLaw 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 LeanLaw. 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 LeanLaw 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 LeanLaw 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 LeanLaw is kept running until the checks on Clio Manage are finished.

Where the data is now

LeanLaw and QuickBooks Online hold two halves of the same financial record, kept in step by a live sync. A firm leaving LeanLaw is usually keeping QuickBooks, at least at first. So the question is less what to extract than how to change the system feeding QuickBooks without posting anything twice, and where the matter-level detail that only LeanLaw holds will live afterwards.

  1. QuickBooks keeps the ledger

    Every invoice, payment and trust transaction entered in LeanLaw is also in QuickBooks Online. If the destination connects to the same QuickBooks company, it must start from an agreed date and recognise what is already there. Where the destination has its own general ledger, QuickBooks is closed off at a period end and balances are carried in.

  2. Matter detail lives in LeanLaw

    QuickBooks knows the totals. LeanLaw knows which timekeeper did what on which matter, at what rate, and against what budget. That is the part to extract: time and expense entries with their narratives, and the invoice lines they became. The sums are checked back to the QuickBooks figures client by client.

  3. Trust in two places

    The trust bank account is an account in QuickBooks Online, and the ledger for each client and matter is in LeanLaw. Both have to agree with the bank statement. The three-way reconciliation is completed and saved for the last period before cutover, and opening trust balances are taken from it.

  4. Compensation and origination

    LeanLaw tracks attorney compensation and origination credit as time is billed and collected, and partners may be paid on those reports. Not every system records origination against a matter. The firm checks early whether the destination can, and saves the historic compensation reports whatever the answer.

  5. It was never the case file

    Parties, deadlines, documents and correspondence were never in LeanLaw. Some firms pair it with Clio or MyCase for those, and others use folders and Outlook. A move to an all-in-one system therefore draws on several sources, and the matter list from LeanLaw is used as the index that ties them together.

More about moving off LeanLaw

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

  4. Cutover

    Changes in LeanLaw 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. LeanLaw 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 LeanLaw 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 fromLeanLaw
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 LeanLaw 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

LeanLaw to Clio Manage: what firms ask

If we stop using LeanLaw, do we lose our QuickBooks Online data?

No. QuickBooks Online is a separate subscription in the firm’s own name, and the invoices, payments and trust entries that synced into it stay there. What goes when LeanLaw goes is the legal layer on top: time narratives, matter ledgers and the reports built from them, which is why those are extracted.

Can the new system take over the same QuickBooks company?

Often, yes. It needs to be told which customers and open invoices already exist so that it links to them and does not create a second set. The switch is made at an agreed date, with LeanLaw’s sync turned off first and the receivables total compared on both sides.

We use LeanLaw with Clio for case management. Which is the source for matters?

Both, for different things. Clio would hold the case detail, documents and calendar, and LeanLaw the time, bills and trust ledgers. The two matter lists are compared in the analysis. A matter that appears in one and not the other is traced and resolved before anything is loaded.

Do trust balances in LeanLaw 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 LeanLaw have a place in Clio Manage?

Most of it does on paper. Notes, tasks, 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 LeanLaw 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. Notes, tasks, 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

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

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