Data migration route
Clio Grow to Server drives migration
Clio Grow is a cloud CRM and intake system, and Server drives are plain files on equipment the firm controls. What moves is the files, plus a readable export of everything else the old system holds.
Clio GrowCloud- Documents: Carried across
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Billing: Confirmed in the analysis
Server drivesFiles- Matters: Kept as a readable archive
- Contacts: Kept as a readable archive
- Calendar: Kept as a readable archive
- Custom fields: Kept as a readable archive
- Intake: Kept as a readable archive
- 1 carried
- 1 mapped
- 4 to confirm
- 5 archived
What moves
What moves from Clio Grow to Server drives
Each row is a kind of record Clio Grow holds, whether Server drives have a place for it, and what is planned. On this route one kind of record carries across, one kind needs mapping, five kinds have no place in Server drives and are archived 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. | No placeA matter becomes a folder; its details survive only in an index file. | Kept as a readable archive |
| ContactsClients, other parties and referrers | HeldPerson and company contacts; synced with Clio Manage where both are used. | No placeCan be kept only as an exported spreadsheet. | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | Held in partDocuments prepared from templates and sent for signature during intake. | Has a placeFiles in folders, named and dated during the load. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partAs .msg or .eml files in each matter’s correspondence folder. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place in partAs a text or PDF file per matter, not as separate records. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | Held in partAppointments booked through Clio Scheduler or entered by hand, with reminders. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | No place | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | To be confirmed | Has a place in partInvoices as PDF files; no ledger. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldContact and matter custom fields, shared with Clio Manage. | No place | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | HeldDocument templates, including PDF templates with signature fields. | Has a place in partPrecedents as Word files; merge fields tied to the old system stop working. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldIntake form templates and a pipeline grouped as Intake, Hired and Not hired. | No place | Kept as a readable archive |
What the plans mean
- Carried across
- Server drives has a place for this kind of record. It is loaded there and checked against Clio Grow.
- Carried with mapping
- Server drives 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.
- Kept as a readable archive
- Server drives has no place for it. It is exported in a format that opens without Clio Grow 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
An export the firm can open without the system.
Server drives hold files, and most of what Clio Grow holds is records. This route is therefore an export job. Each kind of record is written out in a format that opens without the system it came from: lists as spreadsheets, statements and invoices as PDFs, attachments as the files they were. The export is laid out in folders that make sense to someone who never used Clio Grow, by client or by year, with a short index file saying what is where.
Firms do this when a subscription is ending, when a system is being retired, or to meet a retention rule. The test of the result is whether a question can still be answered from it years later: what was this client invoiced, who signed this agreement and when. So the trial export is checked by asking those questions of it. Totals are agreed to the system’s own reports, and access to the folder in Server drives is limited before the export is copied in.
Clio Grow is hosted by its maker and Server drives sit 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 Server drives
Some firms leave a practice or document system and keep their documents on a server drive, either as the working store or as the archive of a system being switched off. The files will arrive without the database that described them. Everything the firm wants to keep knowing about a document has to be put into its path, its name or an index file.
Agree the tree and the names
A fixed pattern is chosen, for example client name and number, then matter number and short description, then a standard set of subfolders. Document titles from the old system become file names. Where two documents share a title, a date or sequence number is added so nothing is overwritten.
Budget the path length
Share name, client, matter, subfolder and file name all count towards the 260 character limit that many Windows programs still apply. The pattern is tested against the firm’s longest client names and document titles before the load. Descriptions are trimmed by rule, never by cutting off the file extension.
Dates have to be set deliberately
A file written to the server today is dated today unless its modified date is set from the old system’s record. Document dates are how lawyers find things in a folder. Which date each file is to carry is agreed in the analysis, and the trial load checks a sample.
Emails become message files
Emails filed to matters in the old system are written out as .msg or .eml files in a correspondence folder, named by date, sender and subject so they sort in order. Attachments stay inside the message. Subjects with characters Windows forbids are cleaned, and long ones cut.
Keep an index beside the files
A spreadsheet or small database listing every document with its matter, author, original date, document type and new path is the only place the old system’s profile data survives. It lets someone find a document by something other than its name. What the index records, and who keeps it, is decided in the analysis.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Server drives on this route, 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 Server drives. 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 Server drives 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
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 Server drives. 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
Server drives are storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.
A server drive does only what the firm and its IT provider make it do. Setting one up as a document store means building the share, deciding who can open which folders, and arranging the protections a document system would have supplied: backups, earlier versions and a way to recover a deleted folder. The filing rule is written down and taught.
What is agreed and set up
- Share and top-level folders for clients, precedents and administration
- Security groups and folder permissions, with restricted matters separate
- Drive letter mapped for every user at sign-in
- Backup schedule and shadow copies for earlier versions
- Written naming rule for client, matter and document names
- Read-only area for closed matters and archived system exports
Questions
Clio Grow to Server drives: 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 Server drives?
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 Server drives are kept as reports and invoice copies.
What happens to records Server drives have no place for?
On this route that is matters, contacts, calendar entries, custom fields and intake records. They are exported from Clio Grow 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 Clio Grow data is loaded into Server drives?
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.
Other routes
Other routes from Clio Grow and into Server drives
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 Server drives are the names and marks of their owners, used here only to identify the two systems.
Moving from Clio Grow to Server drives?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.