Data migration route
Access Legal Proclaim data to SQLite
Access Legal Proclaim is a server-based practice management system, and SQLite is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what Access Legal Proclaim holds and keeps it readable and open to queries.
Access Legal ProclaimServer- Matters: Exported in full
- Tasks: Exported in full
- Time and expenses: Exported in full
- Billing: Exported in full
- Trust money: Exported in full
- Firm accounts: Exported in full
- Intake: Exported in full
- Documents: Exported with mapping
- Emails: Exported with mapping
- Contacts: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Calendar: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
SQLiteFiles- Templates: Kept as a readable archive
- 7 carried
- 2 mapped
- 4 to confirm
- 1 archived
What moves
What moves from Access Legal Proclaim to SQLite
Each row is a kind of record Access Legal Proclaim holds, whether SQLite has a place for it, and what is planned. On this route seven kinds of record carry across, two kinds need mapping, one kind has no place in SQLite and is 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 placeA matters table keyed by matter number. | Exported in full |
| ContactsClients, other parties and referrers | To be confirmed | Has a placeContacts and their roles on matters as linked tables. | Confirmed in the analysis |
| DocumentsFiles stored in or linked from the system | HeldDocuments are produced and stored on the case, with bundles. | Has a place in partListed in a table; the files themselves stay in folders beside the database. | Exported with mapping |
| EmailsEmails saved to matters or to the store | HeldEmails are linked to cases. | Has a place in partAs message files in folders, indexed in a table. | Exported with mapping |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeA notes table linked to matters. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a placeA table of dated entries, with no calendar view. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | HeldTasks are generated by workflows. | Has a placeA table of tasks and their status at the final date. | Exported in full |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime is recorded against budgets. | Has a placeA table of time and expense entries. | Exported in full |
| BillingInvoices, payments and debtor balances | HeldBills and court forms are prepared from recorded time. | Has a placeInvoice and receipt tables; invoice PDFs kept as files. | Exported in full |
| Trust moneyTrust or client account ledgers and balances | Held in partThrough the optional legal accounts module. | Has a placeTrust transactions as rows, for look-up and not for accounting. | Exported in full |
| Firm accountsGeneral ledger, office account and payables | Held in partOnly where the firm has taken the legal accounts module. | Has a placeLedger journals as rows, where the source held them. | Exported in full |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeColumns added to the table they belonged to. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldLetters and documents selected and adapted by workflow. | No placePrecedent files are kept in folders, not in the database. | Kept as a readable archive |
| IntakeLeads, enquiries, intake forms and pipelines | HeldAn Opportunities module with online quotes. | Has a placeAn enquiries table, where the source tracked them. | Exported in full |
What the plans mean
- Exported in full
- SQLite has a place for this kind of record. It is loaded there and checked against Access Legal Proclaim.
- Exported with mapping
- SQLite 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
- SQLite 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
Not a new system. A complete copy the firm can query.
Writing Access Legal Proclaim out to SQLite is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.
What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Access Legal Proclaim as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.
Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in Access Legal Proclaim stays untouched until the copy in SQLite has been checked.
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 SQLite
A SQLite archive suits a firm that wants the old system’s records kept, seldom consulted, and free of any server or subscription. Everything structured goes into one file. That simplicity moves the responsibility elsewhere: the file has no security of its own and no administrator watching it, so where it is stored and who can reach it are the real decisions.
One file, kept with the archive
Matters, contacts, time, invoices and trust transactions become tables in a single file. It is stored with the firm’s closed-matter records and can be copied like any document. A checksum recorded when the file is finalised lets anyone confirm, years later, that the copy they hold has not been altered, and the firm decides whether to keep one.
No logins inside the file
SQLite has no users or passwords. Anyone who can open the file can read every client’s ledger. Protection comes from where it is kept, such as a restricted folder or an encrypted volume, and that choice is the firm’s. It can suit an archive consulted by two people, and it is said plainly so nobody assumes otherwise.
Built for reading, not sharing
Only one program can write to the file at a time, and SQLite’s authors point people to a client/server database where many users share data over a network. A finished archive never meets that limit. It is the reason SQLite is used here for records that are closed and not for anything staff still update.
Documents stay outside it
Documents remain ordinary files in matter folders, and a table in the database lists each one with its matter, title, dates and path. Keeping them as files means they open with a double-click and can be handed to a client. The table is how a file is found by matter number instead of by guessing its name.
Someone has to open it
SQLite publishes its own command-line program for opening a database file, and other tools read the format too. None of that helps if nobody remembers how. Saved queries for the usual look-ups and a short note on which tool to use can sit in the same folder as the file, and the firm decides what it needs.
How NewLaw runs it
Four steps, in this order.
This route produces an archive, not a working system, so the steps are about completeness and proof.
Analysis
We read what Access Legal Proclaim holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything Access Legal Proclaim holds is in scope unless you take it out.
Clean-up, if you want it
An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.
Trial export
The data is written to SQLite as a trial and checked against Access Legal Proclaim: record counts, totals where Access Legal Proclaim holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.
Final export
After the last day of work in Access Legal Proclaim, the export is run a final time and checked again. There is nothing to go live. Access Legal Proclaim is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.
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 SQLite. 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
Structure, permissions and handover
SQLite is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.
There is nothing to install on a server and nothing to license. The work is in making the file usable and safe to keep: naming it, documenting its tables, storing it where the firm’s records policy says archives go, and checking that a member of staff can open it and find a matter. Whether a second copy is held somewhere separate is the firm’s call.
What is agreed and set up
- File name, storage location and whether a second copy exists
- Whether a checksum is recorded for later verification
- Saved queries for matter, ledger and document look-ups
- Which tool staff will use to open the file
- Who may open the folder the file sits in
- Retention period and destruction date noted beside the file
Questions
Access Legal Proclaim to SQLite: 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.
Does the copy in SQLite hold trust ledgers from Access Legal Proclaim?
Yes. Trust transactions as rows, for look-up and not for accounting. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in Access Legal Proclaim as at the export date.
What happens to records SQLite has no place for?
On this route that is templates. 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 is written out to SQLite?
Documents and emails are exported 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 decides who may open the archive and how long it is kept.
Other routes
Other routes from Access Legal Proclaim and into SQLite
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 SQLite are the names and marks of their owners, used here only to identify the two systems.
Moving from Access Legal Proclaim to SQLite?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.