Data migration route
Clio Manage data to Full data export
Clio Manage is a cloud practice management 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 Manage holds and keeps it readable and open to queries.
Clio ManageCloud- Matters: Exported in full
- Contacts: Exported in full
- Documents: Exported in full
- Notes: Exported in full
- Calendar: Exported in full
- Tasks: Exported in full
- Time and expenses: Exported in full
- Billing: Exported in full
- Trust money: Exported in full
- Emails: Exported with mapping
- Firm accounts: Exported with mapping
- Custom fields: Exported with mapping
- Templates: Exported with mapping
- Intake: Exported with mapping
Full data exportFiles- 9 carried
- 5 mapped
What moves
What moves from Clio Manage to Full data export
Each row is a kind of record Clio Manage holds, whether Full data export has a place for it, and what is planned. On this route nine kinds of record carry across and five kinds need mapping.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldOpen, Pending or Closed, with a display number built from a firm-wide numbering scheme. | Has a placeA matters table keyed by the original matter number. | Exported in full |
| ContactsClients, other parties and referrers | HeldPerson and company contacts; related contacts link other parties to a matter. | 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 | HeldStored under contacts and matters in folders, with version history. | Has a placeFiles under their original names, in client and matter folders. | Exported in full |
| EmailsEmails saved to matters or to the store | HeldFiled from Outlook as email logs, or forwarded to a matter and stored as EML files. | Has a place in partFiled emails as message files in the matter’s folder, if the source exposes them. | Exported with mapping |
| NotesFile notes, matter notes and contact notes | HeldMatter notes and contact notes. | Has a placeA notes table with matter, author and date for each note. | Exported in full |
| CalendarAppointments, court dates and deadlines | Held | 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 | Held | Has a placeA table of tasks with assignee, due date and status. | Exported in full |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime entries and expense entries are both called activities. | Has a placeA time entries table with fee earner, matter, units, rate and billed status. | Exported in full |
| BillingInvoices, payments and debtor balances | HeldBills move from draft through approval to unpaid and paid. | Has a placeInvoice, line and receipt tables; invoice PDFs can be kept beside them. | Exported in full |
| Trust moneyTrust or client account ledgers and balances | HeldTrust funds can be held at client level or matter level. | Has a placeA trust transactions table; ledger reports can be kept as PDF beside it. | Exported in full |
| Firm accountsGeneral ledger, office account and payables | Held in partClio Accounting is a separate Clio product, documented for the US and Canada. | Has a place in partJournals and account balances, where the source held a general ledger. | Exported with mapping |
| Custom fieldsFields and record types the firm added itself | HeldMatter and contact custom fields, shared with Clio Grow. | Has a placeExtra columns under their original field names. | Exported with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument templates with merge fields, made from Word, Excel, PowerPoint and PDF files. | Has a place in partTemplate files only; the merge fields in them will not run. | Exported with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partLead pipeline and intake forms are in Clio Grow, a companion product. | 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 Manage.
- 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.
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 Manage 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 Manage 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 Manage 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 Manage will release depends on its export tools, and that is confirmed in the analysis.
Where the data is now
Leaving Clio Manage
Leaving Clio Manage is mostly a question of what comes out and in what form. Clio’s export page produces spreadsheets of contacts, matters, notes, tasks, calendar entries and time, and balances come from reports. Documents and billing history are not in those spreadsheets, so they are collected separately and joined back to the right matters.
The display number can change
A matter’s display number is built from a firm-wide scheme: matter number, client name, year and other parts in a chosen order. An administrator can change the scheme and apply it to every existing matter. The number in the export may therefore differ from the one on older letters. We check the Client Reference field as well.
Trust held at client level
Clio lets a firm hold trust funds against the client as a whole, not only against a matter. Many trust ledgers elsewhere are strictly per matter. Each client-level balance then has to be allocated to a matter before cutover, and the accounts team makes that allocation in Clio so the closing report already shows it.
Activities and communications
Time entries and expense entries are both called activities and export as separate lists. Filed emails and phone logs are communications. An email forwarded to a matter’s Maildrop address is stored as an EML file, while one filed from Outlook is an email log. The analysis counts each kind, since they land in different places.
Documents may sit outside Clio
Files can be stored in Clio itself or in a connected service. With the OneDrive for Business integration, for example, Clio creates a root folder with a subfolder for every client and matter. Before planning the document move we establish which store each office has been saving to, and whether both hold files.
Draft bills at cutover
A bill in Clio is a draft, pending approval, unpaid or paid, and a draft does not yet count towards the client’s balance. Before the final collection the accounts team approves or discards every draft. The debtor figure taken across is then the one on Clio’s accounts receivable report, with no half-finished bills behind it.
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 Manage holds, table by table, and agree with you what the copy in Full data export must be able to answer later. Everything Clio Manage 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 Manage: record counts, totals where Clio Manage 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 Manage, the export is run a final time and checked again. There is nothing to go live. Clio Manage 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 Manage 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 Manage 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 Manage to Full data export: what firms ask
Can our matter numbers stay the same when we leave Clio?
The destination decides. If it accepts a supplied matter number, the Clio display number is loaded as it stands. Because Clio’s scheme can include the client’s name, some firms take the chance to shorten it. Where the new system insists on its own numbering, the Clio number is kept in a reference field.
Does our billing history come out of Clio?
Time and expense entries export as lists, and outstanding balances come from the accounts receivable report. Whether the new system can hold past invoices as invoices depends on that system. Where it cannot, we agree with the firm how the history is kept: as PDF copies on each matter, or in the archived Clio data.
We also use Clio Grow. Is that a separate job?
It is a separate product with its own data, so it is scoped separately. Matters already converted from Grow exist in Clio Manage and move with it. What remains in Grow is the pipeline: leads not yet hired, intake forms and signed engagement documents. The analysis shows how much of that the firm still needs.
Does the copy in Full data export hold trust ledgers from Clio Manage?
Yes. A trust transactions table; ledger reports can be kept as PDF beside it. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in Clio Manage as at the export date.
Does everything in Clio Manage have a place in Full data export?
On paper, yes: each kind of record Clio Manage holds has a place in Full data export. Whether every field fits is a separate question, and the analysis answers it field by field. Anything with no place comes across as a note or stays behind, and you see which before the move.
What has to be decided before Clio Manage is written out to Full data export?
Emails, the firm’s accounts, custom fields, templates and intake records are exported with mapping, so each mapping is agreed with you first. The firm also decides who may open the archive and how long it is kept.
Other routes
Other routes from Clio Manage and into Full data export
Other destinations from Clio Manage
Other systems that move 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 Manage and Full data export are the names and marks of their owners, used here only to identify the two systems.
Moving from Clio Manage 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.