Data migration route
Lead Docket to Clio Manage migration
Lead Docket is a cloud CRM and intake system, and Clio Manage is a cloud practice management system. Contacts and intake history move, and the matters themselves start life in Clio Manage.
Lead DocketCloud- Contacts: Carried across
- Documents: Carried across
- Emails: Carried across
- Notes: Carried across
- Tasks: Carried across
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Calendar: Confirmed in the analysis
- Trust money: Confirmed in the analysis
Clio ManageCloud- Intake: Kept as a readable archive
- 5 carried
- 3 mapped
- 2 to confirm
- 1 archived
What moves
What moves from Lead Docket to Clio Manage
Each row is a kind of record Lead Docket holds, whether Clio Manage has a place for it, and what is planned. On this route five kinds of record carry across, three kinds need mapping, one kind has no place in Clio Manage and is archived and two kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| ContactsClients, other parties and referrers | HeldLeads and referral partners. | Has a placePeople and companies, with related contacts linked to matters by a separate template. | Carried across |
| DocumentsFiles stored in or linked from the system | Held in partIntake documents and files attached to a lead. | Has a placeFiled under the matter; Clio scopes document migration separately from data. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partFollow-up emails and texts sent from the product are kept with the lead. | Has a placeHeld as communications on the matter, with phone logs. | Carried across |
| NotesFile notes, matter notes and contact notes | HeldNotes on each lead. | Has a placeMatter notes and contact notes each have a template. | Carried across |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a placeCalendar events have a migration template. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | HeldAutomated recurring tasks for each lead. | Has a placeTasks have a migration template. | Carried across |
| BillingInvoices, payments and debtor balances | Held in partPayment requests for consultation fees, retainers and referral fees. | Has a place in partAn outstanding balance loads as one line per matter; past invoices do not. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a place in partA trust balance loads as one line per matter or contact; past transactions do not. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldCustom intake forms with the firm’s own qualifying fields. | Has a placeCreated first, then filled from the custom field templates. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held in partAutomated follow-up messages and custom intake scripts. | Has a placeRebuilt as Clio document templates with its merge fields. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldThe whole product: leads, sources, statuses, referrals and conversion. | No placeLeads and intake forms belong in Clio Grow. | Kept as a readable archive |
What the plans mean
- Carried across
- Clio Manage has a place for this kind of record. It is loaded there and checked against Lead Docket.
- Carried with mapping
- Clio Manage 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
- Clio Manage has no place for it. It is exported in a format that opens without Lead Docket 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
Contacts and enquiries move. Matters begin in the new system.
A CRM knows people: who enquired, who referred them, what was sent and when. It does not know matters the way a practice system does. So the move from Lead Docket to Clio Manage is mostly a contacts job, and contacts are where duplicates live. The same person appears as a lead, a client and a referrer, sometimes under three email addresses. They are merged before extraction where they can be identified, because Clio Manage will invoice and receipt against these records.
Pipelines, campaigns and automations seldom have a direct equivalent in a practice system. Open enquiries can be loaded as contacts with a note of their stage, or opened as matters if the firm wants them worked from the first day. Intake forms and email sequences are set up again in whatever Clio Manage or its intake tool provides. Past correspondence is kept as notes or documents on the contact, so the history of a relationship can still be read.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Lead Docket 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 Lead Docket is kept running until the checks on Clio Manage are finished.
Where the data is now
Leaving Lead Docket
Moving off Lead Docket is a move of leads, not matters. The questions are how much history the firm wants, and where it goes. Signed leads already exist as cases elsewhere. What remains is the pipeline in progress, the declined and referred-out enquiries, and the marketing history that the firm’s spending decisions rest on.
Leads are not matters
A lead has a status, a source and intake answers, but no matter number or ledger. Loading every lead into a practice system as a matter fills it with enquiries that never became work. Open leads go to the destination’s intake module, and declined ones become contacts with a note or stay in an export.
Marketing source and spend
Each lead carries the source it came from, and the firm enters spend against its campaigns so the return can be reported. That history is only useful if the source names survive unchanged. The source list is tidied first, and the old reports are exported so last year’s figures can still be compared.
Referral fees still owed
Leads referred to other firms are tracked with their fees, and the product checks in with referral partners automatically. Some of those fees are still to come when the firm moves. Each open referral is listed with partner, client and expected fee, and loaded where someone will keep following it up.
Intake answers on custom forms
Intake scripts are custom to each firm, so the answers sit in fields the firm designed. For signed clients those answers will usually have been passed to the case system already. Answers on open leads are mapped to the new intake form question by question, with anything unmatched kept as a note.
Duplicates with the case system
A signed lead exists twice: once here and once as a client in the case management system. If both are loaded into one new system, every client appears twice. The two are matched on the link between them or on name and phone, and the case record is treated as the master.
Where it is going
Arriving in Clio Manage
Clio Manage is loaded through its migration templates, one spreadsheet per kind of record, imported in a fixed order with contacts first. Clio’s own migration guide is plain about the limit: balances come across, financial history does not. So a load into Clio is planned as records plus opening positions, with the old system kept for the history behind them.
Matters link by client name
The matters template ties each matter to its client by an exact match on first name, last name or company name. A client spelt two ways in the old system becomes two contacts, or a matter assigned to an unknown client. This is why contact clean-up is finished before the first trial load, not after it.
Decide the numbering scheme first
Clio numbers imported matters itself unless the account is set to manual numbering, in which case the old number is supplied in the template. That setting and the firm’s preferred scheme are decided before any matter is loaded. The Client Reference field is available for an old file number the firm still wants to see.
Balances, one line each
Under Clio’s standard migration, an outstanding balance arrives as one line per matter and a trust balance as one line per matter or contact. Past invoices, billed time, payments and trust transactions are listed as data that cannot be migrated. The trust total is reconciled against the old system’s closing report on the trial load.
Custom fields must exist
Matter and contact custom fields are created in Clio before their values are imported, each with a field type. Accounts set up for a particular practice area come with preconfigured fields and matter templates, which affects the mapping. We compare those with the old system’s fields and add only what is missing.
Rates and permissions by hand
Billable rates for users, clients and matters are not part of an import. Neither are user permissions or settings. They are entered in Clio during set-up from a schedule the firm confirms, and a sample of imported unbilled time is checked against that schedule before the trial load is signed off.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover.
Analysis
We read what Lead Docket holds and how its records link, then agree with you, field by field, where each piece will sit in Clio Manage. Anything with no place there comes across as a note or stays behind, and you see which before the move.
Clean-up
Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Lead Docket, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Clio Manage as a trial and checked against Lead Docket: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Lead Docket are frozen for an agreed window, the data is collected a final time and Clio Manage goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in Lead Docket as at the cutover date. Lead Docket 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 Lead Docket 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 Lead Docket holds
What is in it, how its records link, and where each piece would sit in Clio Manage. 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 Clio Manage
Loaded data is not yet a working system. This is what NewLaw sets up in Clio Manage, beyond the migration, so that people can work in it from the first day.
Much of a Clio Manage set-up is firm-wide settings. The numbering scheme, practice areas, matter stages, billing preferences and trust accounts apply to everyone, so they are agreed once and early. Trust and accounting features are not the same in every country Clio sells in, so the firm’s own region is checked first. Document templates and custom fields follow. Email and document integrations are then installed for each user and tested on a real matter.
Set-up decisions in Clio Manage
- Matter numbering scheme, practice areas and matter stages
- Custom fields for matters and contacts, by practice area
- Document templates with merge fields, uploaded from Word or PDF
- Billing settings, user and client rates, and trust accounts
- Roles and permissions for each user
- Outlook add-in, Clio Drive and the accounting connection
Questions
Lead Docket to Clio Manage: what firms ask
Should our declined leads move to the new system?
Often not as live records. Declined enquiries matter for conflict checks and for marketing numbers, and neither needs them cluttering the intake screen. One arrangement is to load the contact with a one-line reason and keep the full export on file. Firms with strict conflict rules load more.
We are leaving Filevine as well. Does Lead Docket have to go?
Not necessarily. Lead Docket connects to case management software other than Filevine, so it can stay if the new system is one it works with or can accept leads another way. If the destination has its own intake module, running one tool is simpler, and the open pipeline is moved across at the same cutover.
Can the marketing reports be recreated?
The figures can, if source and spend come across cleanly. Reports are rebuilt in the destination’s own reporting or in a spreadsheet fed from it. Historic periods are exported from Lead Docket before the move, because rebuilding several years of conversion history inside a new system is seldom needed.
Do trust balances in Lead Docket have a place in Clio Manage?
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 Lead Docket before the plan is fixed. If Clio Manage turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.
What happens to records Clio Manage has no place for?
On this route that is intake records. They are exported from Lead Docket 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 Lead Docket data is loaded into Clio Manage?
Billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Calendar entries and trust ledgers are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from Lead Docket and into Clio Manage
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.
Lead Docket and Clio Manage are the names and marks of their owners, used here only to identify the two systems.
Moving from Lead Docket to Clio Manage?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.