Data migration route
Access Legal Proclaim data to Microsoft SQL Server
Access Legal Proclaim is a server-based practice management system, and Microsoft SQL Server is a database on a server the firm runs. 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
- Templates: Exported with mapping
- Contacts: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Calendar: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
Microsoft SQL ServerServer- 7 carried
- 3 mapped
- 4 to confirm
What moves
What moves from Access Legal Proclaim to Microsoft SQL Server
Each row is a kind of record Access Legal Proclaim holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route seven kinds of record carry across, three kinds need mapping 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 table of matters linked to clients, parties and fee earners. | Exported in full |
| ContactsClients, other parties and referrers | To be confirmed | Has a placePeople and companies, with their roles on each matter. | 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 partAs files in folders with an index table; storing files in the database is possible. | Exported with mapping |
| EmailsEmails saved to matters or to the store | HeldEmails are linked to cases. | Has a place in partAs message files with an index table, or as rows of header fields. | Exported with mapping |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeRows of text linked to matters and contacts. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a placeRows of appointments and key dates; nothing displays them as a calendar. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | HeldTasks are generated by workflows. | Has a placeRows with assignee, due date and status. | Exported in full |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime is recorded against budgets. | Has a placeTime and expense rows with rates and billed status. | Exported in full |
| BillingInvoices, payments and debtor balances | HeldBills and court forms are prepared from recorded time. | Has a placeInvoices, lines and receipts as rows; 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 placeTransactions and balances for look-up; it is not a trust accounting system. | Exported in full |
| Firm accountsGeneral ledger, office account and payables | Held in partOnly where the firm has taken the legal accounts module. | Has a placeGeneral ledger journals and balances, where the source held them. | Exported in full |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeAs added columns, or a table of field names and values. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldLetters and documents selected and adapted by workflow. | Has a place in partPrecedent files can be stored; automation does not run here. | Exported with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldAn Opportunities module with online quotes. | Has a placeEnquiry rows, where the source recorded them. | Exported in full |
What the plans mean
- Exported in full
- Microsoft SQL Server has a place for this kind of record. It is loaded there and checked against Access Legal Proclaim.
- Exported with mapping
- Microsoft SQL Server 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.
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 Microsoft SQL Server 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 Microsoft SQL Server 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 Microsoft SQL Server
There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.
Restored copy or rebuilt schema
Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.
No screens come with it
A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.
Documents sit beside the database
Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.
The edition follows the size
A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.
Backups and a test restore
An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.
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 Microsoft SQL Server 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 Microsoft SQL Server 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 Microsoft SQL Server. 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
Microsoft SQL Server 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.
Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.
What is agreed and set up
- Server, instance and edition agreed with the IT provider
- Read-only logins and roles for named staff
- Views for matter, ledger, time and document look-ups
- Backup schedule and who tests a restore
- Plain names and descriptions for tables and columns
- Excel or Power BI connected for reporting
Questions
Access Legal Proclaim to Microsoft SQL Server: 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 Microsoft SQL Server hold trust ledgers from Access Legal Proclaim?
Yes. Transactions and balances for look-up; it is not a trust accounting system. 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.
Does everything in Access Legal Proclaim have a place in Microsoft SQL Server?
Most of it does on paper. Contacts, notes, calendar entries and custom fields could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in Microsoft SQL Server is kept as a readable archive, and you see which before the move.
What has to be decided before Access Legal Proclaim is written out to Microsoft SQL Server?
Documents, emails and templates 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 Microsoft SQL Server
Other destinations from Access Legal Proclaim
Other systems that move into Microsoft SQL Server
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 Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.
Moving from Access Legal Proclaim to Microsoft SQL Server?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.