Data migration route
Mitratech CaseCloud to Dropbox migration
Mitratech CaseCloud is a cloud practice management system, and Dropbox is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.
Mitratech CaseCloudCloud- Documents: Carried across
- Emails: Carried with mapping
- Notes: Carried with mapping
- Templates: Carried with mapping
- Trust money: Confirmed in the analysis
DropboxCloud- Matters: Kept as a readable archive
- Contacts: Kept as a readable archive
- Calendar: Kept as a readable archive
- Tasks: Kept as a readable archive
- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Custom fields: Kept as a readable archive
- Intake: Kept as a readable archive
- 1 carried
- 3 mapped
- 1 to confirm
- 8 archived
What moves
What moves from Mitratech CaseCloud to Dropbox
Each row is a kind of record Mitratech CaseCloud holds, whether Dropbox has a place for it, and what is planned. On this route one kind of record carries across, three kinds need mapping, eight kinds have no place in Dropbox and are archived 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. | No placeA matter is a folder named by the firm’s convention. | Kept as a readable archive |
| ContactsClients, other parties and referrers | HeldAccounts and contacts in Salesforce, attached to matters by participant role. | No place | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | HeldRelated Files on the matter, or an integrated document system. | Has a placeFiles in folders; the folder path is the only index. | Carried across |
| 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 .msg or .eml files filed in the matter folder. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | HeldMatter comments. | Has a place in partAs documents saved to the matter folder. | Carried with mapping |
| CalendarAppointments, court dates and deadlines | HeldMatter Calendar. CalendarRules is listed for court rules dates. | No place | Kept as a readable archive |
| TasksTo-dos and workflow steps assigned to people | HeldTask checklists and activity plans with dependencies. | No place | Kept as a readable archive |
| Time and expensesTime and expense entries, billed and unbilled | HeldTimekeepers, rates, UTBMS codes and batch time entry. | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | Held in partBillings are generated from time, expenses and fee arrangements. | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | To be confirmed | No place | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | HeldFields can be added to matters, participants and time layouts. | No place | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | HeldAdvoDoc templates, budget templates and activity plan templates. | Has a place in partPrecedents load as ordinary files in a precedents folder. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldIntakes and intake forms with a convert-to-matter action. | No place | Kept as a readable archive |
What the plans mean
- Carried across
- Dropbox has a place for this kind of record. It is loaded there and checked against Mitratech CaseCloud.
- Carried with mapping
- Dropbox 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
- Dropbox has no place for it. It is exported in a format that opens without Mitratech CaseCloud 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
Out of the system, into folders the firm can read.
File storage has folders and files and nothing else. Moving from Mitratech CaseCloud into Dropbox means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters Dropbox does not allow in a name.
Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in Mitratech CaseCloud.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Mitratech CaseCloud depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to Mitratech CaseCloud is kept running until the checks on Dropbox are finished.
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 Dropbox
Loading matter files into Dropbox is a matter of getting the tree right, since the tree is all there is. No field holds a matter number or a client name. The folder names carry that, so the naming rule is agreed first: what a client folder is called, what a matter folder is called, and which subfolders every matter gets.
Team folders before files
Team folders are shared with groups, and each group is given an editor or view-only role. The groups and the top-level folders are created before the load so that files arrive already restricted. Loading first and sharing afterwards leaves a period in which the wrong people can see everything.
Keep paths under 260 characters
Dropbox’s naming guidance asks for full paths shorter than 260 characters. Matter trees from document systems often exceed that once the client name, matter description and subfolders are joined. Long paths are measured early and cut back by rule, usually by trimming the matter description and keeping the number.
Characters that get swapped
On Windows, the desktop app replaces restricted characters in names with an underscore. A file called Smith v Jones: Affidavit becomes something slightly different on some machines. Names are cleaned before loading so that the file has one name everywhere and matches the index kept from the old system.
Matter data has nowhere to go
Parties, matter type, responsible lawyer, open and closed dates: none of it has a field here. If the firm is leaving a practice management system and keeping only documents, that data can be kept as an exported spreadsheet beside the folders, so they can still be read against it. Whether one is produced is decided in the analysis.
History starts on loading day
Version history in Dropbox begins when a file arrives. Earlier versions from the old system come across as separately named files in the matter folder, or stay behind. The firm sees a sample matter loaded with its earlier versions as named copies before choosing.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Dropbox on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what Mitratech CaseCloud holds and how it is organised, then agree with you where each kind of record will sit in Dropbox. Anything with no place there stays behind or is archived, and you see which before the move.
Clean-up
Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.
Trial load
A trial is loaded into Dropbox and checked against Mitratech CaseCloud: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.
Cutover
There is no financial cutover on this route. After a short freeze on changes in Mitratech CaseCloud, a final pass over a weekend picks up what changed since the trial. Mitratech CaseCloud 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 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 Dropbox. 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
Dropbox is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.
Beyond the load, a firm on Dropbox needs the account arranged so the files belong to the firm and not to individuals. That means a team plan with an administrator, groups that match how the firm works, and a decision about which folders sync to every computer. A written filing rule tells staff where each new matter folder goes.
What is agreed and set up
- Team folders for clients, precedents and administration
- Groups by team, each with an editor or viewer role
- Which folders sync to PCs and which stay online-only
- Rules for sharing links and folders with clients
- A written naming rule for client and matter folders
- Steps for removing a leaver without losing their folders
Questions
Mitratech CaseCloud to Dropbox: 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.
Do trust balances in Mitratech CaseCloud have a place in Dropbox?
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. If Dropbox turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.
What happens to records Dropbox has no place for?
On this route that is matters, contacts, calendar entries, tasks, time entries, billing records, custom fields and intake records. They are exported from Mitratech CaseCloud 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 Mitratech CaseCloud data is loaded into Dropbox?
Emails, notes and templates are carried with mapping, so each mapping is agreed with you first. Trust ledgers are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from Mitratech CaseCloud and into Dropbox
Other destinations from Mitratech CaseCloud
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 Dropbox are the names and marks of their owners, used here only to identify the two systems.
Moving from Mitratech CaseCloud to Dropbox?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.