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

Data migration route

Lawmatics to Clio Manage migration

Lawmatics is a cloud CRM and intake system, and Clio Manage is a cloud practice management system. Contacts and intake history move, and the matters themselves start life in Clio Manage.

FromLawmaticsCloud
  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 Lawmatics to Clio Manage

Each row is a kind of record Lawmatics 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 Lawmatics and their place in Clio Manage
RecordIn LawmaticsIn Clio ManageWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldA matter is a lead, a client or a lost enquiry, with a status of PNC, Hired or Lost.Has a placeImported from a matters template, after contacts.Carried across
ContactsClients, other parties and referrersHeldContacts and companies; other parties link to a matter as relationships.Has a placePeople and companies, with related contacts linked to matters by a separate template.Carried across
DocumentsFiles stored in or linked from the systemHeld in partA Files tab with folders on each matter. Files download one matter at a time.Has a placeFiled under the matter; Clio scopes document migration separately from data.Carried across
EmailsEmails saved to matters or to the storeHeld in partMail sync logs emails with known contacts on the matter timeline.Has a placeHeld as communications on the matter, with phone logs.Carried across
NotesFile notes, matter notes and contact notesHeldHas a placeMatter notes and contact notes each have a template.Carried across
CalendarAppointments, court dates and deadlinesHeldAppointments with event types, synced with Google, Outlook or iCloud calendars.Has a placeCalendar events have a migration template.Carried across
TasksTo-dos and workflow steps assigned to peopleHeldTasks with custom statuses and tags.Has a placeTasks have a migration template.Carried across
Time and expensesTime and expense entries, billed and unbilledHeld in partTime entries and expenses, in the Time & Billing module.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 balancesHeld in partInvoices and payments, in the Time & Billing module.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 partA trust account with a running balance per matter, in the Time & Billing module.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 on matters, contacts and companies.Has a placeCreated first, then filled from the custom field templates.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument templates, email templates, custom forms and automations.Has a placeRebuilt as Clio document templates with its merge fields.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldPipelines, custom forms, booking links, marketing sources and campaigns.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 Lawmatics.
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 Lawmatics 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

Contacts and enquiries move. Matters begin in the new system.

A CRM knows people: who enquired, who referred them, what was sent and when. It does not know matters the way a practice system does. So the move from Lawmatics to Clio Manage is mostly a contacts job, and contacts are where duplicates live. The same person appears as a lead, a client and a referrer, sometimes under three email addresses. They are merged before extraction where they can be identified, because Clio Manage will invoice and receipt against these records.

Pipelines, campaigns and automations seldom have a direct equivalent in a practice system. Open enquiries can be loaded as contacts with a note of their stage, or opened as matters if the firm wants them worked from the first day. Intake forms and email sequences are set up again in whatever Clio Manage or its intake tool provides. Past correspondence is kept as notes or documents on the contact, so the history of a relationship can still be read.

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

Where the data is now

Lawmatics will export matters, contacts and companies as CSV files with every field, custom fields included. Files are different: they cannot be exported for all matters at once. So a move off it runs in two streams, a quick one for the structured records and a slower one that collects each matter’s files, notes and timeline.

  1. Three statuses, one record type

    Leads, clients and lost enquiries are all matters, told apart by a status of PNC, Hired or Lost and any sub-statuses the firm added. A practice system usually wants only the hired ones as matters. The others go to its intake side if it has one, or are kept as contacts with a note of the enquiry.

  2. Files come out matter by matter

    The bulk export covers records and fields. Files saved on matters, the vendor’s help centre says plainly, cannot be exported for all matters at once in the app, only downloaded matter by matter. The API also exposes files and folders, which is the other route for any real volume. Either way the result is checked against a count for each matter.

  3. Relationships are separate contacts

    A spouse, a co-defendant or a referring lawyer is linked to a matter through a relationship type the firm defined, and each is a full contact in the CRM. Those links are exported with the matter and mapped to the destination’s party roles. Where a role has no equivalent, the firm chooses the nearest one.

  4. Often already synced elsewhere

    Plenty of firms have Lawmatics pushing hired matters into Clio Manage or another practice system. That sync runs mostly one way, and notes, files or fields added in Lawmatics afterwards cross only when someone presses Sync again. Before a move the two systems are compared, so the later additions are not lost.

  5. Automations and forms

    Intake forms, email campaigns and automations do the daily work in this product, and none of them export as something another system can run. Each live automation is documented with its trigger and steps. Forms embedded in the firm’s website are replaced at cutover so enquiries stop arriving in the old account.

More about moving off Lawmatics

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

  4. Cutover

    Changes in Lawmatics 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. Lawmatics 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 Lawmatics 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 fromLawmatics
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 Lawmatics 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

Lawmatics to Clio Manage: what firms ask

Can we move from Lawmatics into a full practice management system?

Yes. Hired matters and their contacts map naturally onto clients and matters, and the custom fields come out in the same export. What needs thought is the enquiries that never became clients. A destination with an intake module can take them as leads. Otherwise they are kept as contacts, or left in the export file.

Do the files on each matter come with it?

They do, but not through the bulk export, which covers records only. Files are downloaded per matter or pulled through the API with their folder names. Signed engagement documents and completed intake forms are saved to the Files tab automatically, so those are included. The trial load compares file counts matter by matter.

What happens to our trust balances in Lawmatics?

The trust account table exports to CSV as filtered on screen, showing deposits, payments and a running balance. Balances per matter are rebuilt in the destination from that table and agreed to the bank statement before cutover. The trust cutover is rehearsed on a full trial load first, because it cannot simply be run again.

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

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

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