Moving off a system
Migrating from Clio Grow
Client intake and lead tracking for law firms, with online intake forms, a status pipeline, appointment booking and documents sent for e-signature. This page sets out what Clio Grow holds, what moving off it involves and where its records can go.
Where it can go
Routes from Clio Grow
Each route has a page of its own: what moves, what has no place in the destination and how the move is run.
Practice management systems
Actionstep7 of 11 kinds of record have a place
Centerbase7 of 11 kinds of record have a place
Clio Manage6 of 11 kinds of record have a place
MyCase7 of 11 kinds of record have a place
Rocket Matter7 of 11 kinds of record have a place
SimpleLaw7 of 11 kinds of record have a place
Smokeball7 of 11 kinds of record have a place
SurePoint Finance Enterprise3 of 11 kinds of record have a place
Case management systems
Document management systems
Accounting and billing systems
CRM and intake systems
File storage
Box3 of 11 kinds of record have a place
Dropbox2 of 11 kinds of record have a place
Google Drive2 of 11 kinds of record have a place
OneDrive2 of 11 kinds of record have a place
Server drives2 of 11 kinds of record have a place
SharePoint6 of 11 kinds of record have a place
Sync.com2 of 11 kinds of record have a place
What it holds
The records Clio Grow keeps
Fourteen kinds of record matter to a move. Clio Grow keeps seven of them, three in part, and four could not be confirmed from its maker’s own material.
- MattersIn partProspective matters, called opportunities on newer screens, each with a pipeline status.
- ContactsYesPerson and company contacts; synced with Clio Manage where both are used.
- DocumentsIn partDocuments prepared from templates and sent for signature during intake.
- EmailsTo be confirmedEmails saved to matters or to the store
- NotesTo be confirmedFile notes, matter notes and contact notes
- CalendarIn partAppointments booked through Clio Scheduler or entered by hand, with reminders.
- TasksTo be confirmedTo-dos and workflow steps assigned to people
- Time and expensesNoTime and expense entries, billed and unbilled
- BillingTo be confirmedInvoices, payments and debtor balances
- Trust moneyNoTrust or client account ledgers and balances
- Firm accountsNoGeneral ledger, office account and payables
- Custom fieldsYesContact and matter custom fields, shared with Clio Manage.
- TemplatesYesDocument templates, including PDF templates with signature fields.
- IntakeYesIntake form templates and a pipeline grouped as Intake, Hired and Not hired.
Moving off it
Leaving Clio Grow
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.
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.
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.
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.
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.
The system
What Clio Grow is
Clio Grow is Clio’s intake and client relationship product. A firm uses it to keep track of people who have enquired but not yet signed: taking their details through online forms, booking consultations and sending engagement documents for signature. It is sold alongside Clio Manage and is designed to work with it.
It runs in a browser at its own address, separate from Clio Manage. Grow holds contacts and prospective matters, which its newer screens call opportunities. Each one sits in a pipeline under Intake, Hired or Not hired. When a client signs, the matter is converted into Clio Manage, and from then on the two products keep its main details in sync.
- Kind
- CRM and intake
- Runs as
- Cloud, hosted by its maker
- Made by
- Clio (Themis Solutions)
- Mainly used in
- The United States, Canada, the United Kingdom and Australia
- Also known as
- Lexicata
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in the new system on most routes, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what Clio Grow holds and how it is organised, then agree with you where each kind of record will sit in the new system. Anything with no place there stays behind or is archived, and you see which before the move.
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.
Trial load
A trial is loaded into the new system 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.
Cutover
There is no financial cutover on this route. After a short freeze on changes in Clio Grow, a final pass over a weekend picks up what changed since the trial. 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
Choose where the Clio Grow data is going, or tell us you have not decided. The first step is the analysis, and the price is fixed once it is done.
Step 1 of 5
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what Clio Grow holds
What is in it, how its records link, and where each piece would sit in the new system. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- A fixed price in writing
Set after the analysis, so it reflects what is in your data. You have it before any work starts.
After the move
Setting up the system you move to
A migration ends with data in a new system. Whether people can work in it on the first day depends on how that system was set up: matter types, templates, billing, permissions. NewLaw does that work as well, and each destination’s page says what its set-up involves.
Set-up, by destination
- Actionstep
- Box
- Centerbase
- Clio Manage
- Dropbox
- Filevine
- Full data export
- Gladiate
- Google Drive
- iManage Cloud
- Lawmatics
- LexWorkplace
- Litify
- Microsoft SQL Server
- MyCase
- Neos
- NetDocuments
- OneDrive
- QuickBooks Online
- Rocket Matter
- Server drives
- SharePoint
- SimpleLaw
- SmartAdvocate
- Smokeball
- Soluno
- SQLite
- SurePoint Finance Enterprise
- Sync.com
Questions
Moving off Clio Grow: 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.
Where to start
Still deciding where to move?
Choose the system before you plan the move, and see where AI fits once your data is in it.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
Clio Grow and the other product names and logos on this page belong to their owners and are used only to identify the systems.
Moving off Clio Grow?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.