Data migration route
Juris to Clio Manage migration
Juris is a server-based accounting and billing system, and Clio Manage is a cloud practice management system. The financial records lead: balances and open items move, and the matters in Clio Manage are built around them.
- Matters: Carried across
- Contacts: Carried across
- Notes: Carried across
- Calendar: Carried across
- Time and expenses: Carried with mapping
- Billing: Carried with mapping
- Trust money: Carried with mapping
- Documents: Confirmed in the analysis
- Emails: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
Clio ManageCloud- Firm accounts: Kept as a readable archive
- 4 carried
- 3 mapped
- 5 to confirm
- 1 archived
What moves
What moves from Juris to Clio Manage
Each row is a kind of record Juris holds, whether Clio Manage has a place for it, and what is planned. On this route four kinds of record carry across, three kinds need mapping, one kind has no place in Clio Manage and is archived and five kinds are confirmed in the analysis.
| Record | In Juris | What is planned | |
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldClients and matters as financial records, coded by lawyer, practice class and office. | Has a placeImported from a matters template, after contacts. | Carried across |
| ContactsClients, other parties and referrers | Held in partClients, vendors and names typed on note cards. | 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 | To be confirmed | Has a placeFiled under the matter; Clio scopes document migration separately from data. | Confirmed in the analysis |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a placeHeld as communications on the matter, with phone logs. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | Held in partNote cards at client or matter level. | Has a placeMatter notes and contact notes each have a template. | Carried across |
| CalendarAppointments, court dates and deadlines | Held in partThe vendor’s site lists a Juris Calendar beside the main product. | Has a placeCalendar events have a migration template. | Carried across |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a placeTasks have a migration template. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldEntered in Juris, Juris Suite or the Juris Go mobile app. | Has a place in partUnbilled time entries load; billed time entries do not, by Clio’s migration guide. | Carried with mapping |
| BillingInvoices, payments and debtor balances | HeldIncludes electronic billing. | 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 | Held | Has a place in partA trust balance loads as one line per matter or contact; past transactions do not. | Carried with mapping |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral ledger with multi-level sub-accounts, payables and cheque reconciliation. | No placeNot in Clio Manage. Books sit in a linked accounting package, or in Clio Accounting where Clio offers it. | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeCreated first, then filled from the custom field templates. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | To be confirmed | Has a placeRebuilt as Clio document templates with its merge fields. | Confirmed in the analysis |
What the plans mean
- Carried across
- Clio Manage has a place for this kind of record. It is loaded there and checked against Juris.
- 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 Juris 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
Time, bills and balances move. How much history is a decision.
Coming from an accounting or billing system, the records that count are balances: unbilled time, unpaid invoices, client funds, the ledger. A practice management system takes these as opening positions on a matter. So every client and job in Juris needs a matter to land on, and the first piece of work is building that matter list, often from client and project codes that were never meant to be matter numbers.
How much history to bring is the main choice. Paid invoices from years ago can be loaded as records, kept as PDF copies on the matter, or left in a read-only copy of Juris. Most firms bring open items and a period of history, and keep the rest as reports. Opening balances in Clio Manage are agreed to the trial balance and aged debtors from Juris as at the cutover date, and that load is rehearsed before it is done for real.
Juris runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. Clio Manage is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.
Where the data is now
Leaving Juris
Juris holds the firm’s financial history and little else, so a move off it is mostly about money and the codes that classify it. Work in progress, receivables, trust, payables and the ledger are each agreed to a Juris report. Matter documents and calendars usually live in another product beside it, and that product is brought into the same plan.
Three kinds of charge
Juris separates fees, cash expenses and non-cash expenses, and supports accrual, billed and cash accounting methods. Many destinations know only time and disbursements. The mapping has to say where non-cash expenses go, or unbilled and billed cost totals will not agree after the load.
Codes carry the reporting
Billing lawyer, originating lawyer, working timekeeper, practice class, office and billing agreement are all coded on the matter. Partner reports are built on them. Each code table is extracted and mapped, and codes that have drifted into near-duplicates are tidied in Juris before extraction.
Note cards feed conflict searches
Clients and matters can have note cards with other names and special information, and the conflict search reads them. They are where related parties were typed when there was no better field. Note cards come across as notes, and names inside them are flagged in case the firm wants them as contacts.
Juris Suite is a second layer
Firms with Juris Suite enter time, run collections and keep budgets through it. Budgets and collection notes are extra records worth asking about. They are listed in the analysis so nobody finds after go-live that the collections history was never in scope.
Sub-accounts in the chart
The chart of accounts can be split into multi-level sub-accounts to match how the firm is organised. A destination with a flat chart needs those collapsed or turned into tracking categories. The firm’s accountant agrees the new chart first, and the closing trial balance is restated into it before loading.
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.
Trust money moves on this route, so the trust cutover gets a rehearsal of its own.
Analysis
We read what Juris 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 Juris, 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 Juris: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Juris are frozen for an agreed window, the data is collected a final time and Clio Manage goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. Juris 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 Juris 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 Juris 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
Juris to Clio Manage: what firms ask
Can we keep our client and matter codes?
Juris codes are carried over wherever the destination allows a firm-set number, with the same padding and separators so old bills still match. If the new system numbers matters itself, the Juris code is stored as a reference and printed on invoices where clients expect to see it.
How much billing history should we bring?
Enough to answer a client’s question about a bill and to run aged debtors properly. Open invoices are loaded with their original dates. Paid invoices from earlier years can be loaded as summaries or left in Juris, kept read only. The destination’s limits usually decide it.
Our e-billing clients have strict formats. What happens?
The task codes, timekeeper classifications and client rates behind your e-bills are extracted and rebuilt in the new system. Past submissions stay where they are. Before go-live one real invoice for each e-billing client is produced from the trial load and checked against that client’s rules.
Do trust balances in Juris have a place in Clio Manage?
In part. A trust balance loads as one line per matter or contact; past transactions do not. The analysis sets out which trust records have a place in Clio Manage and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.
What happens to records Clio Manage has no place for?
On this route that is the firm’s accounts. They are exported from Juris 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 Juris data is loaded into Clio Manage?
Time entries, billing records and trust ledgers are carried with mapping, so each mapping is agreed with you first. Documents, emails, tasks, custom fields and templates 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 Juris and into Clio Manage
Other destinations from Juris
Other systems that move 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.
Juris and Clio Manage are the names and marks of their owners, used here only to identify the two systems.
Moving from Juris 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.