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

Data migration route

Clio Grow to Lawmatics migration

Clio Grow and Lawmatics are each a cloud CRM and intake system. The records move, and the pipeline, forms and automations are set up again in Lawmatics.

FromClio GrowCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Calendar: Carried across
  4. Intake: Carried across
  5. Documents: Carried with mapping
  6. Custom fields: Carried with mapping
  7. Templates: Carried with mapping
  8. Emails: Confirmed in the analysis
  9. Notes: Confirmed in the analysis
  10. Tasks: Confirmed in the analysis
  11. Billing: Confirmed in the analysis
ToLawmaticsCloud
  • 4 carried
  • 3 mapped
  • 4 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Clio Grow to Lawmatics

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

Records in Clio Grow and their place in Lawmatics
RecordIn Clio GrowIn LawmaticsWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partProspective matters, called opportunities on newer screens, each with a pipeline status.Has a placeLoaded from CSV with a status of PNC, Hired or Lost and a pipeline stage.Carried across
ContactsClients, other parties and referrersHeldPerson and company contacts; synced with Clio Manage where both are used.Has a placeContacts and companies load from CSV; relationships link further parties to a matter.Carried across
DocumentsFiles stored in or linked from the systemHeld in partDocuments prepared from templates and sent for signature during intake.Has a place in partFiles and folders on each matter, added by upload or API, not by the spreadsheet import.Carried with mapping
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partEmails reach a matter through mail sync from a connected mailbox.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeNotes on matters, contacts and companies.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partAppointments booked through Clio Scheduler or entered by hand, with reminders.Has a placeAppointments, called events, with types and locations.Carried across
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeConfirmed in the analysis
BillingInvoices, payments and debtor balancesTo be confirmedHas a place in partInvoices and payments; a past invoice is entered as sent, then marked paid.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldContact and matter custom fields, shared with Clio Manage.Has a placeMatter, contact and company fields. A field must exist before data is imported into it.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument templates, including PDF templates with signature fields.Has a place in partDocument and email templates are rebuilt with Lawmatics merge fields.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldIntake form templates and a pipeline grouped as Intake, Hired and Not hired.Has a placePipelines and stages, marketing sources and campaigns.Carried across

What the plans mean

Carried across
Lawmatics has a place for this kind of record. It is loaded there and checked against Clio Grow.
Carried with mapping
Lawmatics 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

Contacts and leads move. Forms and automations are rebuilt.

Between two tools that manage contacts and enquiries, the records move cleanly and the machinery does not. Each pipeline stage in Clio Grow needs an equivalent in Lawmatics, and stage names seldom line up. Open leads are loaded at the matching stage so that follow-up carries on. Closed and lost leads come across with their outcome, because conversion reporting depends on them. Sources and referrers are put into one list first.

Forms, email templates, sequences and automations are rebuilt by hand. It is worth doing on purpose: most firms find a sequence still running that nobody remembers setting up. Web forms and booking links on the firm’s site are repointed at cutover, and a test enquiry is put through each one. Consent and unsubscribe records move with the contacts and are checked separately, since a mistake there means emailing people who opted out.

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

Where the data is now

Clio Grow holds the part of the firm’s record that comes before a matter exists. Moving off it means deciding how much of that history is worth carrying: open leads certainly, lost leads perhaps, form answers and signed documents where they belong to people who became clients. Contacts and opportunities export as spreadsheets. Completed forms and documents are gathered separately.

  1. Hired matters live in two places

    Once a matter is converted, it exists in Clio Manage as well as in Grow, and the two copies stay in sync. If the firm’s Clio Manage data is also moving, loading both would create every client twice. We take converted matters from Clio Manage and use Grow only for what never left the pipeline.

  2. Your statuses, their three groups

    Pipeline columns are statuses the firm created, grouped under Intake, Hired and Not hired. A new intake tool will have its own stages, and each Grow status is mapped to one. The Not hired group is usually where the volume is. They can come across as contacts with a tag, without a pipeline record.

  3. Form answers and custom fields

    A question on an intake form can be mapped to a custom field on the contact or matter. During the analysis we go through each form template to see which questions were mapped, because that decides whether an answer travels as a field value with the record or has to be taken from the completed form.

  4. Fields shared with Clio Manage

    Custom fields are common to Grow and Clio Manage: creating, editing or deleting one in either product changes it in the other. A firm that is leaving Grow but staying on Clio Manage should not tidy up Grow’s fields on the way out, because the change follows through to its live matters.

More about moving off Clio Grow

Where it is going

Lawmatics takes matters, contacts and companies from CSV files, and its API accepts notes, tasks, appointments, files, time entries and invoices. It is an intake and client relationship system, so a firm arriving from full practice management has to decide what it is for. People and matters load well. There is no general ledger, and years of billing history have no natural home.

  1. Contacts and matters load separately

    The import expects two spreadsheets: one for contacts or companies with no case, such as referrers and other lawyers, and one for matters. A matter import creates the matter and its primary contact together. Every matter has exactly one primary contact, so joint clients are loaded as one primary and one relationship.

  2. Set up before loading

    Owner, stage, practice area, source and campaign are matched by name. A value on the spreadsheet that does not match one in Lawmatics exactly creates a new one, which is how a firm ends up with two spellings of the same practice area. Users, pipelines, practice areas and marketing sources are set up first, and custom fields must exist before data is loaded into them.

  3. Statuses and matter numbers

    Each imported matter must be PNC (potential new client), Hired or Lost, with open and closed handled as sub-statuses the firm creates. The case number is a system field assigned by an auto-numbering pattern and cannot be edited by hand afterwards. Whether old matter numbers can be loaded into it, or belong in a custom field, is tested in the trial load.

  4. Duplicates are matched by email

    With Match Contacts by Email switched on, a contact whose email already exists is skipped or updated, never doubled. Names and phone numbers are not checked. Matters are not deduplicated at all, so two rows with one email create two matters on one contact. Clean-up therefore happens in the spreadsheet, and automations are switched off for every load.

  5. What has no place

    There is no general ledger. The Time & Billing module holds time entries, expenses, invoices and a trust account with a running balance per matter, and past invoices are entered as already sent and then marked paid. A firm that needs its full accounting history keeps the old system read only or carries the books in an accounting package.

More about moving into Lawmatics

How NewLaw runs it

Four steps, in this order.

No financial cutover is planned on this route, so a load can be run again until it is right. If the analysis finds financial records with a place in Lawmatics, they get a rehearsed cutover of their own.

  1. Analysis

    We read what Clio Grow holds and how it is organised, then agree with you where each kind of record will sit in Lawmatics. Anything with no place there stays behind or is archived, and you see which before the move.

  2. Clean-up

    Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.

  3. Trial load

    A trial is loaded into Lawmatics and checked against Clio Grow: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.

  4. Cutover

    After a short freeze on changes in Clio Grow, a final pass over a weekend picks up what changed since the trial. If the analysis found financial records to move, their cutover is rehearsed on a full trial load first. Clio Grow 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 Clio Grow 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 fromClio Grow
Moving toLawmatics

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 Clio Grow holds

    What is in it, how its records link, and where each piece would sit in Lawmatics. 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 Lawmatics

Loaded data is not yet a working system. This is what NewLaw sets up in Lawmatics, beyond the migration, so that people can work in it from the first day.

In Lawmatics the design comes before the data. The pipeline stages, practice areas, custom fields and relationship types decide what the import can hold, and the forms and automations decide what the firm’s intake looks like from the first day. If a practice system sits behind it, the field mapping between the two is part of the same job.

Set-up decisions in Lawmatics

  • Pipelines and stages for intake and for open matters
  • Practice areas, sub-statuses, relationship types and the matter numbering pattern
  • Custom fields on matters, contacts and companies
  • Intake forms, booking links and e-signature document templates
  • Follow-up automations, with marketing sources and campaigns
  • Mail and calendar sync, user roles and practice system integration

Questions

Clio Grow to Lawmatics: what firms ask

We are keeping Clio Manage. What actually needs to move?

Less than firms expect. Clients and matters that were converted are already in Clio Manage. What has to move is the open pipeline, plus the intake forms, document templates and booking pages, which are rebuilt in the new intake tool. Lost leads are optional, and the firm decides how far back to go.

Should leads we never signed come across?

It depends on what the firm does with them. If old enquiries are used for conflict checks or marketing, they are worth loading as contacts with their source and outcome. Where nobody has looked at them in years, an exported spreadsheet kept on file is enough, and the new system starts cleaner.

What happens to signed engagement letters?

A signed document for a client who was hired belongs on that client’s matter. Where the conversion to Clio Manage did not carry it, we collect it from Grow and file it to the matter in the destination. Signed documents for people who never became clients are archived with the export, not loaded.

Does billing history from Clio Grow move into Lawmatics?

That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in Clio Grow before the plan is fixed. Billing records with no place in Lawmatics are kept as reports and invoice copies.

Does everything in Clio Grow have a place in Lawmatics?

Most of it does on paper. Emails, notes, tasks and billing 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 Lawmatics is kept as a readable archive, and you see which before the move.

What has to be decided before Clio Grow data is loaded into Lawmatics?

Documents, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails, notes, tasks and billing records are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.

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

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

Moving from Clio Grow to Lawmatics?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.