Data migration route
Open Case Management (OCM) to Clio Manage migration
Open Case Management (OCM) is a server-based case management system for legal aid work, and Clio Manage is a cloud practice management system. Case records move into matters, and time, billing and trust are set up in Clio Manage, often from a separate accounts package.
- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Notes: Carried across
- Calendar: Carried across
- Tasks: Carried across
- Time and expenses: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Emails: Confirmed in the analysis
Clio ManageCloud- Intake: Kept as a readable archive
- 6 carried
- 3 mapped
- 1 to confirm
- 1 archived
What moves
What moves from Open Case Management (OCM) to Clio Manage
Each row is a kind of record Open Case Management (OCM) holds, whether Clio Manage has a place for it, and what is planned. On this route six kinds of record carry across, three kinds need mapping, one kind has no place in Clio Manage and is archived and one kind is confirmed in the analysis.
| Record | In Open Case Management (OCM) | What is planned | |
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldCases, each started from an intake. | Has a placeImported from a matters template, after contacts. | Carried across |
| ContactsClients, other parties and referrers | HeldClients, adverse parties and contacts on every case, with duplicate merging. | 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 | HeldUploaded files indexed for search, including PDFs and WordPerfect documents. | Has a placeFiled under the matter; Clio scopes document migration separately from data. | Carried across |
| 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 | Has a placeMatter notes and contact notes each have a template. | Carried across |
| CalendarAppointments, court dates and deadlines | HeldShared calendars with iCal feeds. | Has a placeCalendar events have a migration template. | Carried across |
| TasksTo-dos and workflow steps assigned to people | HeldTicklers. | Has a placeTasks have a migration template. | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTimeslips on every case. | Has a place in partUnbilled time entries load; billed time entries do not, by Clio’s migration guide. | Carried with mapping |
| Custom fieldsFields and record types the firm added itself | HeldCustom fields, HTML fields and editable menus. | Has a placeCreated first, then filled from the custom field templates. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldForm letters and generated documents using configurable template tags. | Has a placeRebuilt as Clio document templates with its merge fields. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldIntake with financial and citizenship eligibility, conflict and duplicate checks. | 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 Open Case Management (OCM).
- 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 Open Case Management (OCM) 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
Cases come across. The accounts are set up new.
A case management system holds the working file: parties, notes, deadlines, documents and the fields a practice area needs. It is not usually the firm’s ledger, so time, invoices and trust often sit in an accounting package beside it. Moving to Clio Manage brings those two sources together. The case records come from Open Case Management (OCM). Opening balances for debtors and trust, where they move at all, come from the accounts package and are agreed to its reports.
Case systems are heavy with custom fields, and that is where the mapping work is. A personal injury or immigration file can carry dozens of fields that a general practice system has no standard place for. Each one is matched to a field in Clio Manage, created there as a custom field, or written into a note on the matter. The firm sees which before the load. Workflows and task templates are rebuilt, not copied.
Open Case Management (OCM) 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 Open Case Management (OCM)
Where OCM is self-hosted, the database and the uploaded files are on a server the program or its host controls. That makes collection simple and makes the mapping the real work. The records were designed for legal aid reporting: intakes that may never become cases, eligibility answers, timeslips and the codes that funders count. Each needs a place or a decision.
Intakes that never became cases
An intake is started, screened for financial and citizenship eligibility, checked for conflicts and duplicates, then reviewed and assigned. Many stop before a case is opened. Those records still matter, because a person turned away last year is a conflict check hit this year. They are loaded as contacts with a note, or as closed enquiries.
WordPerfect files in the store
Uploaded documents are indexed for search, and the project documents support for WordPerfect files as well as PDFs. Programs that have run for decades often have both. Files move in their original format. Whether the new system can preview or search a WordPerfect document is tested in the trial load, not assumed.
Menus the program edited
Menus, custom fields and HTML fields can all be changed by the program, so the values on a case come from lists that are local to that site. Every list is exported with its codes and labels. Retired values that still appear on old cases are kept, since deleting them would blank the field on those records.
MegaReport queries
Staff build their own ad hoc reports with a tool called MegaReport, alongside the built-in reports and LSC case service reporting. Saved queries are not data and do not migrate. The ones still used are listed, and each is either rebuilt in the new system or replaced by an export the program can run itself.
Peer transfers between programs
Cases can be transferred to a peer program running the same software. A transferred case has a history that began somewhere else. These are identified in the analysis so that the originating program, the transfer date and any documents that arrived with the case are preserved on the record.
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 Open Case Management (OCM) 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 Open Case Management (OCM), 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 Open Case Management (OCM): record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Open Case Management (OCM) 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 Open Case Management (OCM) as at the cutover date. Open Case Management (OCM) 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 Open Case Management (OCM) 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 Open Case Management (OCM) 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
Open Case Management (OCM) to Clio Manage: what firms ask
We run OCM on our own server. Does that make moving easier?
It makes getting the data out easier, because the database and the uploaded files are under the program’s control and can be copied in full. It does not shorten the mapping or the checking. A complete copy is taken for the trial load, and a second one at cutover after changes are frozen.
We are told OCM has been renamed. Does that force a move?
No one has to move because of a name. The open-source code is still published and receives security and bug fixes, and the commercial version continues as Ciprocity. Whether and when to move is the program’s own decision. If a move is planned, the installed version is identified first.
What happens to closed cases and old intakes?
Both are normally brought across. Legal aid programs rely on old records for conflict checks and funder audits, so leaving them behind saves little. If volume is a concern, the names and case numbers are loaded for every record and the full detail only from a chosen year onwards, with the remainder kept read only.
Do documents from Open Case Management (OCM) keep their folders and dates in Clio Manage?
Clio Manage stores documents. Filed under the matter; Clio scopes document migration separately from data. Each file is placed under the client and matter it came from, and created and modified dates are carried, so a document still shows when it was written. The trial load is checked by count and by opening a sample.
What happens to records Clio Manage has no place for?
On this route that is intake records. They are exported from Open Case Management (OCM) 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 Open Case Management (OCM) data is loaded into Clio Manage?
Time entries, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Emails 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 Open Case Management (OCM) 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.
Open Case Management (OCM) and Clio Manage are the names and marks of their owners, used here only to identify the two systems.
Moving from Open Case Management (OCM) 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.