Data migration route
ProTempus to Clio Manage migration
ProTempus is a server-based practice management system, and Clio Manage is a cloud one. Both run a whole practice, so this is a full move, and the financial records set the timetable.
- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Emails: Carried across
- Calendar: Carried across
- Time and expenses: Carried with mapping
- Billing: Carried with mapping
- Trust money: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
Clio ManageCloud- Firm accounts: Kept as a readable archive
- Intake: Kept as a readable archive
- 5 carried
- 4 mapped
- 3 to confirm
- 2 archived
What moves
What moves from ProTempus to Clio Manage
Each row is a kind of record ProTempus holds, whether Clio Manage has a place for it, and what is planned. On this route five kinds of record carry across, four kinds need mapping, two kinds have no place in Clio Manage and are archived and three kinds are confirmed in the analysis.
| Record | In ProTempus | What is planned | |
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldCalled cases; a client can have several, each with its own rate and billing type. | Has a placeImported from a matters template, after contacts. | Carried across |
| ContactsClients, other parties and referrers | HeldClients and other parties, with a role on each case and user-defined contact types. | 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 partNot stored in the program: each client links to a network folder, with keyword indexes. | 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 partEmails are saved as files into the client’s document folder. | Has a placeHeld as communications on the matter, with phone logs. | Carried across |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeMatter notes and contact notes each have a template. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | HeldA calendar per timekeeper, with optional Outlook or Google sync. | 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 | HeldTime can be created from calendar events and phone calls. | 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 | HeldHourly, contingency, flat rate and unit billing; invoices can be split between parties. | 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 | HeldTrust accounting, with invoices payable from the client’s trust balance. | 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 | HeldReceivables, payables and general ledger, or an optional QuickBooks interface. | 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 | HeldBoilerplate forms filled from the database. | Has a placeRebuilt as Clio document templates with its merge fields. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | Held in partA client’s completed PDF intake form can be imported into the case file. | 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 ProTempus.
- 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 ProTempus 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
The whole practice moves, accounts included.
A move between two practice management systems is the widest kind there is. ProTempus and Clio Manage each keep matters, contacts, documents, time and money in one place, but no two systems link those records the same way. In one, a client is a contact with a role on the matter. In another, every matter carries its own client card. Most of the analysis goes into those links, because a matter that arrives without its client or its documents is the first thing staff find.
The financial side decides the dates. Unbilled time, debtor balances and trust ledgers have to agree with ProTempus’s own reports as at one day, and a new system usually wants them as opening balances, not as years of transactions. So the firm decides early how much history comes across as live records and how much is kept as reports. Matter and document loads can be repeated until they are right. The money is loaded once.
ProTempus 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 ProTempus
ProTempus keeps its database on the firm’s own network and never took the documents in, so both are close at hand. The detail to watch is how tightly billing is tied to everything else. Calendar entries become charges, cases under one client bill on different terms, and one invoice can be divided among several payers. Those arrangements need to survive the move.
Documents were never imported
The program does not hold documents. Each client is linked to a folder on the firm’s network, with subfolders for cases, and invoices are saved there as PDFs. The files are already ordinary files. What has to be carried is the link between each client or case and its folder, and any keyword index built on top.
The calendar bills
A calendar event or logged phone call can be turned into a billable item, and it then shows green. Time entries and calendar entries are therefore two views of the same work. Both are extracted, and the billed flag is checked so that an appointment already charged is not loaded as unbilled time.
Cases under a client
Each client can have several cases, and each case has its own rate and its own billing type: hourly, contingency, flat rate or unit. By default each case gets its own invoice. A destination that sets billing terms at client level needs those terms moved down to the matter, one case at a time.
Invoices split between payers
A case’s bill can be divided among any number of parties, each paying a share. The invoice history then shows several debtors for one piece of work. Open balances are loaded against the party who owes them, and the split percentages are recorded on the matter so future bills follow the same rule.
Books inside or QuickBooks
The firm either uses the embedded payables and general ledger or connects to QuickBooks, where each client’s trust money is a sub-account. Where QuickBooks is used, the program can audit its trust balances against those sub-accounts. That audit is run and cleared before extraction, so both sets of figures start out equal.
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 ProTempus 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 ProTempus, 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 ProTempus: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in ProTempus 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. ProTempus 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 ProTempus 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 ProTempus 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
ProTempus to Clio Manage: what firms ask
Our documents are in folders on the server. Do they move?
They can stay or move. ProTempus only points at those folders, so nothing has to be extracted from the program itself. If the new system stores documents, each client folder is loaded against the matching client and matter. The folder names are checked against the client list first, because renamed folders are the usual cause of orphans.
We enter every caller for conflict checks. Do they all come?
They should. A contact list that includes people who only ever phoned is what makes a conflict search worth running. They are loaded as contacts with no matter attached. The clean-up step looks for the same caller entered more than once, though not every duplicate can be found and some may carry across.
Can trust and operating balances be moved together?
Yes, and they are checked together. Each client’s trust balance is loaded as an opening balance and the total is matched to the bank. Unpaid invoices are loaded as debtors. The trust and financial cutover is rehearsed on a full trial load before the real one, because it cannot be run twice.
Do trust balances in ProTempus 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 and intake records. They are exported from ProTempus 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 ProTempus data is loaded into Clio Manage?
Time entries, billing records, trust ledgers and templates are carried with mapping, so each mapping is agreed with you first. Notes, tasks and custom fields 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 ProTempus and into Clio Manage
Other destinations from ProTempus
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.
ProTempus and Clio Manage are the names and marks of their owners, used here only to identify the two systems.
Moving from ProTempus 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.