Data migration route
Mitratech CaseCloud data to Microsoft SQL Server
Mitratech CaseCloud is a cloud 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 Mitratech CaseCloud holds and keeps it readable and open to queries.
Mitratech CaseCloudCloud- Matters: Exported in full
- Contacts: Exported in full
- Notes: Exported in full
- Calendar: Exported in full
- Tasks: Exported in full
- Time and expenses: Exported in full
- Billing: Exported in full
- Intake: Exported in full
- Documents: Exported with mapping
- Emails: Exported with mapping
- Custom fields: Exported with mapping
- Templates: Exported with mapping
- Trust money: Confirmed in the analysis
Microsoft SQL ServerServer- 8 carried
- 4 mapped
- 1 to confirm
What moves
What moves from Mitratech CaseCloud to Microsoft SQL Server
Each row is a kind of record Mitratech CaseCloud holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route eight kinds of record carry across, four kinds need mapping and one kind is confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldMatters, each with a stage, a status and its participants. | Has a placeA table of matters linked to clients, parties and fee earners. | Exported in full |
| ContactsClients, other parties and referrers | HeldAccounts and contacts in Salesforce, attached to matters by participant role. | Has a placePeople and companies, with their roles on each matter. | Exported in full |
| DocumentsFiles stored in or linked from the system | HeldRelated Files on the matter, or an integrated document system. | 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 | Held in partEmail can be sent from a matter. Filing from a mailbox needs the email integration. | 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 | HeldMatter comments. | Has a placeRows of text linked to matters and contacts. | Exported in full |
| CalendarAppointments, court dates and deadlines | HeldMatter Calendar. CalendarRules is listed for court rules dates. | Has a placeRows of appointments and key dates; nothing displays them as a calendar. | Exported in full |
| TasksTo-dos and workflow steps assigned to people | HeldTask checklists and activity plans with dependencies. | Has a placeRows with assignee, due date and status. | Exported in full |
| Time and expensesTime and expense entries, billed and unbilled | HeldTimekeepers, rates, UTBMS codes and batch time entry. | Has a placeTime and expense rows with rates and billed status. | Exported in full |
| BillingInvoices, payments and debtor balances | Held in partBillings are generated from time, expenses and fee arrangements. | Has a placeInvoices, lines and receipts as rows; invoice PDFs kept as files. | Exported in full |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | Has a placeTransactions and balances for look-up; it is not a trust accounting system. | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldFields can be added to matters, participants and time layouts. | Has a placeAs added columns, or a table of field names and values. | Exported with mapping |
| TemplatesPrecedents, document templates and automation | HeldAdvoDoc templates, budget templates and activity plan templates. | Has a place in partPrecedent files can be stored; automation does not run here. | Exported with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldIntakes and intake forms with a convert-to-matter action. | 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 Mitratech CaseCloud.
- 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 Mitratech CaseCloud 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 Mitratech CaseCloud 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.
Mitratech CaseCloud is hosted by its maker and Microsoft SQL Server sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What Mitratech CaseCloud will release depends on its export tools, and that is confirmed in the analysis.
Where the data is now
Leaving Mitratech CaseCloud
CaseCloud data is Salesforce data, so leaving it starts with the org and not with an export button. What has to be established is which of the vendor’s applications the firm installed, how far the administrator customised them, and whether spend management records for outside counsel are in scope as well as the firm’s own matters.
Three applications, one org
Matter Management, Spend Management and Access Control are separate packages in the same org. A law firm may use only the first. A legal department may hold invoices from outside counsel in the second. Scope is set package by package, so nothing is extracted that the firm never used and nothing in use is missed.
Access rules do not export
Access Control decides which users and groups can see a matter and its related records. Those rules are configuration, not data, and the destination has its own security model. Restricted matters are listed with who may see them, and the equivalent restriction is rebuilt and tested in the new system before go-live.
Intakes convert to matters
An intake is its own record, filled in through an intake form and later converted to a matter. Converted intakes repeat what the matter already holds. Unconverted ones are leads or declined enquiries. The firm decides whether those go to the new system’s intake module, become contacts with a note, or stay behind.
Fee arrangements drive the numbers
Fees can be charged through a matter fee arrangement, once or on a recurring schedule, and the arrangement governs how time and expenses are treated. Few destinations model this the same way. Open arrangements are documented matter by matter, so that the next bill after the move is raised on the agreed terms.
Legal holds and conflict checks
The product keeps legal hold notices with their acknowledgements, and conflict checks can be run and their results managed. These are compliance records where the dates matter. If the destination has no place for them, they are exported as documents and filed to the matter or to the firm’s risk records.
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 Mitratech CaseCloud holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything Mitratech CaseCloud 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 Mitratech CaseCloud: record counts, totals where Mitratech CaseCloud 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 Mitratech CaseCloud, the export is run a final time and checked again. There is nothing to go live. Mitratech CaseCloud 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 Mitratech CaseCloud 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 Mitratech CaseCloud 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
Mitratech CaseCloud to Microsoft SQL Server: what firms ask
We bought AdvoLogix years ago. Is this page about our system?
Almost certainly. The product was sold as AdvoLogix Matter Management before Mitratech introduced the CaseCloud name in late 2024, and the two share a help centre. A quick check is the Salesforce app launcher. If it shows matters and participants under an AdvoLogix or CaseCloud application, the firm is on this product whatever the invoice says.
Can we stay on Salesforce and only replace the legal application?
Yes, if the destination also runs on Salesforce, as Litify does. The accounts and contacts can stay where they are, and the matter records are remapped inside the org or moved to a new one. It is still a migration, because each product brings its own objects for matters, parties and time.
What about documents held in NetDocuments or iManage?
If the files are in a document system through the integration, they may not need to move at all. The matter in the new system is pointed at the existing workspace, provided the destination integrates with the same store. Where it does not, the files are moved and the matter number is used to file each one.
Does the copy in Microsoft SQL Server hold trust ledgers from Mitratech CaseCloud?
That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in Mitratech CaseCloud before the plan is fixed.
Does everything in Mitratech CaseCloud have a place in Microsoft SQL Server?
Most of it does on paper. Trust ledgers 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 Mitratech CaseCloud is written out to Microsoft SQL Server?
Documents, emails, custom fields and templates are exported with mapping, so each mapping is agreed with you first. Trust ledgers 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 Mitratech CaseCloud and into Microsoft SQL Server
Other destinations from Mitratech CaseCloud
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.
Mitratech CaseCloud and Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.
Moving from Mitratech CaseCloud 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.