Data migration route
Clio Grow to LexWorkplace migration
Clio Grow is a cloud CRM and intake system, and LexWorkplace is a cloud document management system. Only files and their details have a place there, so this route carries the documents and archives the rest.
Clio GrowCloud- Documents: Carried across
- Matters: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Billing: Confirmed in the analysis
LexWorkplaceCloud- Contacts: Kept as a readable archive
- Calendar: Kept as a readable archive
- Intake: Kept as a readable archive
- 1 carried
- 3 mapped
- 4 to confirm
- 3 archived
What moves
What moves from Clio Grow to LexWorkplace
Each row is a kind of record Clio Grow holds, whether LexWorkplace has a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping, three kinds have no place in LexWorkplace 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. | Has a place in partName, custom ID, client, type, location, staff, tags and dates. No parties or financial fields. | Carried with mapping |
| ContactsClients, other parties and referrers | HeldPerson and company contacts; synced with Clio Manage where both are used. | No placeOnly a client name, status, attorneys and tags. | 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 placeFiled to a matter or to Firm Documents, in folders. | Carried across |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a placeOn the matter’s Email tab, in their own folders. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeAs Matter Notes on the matter’s Notes tab. | 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 | To be confirmed | Confirmed in the analysis |
| BillingInvoices, payments and debtor balances | To be confirmed | No place | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldContact and matter custom fields, shared with Clio Manage. | Has a place in partOld categories can become document types, statuses or tags. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument templates, including PDF templates with signature fields. | Has a place in partStored as files in Firm Documents. | 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
- LexWorkplace has a place for this kind of record. It is loaded there and checked against Clio Grow.
- Carried with mapping
- LexWorkplace 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
- LexWorkplace 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
Only the documents have a place here.
LexWorkplace is a document management system: it takes files and the details that describe them. Most of what Clio Grow holds is not files. Entries, balances, settings and lists have no place in a document store, and the table above is short for that reason. What can move is any document Clio Grow produced or stored: invoices as PDFs, signed agreements, attachments, exported reports. Each is filed under the client or matter it relates to.
The useful version of this job is often an archive. A firm retiring a system wants its records readable later without keeping the subscription or the old PC. The data is exported in open formats, spreadsheets and PDFs, and filed in LexWorkplace in a workspace set aside for it, with access limited to the people who need it. That gives the firm one place to look, under the same retention rules as the rest of its documents.
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 LexWorkplace are finished.
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 LexWorkplace
LexWorkplace expects every document and email to belong to a matter, so loading it starts with the matter list: name, custom ID, client, type and dates. Uptime Legal states that it runs migration and onboarding for its customers itself. The preparation is getting the old system’s content into a clean client and matter structure, with the exceptions resolved, ready for that load.
Matters carry little, by design
A matter record holds a name, a custom ID, a client, a type, a location, assigned staff, tags and open and close dates. Parties, court details and financial data have no fields. Those stay in the practice management system, and the two are tied together by using the same matter number as the custom ID.
Clients are only containers
LexWorkplace says plainly that its clients are for grouping matters, not for client management. A client has a name, a status, primary attorneys and tags. Addresses, phone numbers and contact history from the old system are not loaded here. They go to the practice management system or stay behind.
Three tabs per matter
Content arrives as documents, emails or notes, each on its own tab with its own folders. Emails held as message files in an old folder tree have to be recognised and loaded as emails, not as documents, or they will not appear where lawyers look for correspondence.
Closed matters and archive
A matter is closed by giving it a close date, and closed matters can be moved to archive storage, where they keep their place but are not searched or indexed until un-archived. Old matters can therefore be loaded and archived straight away. The firm sets the cut-off year.
Profiling is optional unless enforced
Document type, status and tags are not required by default, though a firm can switch on mandatory profiling for matters. If the old system had document types, they are mapped to LexWorkplace types during the load. If it had none, the firm chooses between loading unprofiled and assigning types by folder name.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in LexWorkplace on this route, which makes it repeatable: a load can be run again until it is right. The maker of LexWorkplace says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in Clio Grow and checking each trial against Clio Grow.
Analysis
We read what Clio Grow holds and how it is organised, then agree with you where each kind of record will sit in LexWorkplace. 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 LexWorkplace 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 LexWorkplace. 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
Setting up LexWorkplace
Loaded data is not yet a working system. The maker of LexWorkplace runs or arranges the set-up of its product, so this is what has to be decided and put in place in LexWorkplace, whoever does the work, before people rely on it from the first day.
Setting LexWorkplace up for a firm is a short list of decisions made in its settings, plus software on each computer. The decisions are what the firm calls its matter types, document types and statuses, who can open which matters by default, and whether versioning is automatic or manual. The Launcher and the Outlook add-in are then installed for every user.
Set-up decisions in LexWorkplace
- Matter types, document types, statuses and tag conventions
- Groups, rights and default permissions for new matters
- Automatic or manual versioning, and whether profiling is mandatory
- Linking matters to Clio Manage where the firm uses it
- Launcher, Office and Outlook add-ins on each Windows or Mac computer
- A Firm Documents structure for templates, policies and internal files
Questions
Clio Grow to LexWorkplace: 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 LexWorkplace?
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 LexWorkplace are kept as reports and invoice copies.
What happens to records LexWorkplace has no place for?
On this route that is contacts, calendar entries 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 LexWorkplace?
Matters, 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.
Other routes
Other routes from Clio Grow and into LexWorkplace
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 LexWorkplace are the names and marks of their owners, used here only to identify the two systems.
Moving from Clio Grow to LexWorkplace?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.