Data migration route
Clio Grow data to Full data export
Clio Grow is a cloud CRM and intake system, and Full data export is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what Clio Grow holds and keeps it readable and open to queries.
Clio GrowCloud- Matters: Exported in full
- Contacts: Exported in full
- Documents: Exported in full
- Calendar: Exported in full
- Custom fields: Exported with mapping
- Templates: Exported with mapping
- Intake: Exported with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Billing: Confirmed in the analysis
Full data exportFiles- 4 carried
- 3 mapped
- 4 to confirm
What moves
What moves from Clio Grow to Full data export
Each row is a kind of record Clio Grow holds, whether Full data export 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.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partProspective matters, called opportunities on newer screens, each with a pipeline status. | Has a placeA matters table keyed by the original matter number. | Exported in full |
| ContactsClients, other parties and referrers | HeldPerson and company contacts; synced with Clio Manage where both are used. | Has a placeA contacts table and a table of each contact’s role on each matter. | Exported in full |
| DocumentsFiles stored in or linked from the system | Held in partDocuments prepared from templates and sent for signature during intake. | Has a placeFiles under their original names, in client and matter folders. | Exported in full |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partFiled emails as message files in the matter’s folder, if the source exposes them. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeA notes table with matter, author and date for each note. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partAppointments booked through Clio Scheduler or entered by hand, with reminders. | Has a placeA table of appointments and key dates; nothing shows it as a diary. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a placeA table of tasks with assignee, due date and status. | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | To be confirmed | Has a placeInvoice, line and receipt tables; invoice PDFs can be kept beside them. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldContact and matter custom fields, shared with Clio Manage. | Has a placeExtra columns under their original field names. | Exported with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument templates, including PDF templates with signature fields. | Has a place in partTemplate files only; the merge fields in them will not run. | Exported with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldIntake form templates and a pipeline grouped as Intake, Hired and Not hired. | Has a place in partAn enquiries table, where the source tracked leads. | Exported with mapping |
What the plans mean
- Exported in full
- Full data export has a place for this kind of record. It is loaded there and checked against Clio Grow.
- Exported with mapping
- Full data export 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
Not a new system. A complete copy the firm can query.
Writing Clio Grow out to Full data export is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.
What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Clio Grow as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.
Clio Grow is hosted by its maker and Full data export sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What Clio Grow will release depends on its export tools, and that is confirmed in the analysis.
Where the data is now
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.
Where it is going
Arriving in Full data export
A full export is judged by whether a stranger can use it. In five years the question will be something like: what was the trust balance on this matter the day it closed, and where is the signed agreement. The export is planned backwards from questions of that kind, and it is checked against the live system while the live system can still be opened.
Tables that still join up
Each kind of record becomes its own table: matters, contacts, time entries, invoices, trust transactions. The identifiers that link them are kept in every table, so a time entry can still be traced to its matter and its fee earner. An export that keeps the rows and drops the keys cannot be rejoined later.
Documents with an index
Documents are written to folders by client and matter under their original names. On their own they can be found only by name. An index listing each file with its matter number, title, author, dates and path is what lets someone find the right version of a lease among forty thousand files without the old system’s search. What the index records is settled in the analysis.
Reports a person can read
Raw tables do not satisfy an auditor or a former client. The firm decides which reports are also printed to PDF from the old system as at the final date: trust ledgers, matter ledgers, debtor lists and issued invoices are the usual candidates. They cannot be regenerated once the licence ends.
What an export does not keep
Screens, workflows, document automation, saved searches and user permissions belong to the software and stay with it. Figures the system calculated on the fly, such as a matter’s unbilled total, exist in an export only if they were captured as a report. The firm is told which of these are being let go.
Checked while the source is open
Record counts and financial totals in the export are reconciled to the live system: number of matters, sum of trust balances, total debtors, document count per matter on a sample. This is done before the subscription lapses or the server is turned off, because afterwards there is nothing left to compare against.
How NewLaw runs it
Four steps, in this order.
This route produces an archive, not a working system, so the steps are about completeness and proof.
Analysis
We read what Clio Grow holds, table by table, and agree with you what the copy in Full data export must be able to answer later. Everything Clio Grow holds is in scope unless you take it out.
Clean-up, if you want it
An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.
Trial export
The data is written to Full data export as a trial and checked against Clio Grow: record counts, totals where Clio Grow holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.
Final export
After the last day of work in Clio Grow, the export is run a final time and checked again. There is nothing to go live. Clio Grow is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.
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
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 Full data export. 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.
Beyond the data
Structure, permissions and handover
Full data export is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.
With no product to configure, the set-up is custody, and the decisions are the firm’s. Someone there owns the export, knows where it is kept and can open it. Access needs restricting, because it contains every client’s affairs in one place with none of the old system’s security. The firm sets a destruction date from its retention obligations and decides how the next custodian will learn to use it.
What is agreed and set up
- Folder layout for tables, documents and reports
- What the key to tables, columns and identifiers records
- Where the copies are stored and who is custodian
- Who may open it, as approved by a partner
- Which look-ups staff must be able to do unaided
- Retention period and the date it is next reviewed
Questions
Clio Grow to Full data export: 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 the copy in Full data export hold billing records from Clio Grow?
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.
Does everything in Clio Grow have a place in Full data export?
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 Full data export is kept as a readable archive, and you see which before the move.
What has to be decided before Clio Grow is written out to Full data export?
Custom fields, templates and intake records are exported 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 who may open the archive and how long it is kept.
Other routes
Other routes from Clio Grow and into Full data export
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.
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 Full data export are the names and marks of their owners, used here only to identify the two systems.
Moving from Clio Grow to Full data export?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.