Data migration route
Access Legal Proclaim to Clio Manage migration
Access Legal Proclaim 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.
Access Legal ProclaimServer- Matters: Carried across
- Documents: Carried across
- Emails: Carried across
- Tasks: Carried across
- Time and expenses: Carried with mapping
- Billing: Carried with mapping
- Trust money: Carried with mapping
- Templates: Carried with mapping
- Contacts: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Calendar: 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
- 4 carried
- 4 mapped
- 4 to confirm
- 2 archived
What moves
What moves from Access Legal Proclaim to Clio Manage
Each row is a kind of record Access Legal Proclaim holds, whether Clio Manage has a place for it, and what is planned. On this route four kinds of record carry across, four kinds need mapping, two kinds have no place in Clio Manage and are archived and four kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldCalled cases; several users can work in one case at the same time. | Has a placeImported from a matters template, after contacts. | Carried across |
| ContactsClients, other parties and referrers | To be confirmed | Has a placePeople and companies, with related contacts linked to matters by a separate template. | Confirmed in the analysis |
| DocumentsFiles stored in or linked from the system | HeldDocuments are produced and stored on the case, with bundles. | Has a placeFiled under the matter; Clio scopes document migration separately from data. | Carried across |
| EmailsEmails saved to matters or to the store | HeldEmails are linked to cases. | 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 | To be confirmed | Has a placeCalendar events have a migration template. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | HeldTasks are generated by workflows. | Has a placeTasks have a migration template. | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime is recorded against budgets. | 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 | HeldBills and court forms are prepared from recorded time. | 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 in partThrough the optional legal accounts module. | 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 | Held in partOnly where the firm has taken the legal accounts module. | 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 | HeldLetters and documents selected and adapted by workflow. | Has a placeRebuilt as Clio document templates with its merge fields. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldAn Opportunities module with online quotes. | 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 Access Legal Proclaim.
- 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 Access Legal Proclaim 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. Access Legal Proclaim 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 Access Legal Proclaim’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.
Access Legal Proclaim 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 Access Legal Proclaim
Every Proclaim system is its own build. The workflows decide what a case looks like, the modules installed decide what data exists, and firms have often had both changed over many years. A move starts by reading that set-up. It also has to establish whether the firm’s accounts are in Proclaim’s accounts module or in a separate package.
The workflow is the system
In Proclaim the workflow chooses the letter, adapts it and attaches the right documents. Staff may never have picked a template by hand. None of that logic transfers. Each work type’s workflow is written out during the analysis, and the firm decides which steps to rebuild in the destination and which to retire.
Modules differ firm to firm
Accounts, compliance and practice-area features are each taken as separate modules, so two Proclaim firms can hold quite different data. The analysis lists the modules installed and what each one stores. If accounts are not in Proclaim, the client ledger comes from another system and the two sources have to be matched on case reference.
Different facts per work type
Workflows are supplied for each area of law, and the facts recorded on a personal injury claim are not those on a conveyance. The extract is taken work type by work type. Fields are mapped to the new system’s custom fields where they exist, and brought across as a note where they do not.
A hosted desktop
Access delivers Proclaim through a hosted desktop run by its managed services team. The database and documents sit in that environment, not in the firm’s office, so the copy is requested from Access. A firm that runs Proclaim on its own infrastructure supplies it directly. Both routes are checked the same way.
Claims work at volume
Proclaim is used for claims management, where one fee earner carries many cases and the system generates most of the correspondence. Volume changes the document plan. The firm decides early whether every generated letter moves, or only those on open cases and recent closed ones, with the rest retrievable from the archive.
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 Access Legal Proclaim 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 Access Legal Proclaim, 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 Access Legal Proclaim: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Access Legal Proclaim 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. Access Legal Proclaim 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 Access Legal Proclaim 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 Access Legal Proclaim 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
Access Legal Proclaim to Clio Manage: what firms ask
Should we move to CaseMatters Evo instead?
That is a product decision, and this page does not make it. Access describes CaseMatters Evo as built on Proclaim and browser-based. If the firm is weighing it against other systems, the comparison is made on the firm’s own requirements and costs, with staying on Proclaim as one of the options.
Can our Proclaim workflows be converted?
No tool converts them. They are rebuilt in the new system’s workflow or automation features. The useful starting point is a plain description of each workflow as it runs today, including the letters it sends and the dates it sets. Firms often find several that nobody needs, and those are left behind.
Are our accounts in Proclaim?
Only if the firm took the legal accounts module, and the analysis checks. If it did, client and office ledgers are extracted from Proclaim and reconciled to its reports. Where the accounts are in another package, that package is a second source, and its client ledger is matched to Proclaim’s cases before anything is loaded.
Do trust balances in Access Legal Proclaim 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 Access Legal Proclaim 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 Access Legal Proclaim 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. Contacts, notes, calendar entries 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 Access Legal Proclaim and into Clio Manage
Other destinations from Access Legal Proclaim
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.
Access Legal Proclaim and Clio Manage are the names and marks of their owners, used here only to identify the two systems.
Moving from Access Legal Proclaim 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.