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

Data migration route

Clio Grow to Rocket Matter migration

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

FromClio GrowCloud
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Documents: Carried across
  4. Calendar: Carried across
  5. Custom fields: Carried with mapping
  6. Templates: Carried with mapping
  7. Intake: 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
ToRocket MatterCloud
  • 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 Rocket Matter

Each row is a kind of record Clio Grow holds, whether Rocket Matter 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 Rocket Matter
RecordIn Clio GrowIn Rocket MatterWhat 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 placeMatter File # and matter name are required on import.Carried across
ContactsClients, other parties and referrersHeldPerson and company contacts; synced with Clio Manage where both are used.Has a placeImported as clients or as other contact types.Carried across
DocumentsFiles stored in or linked from the systemHeld in partDocuments prepared from templates and sent for signature during intake.Has a placeNative storage, or a linked OneDrive, Dropbox, Box or NetDocuments account.Carried across
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partEmails can be filed to matters; it does not hold whole mailboxes.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeConfirmed in the analysis
CalendarAppointments, court dates and deadlinesHeld in partAppointments booked through Clio Scheduler or entered by hand, with reminders.Has a placeCarried 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 partOpen balances are supported; how much invoice history loads is confirmed in the analysis.Confirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldContact and matter custom fields, shared with Clio Manage.Has a placeCustom fields and custom pages on contacts and matters.Carried with mapping
TemplatesPrecedents, document templates and automationHeldDocument templates, including PDF templates with signature fields.Has a place in partWord merge templates are rebuilt with the product’s own 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 place in partIntake forms exist; loading open leads is confirmed in the analysis.Carried with mapping

What the plans mean

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

This describes loading into Rocket Matter NextGen, the platform the vendor’s website now presents. Its import runs in a fixed order: contacts, then matters, then time, expenses and balances. The vendor’s import sheets show what each record must carry. Most of the preparation is giving every matter a file number and getting the accounting set-up finished before any financial record goes in.

  1. A file number on every matter

    Matter File # and matter name are the two required fields. The file number is also the key that time, expenses and balances are matched to on the way in. Source matters with no number, or with numbers reused across clients, are given clean ones before the trial load and the old value is kept in a custom field.

  2. Clients and address-book contacts

    A contact is either a client, who can have matters, or an address-book contact such as an opposing lawyer or an expert. Source systems that hold everyone in one list need each record classified. A person who is a client on one matter and a witness on another is loaded once, as a client.

  3. Accounting set-up comes first

    Timekeepers, matter owners, bank accounts and the chart of accounts must exist before financial data is imported, and the client and matter records must already be in place. The trial load follows that order. Time recorded by people who have left still needs a timekeeper to belong to, so former staff are added before their entries are loaded.

  4. Pick the document store early

    Documents can sit in native storage or in a linked OneDrive, Dropbox, Box or NetDocuments account. With a linked account, the system creates a folder for each matter, named from the file number, client and matter name. Changing that pattern later only affects new matters, so it is settled before the load.

  5. One ledger of record

    NextGen has its own chart of accounts, journal entries and bank reconciliation, and it can also sync with QuickBooks Online from a chosen start date. A firm should run one of them as its books. That decision shapes how opening trust and debtor balances are entered, and the accountant is part of it.

More about moving into Rocket Matter

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 Rocket Matter, 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 Rocket Matter. 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 Rocket Matter 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 toRocket Matter

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 Rocket Matter. 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 Rocket Matter

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

Beyond the data, a firm starting on Rocket Matter has a set of choices that are awkward to change once people are billing. Who the timekeepers and matter owners are, how matters are numbered, which bank accounts exist and whether the books run inside the product or in QuickBooks Online all need an answer before go-live. Matter templates and Word merge documents are then built on top.

Set-up decisions in Rocket Matter

  • Timekeepers, matter owners and the rates each one bills at
  • Matter File number format and matter templates by work type
  • Bank accounts, chart of accounts and the QuickBooks Online decision
  • Custom fields and custom pages for contacts and matters
  • Document storage choice and the matter folder naming pattern
  • Word merge templates, invoice layouts and intake forms

Questions

Clio Grow to Rocket Matter: 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 Rocket Matter?

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 Rocket Matter are kept as reports and invoice copies.

Does everything in Clio Grow have a place in Rocket Matter?

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 Rocket Matter 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 Rocket Matter?

Custom fields, templates and intake records 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 Rocket Matter are the names and marks of their owners, used here only to identify the two systems.

Moving from Clio Grow to Rocket Matter?

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

We reply within one business day.