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

Data migration route

Lawcus to Clio Manage migration

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

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

What moves

What moves from Lawcus to Clio Manage

Each row is a kind of record Lawcus holds, whether Clio Manage has a place for it, and what is planned. On this route seven kinds of record carry across, five kinds need mapping and one kind has no place in Clio Manage and is archived.

Records in Lawcus and their place in Clio Manage
RecordIn LawcusIn Clio ManageWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldShown as cards on boards with a stage, or as a list; numbers come from a saved scheme.Has a placeImported from a matters template, after contacts.Carried across
ContactsClients, other parties and referrersHeldContacts with custom fields and field groups.Has a placePeople and companies, with related contacts linked to matters by a separate template.Carried across
DocumentsFiles stored in or linked from the systemHeldFolders in Lawcus, with two-way sync to Google Drive and links to Dropbox, Box or OneDrive.Has a placeFiled under the matter; Clio scopes document migration separately from data.Carried across
EmailsEmails saved to matters or to the storeHeld in partEmails and attachments logged to a matter through the Gmail or Outlook add-ins.Has a placeHeld as communications on the matter, with phone logs.Carried across
NotesFile notes, matter notes and contact notesHeldNotes and interactions on a matter can be pinned or starred.Has a placeMatter notes and contact notes each have a template.Carried across
CalendarAppointments, court dates and deadlinesHeldHas a placeCalendar events have a migration template.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldNo-code workflows can create tasks when a matter changes.Has a placeTasks have a migration template.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldHas 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 contingency; invoice templates per currency; credit notes.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 balancesHeldTrust balances and a minimum retainer threshold per matter.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 itselfHeldCustom fields and field groups for contacts and matters.Has a placeCreated first, then filled from the custom field templates.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument automation and reusable invoice templates.Has a placeRebuilt as Clio document templates with its merge fields.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldLeads on a Kanban board, with client-facing and internal forms.No placeLeads and intake forms belong in Clio Grow.Kept as a readable archive

What the plans mean

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

The whole practice moves, accounts included.

A move between two practice management systems is the widest kind there is. Lawcus and Clio Manage 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 Lawcus’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 Lawcus 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 Lawcus is kept running until the checks on Clio Manage are finished.

Where the data is now

In Lawcus a matter’s position on a board says as much about it as any field. Stages, boards and the automations attached to them are how a firm on Lawcus knows where every file stands. A move off it has to turn that visual arrangement into something the destination can store, and it has to do so without losing the difference between a lead and a matter.

  1. Stages are the status

    Each board has its own stages, and a matter’s stage is what staff look at to see progress. A conveyancing board and a litigation board will not share stage names. Destinations tend to offer one status list, or a status per matter type. Every board’s stages are mapped separately, and the firm approves the mapping.

  2. Leads sit on boards too

    Prospects are tracked on a Kanban board of their own before they become clients. A lead and a matter can look alike in the interface. The extraction keeps them apart, and leads that were never converted are loaded as intake records or left as an exported list, depending on what the destination offers.

  3. Automations are not data

    No-code workflows send emails, create tasks and produce documents when a matter changes stage or a form comes in. None of that is a record that can be moved. The workflows are documented as rules during the analysis, and the firm chooses which ones to rebuild in the new system’s own automation.

  4. QuickBooks was fed one way

    Lawcus pushes invoices, payments and expenses to QuickBooks Online and takes nothing back. An edit made directly in QuickBooks is therefore unknown to Lawcus. The two can drift apart. Receivables are compared on both sides before cutover, and the firm decides which figure is right where they differ.

  5. More than one currency

    Invoice templates can be set up for clients billed in different currencies. A destination that works in one currency cannot hold those balances as they are. Foreign-currency clients are identified early, and the firm decides whether their history is converted at a stated rate or kept in the old system.

More about moving off Lawcus

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

  4. Cutover

    Changes in Lawcus 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. Lawcus 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 Lawcus 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 fromLawcus
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 Lawcus 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

Lawcus to Clio Manage: what firms ask

Our documents sync between Lawcus and Google Drive. Which copy is moved?

The Google Drive copy is usually the easier source, because it is in the firm’s own account and the sync keeps the two alike. Lawcus supplies the link between each folder and its matter. A sample of matters is compared on both sides first to confirm nothing is missing from the Drive.

Can our matter numbers be kept?

Yes. Lawcus generates matter numbers from a numbering scheme the firm saved, so the numbers are consistent and can be carried as they are. If the destination produces numbers in another format, the Lawcus number is kept in a reference field and new matters follow the new format.

What happens to forms our clients filled in?

Answers that were saved to fields on a contact or matter are data and move with that record. Forms marked internal are treated the same way. The form designs are specific to Lawcus. If the new system has intake forms, they are rebuilt there from the same questions.

Do trust balances in Lawcus 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 intake records. They are exported from Lawcus 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 Lawcus 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. 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

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

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