Data migration route
Mitratech CaseCloud to NetDocuments migration
Mitratech CaseCloud is a cloud practice management system, and NetDocuments is a cloud document management system. Documents and email move, filed under the matters they came from. Time, billing and trust have no place in a document system.
Mitratech CaseCloudCloud- Documents: Carried across
- Emails: Carried across
- Matters: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Tasks: Confirmed in the analysis
- Trust money: Confirmed in the analysis
NetDocumentsCloud- Contacts: Kept as a readable archive
- Notes: Kept as a readable archive
- Calendar: Kept as a readable archive
- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Intake: Kept as a readable archive
- 2 carried
- 3 mapped
- 2 to confirm
- 6 archived
What moves
What moves from Mitratech CaseCloud to NetDocuments
Each row is a kind of record Mitratech CaseCloud holds, whether NetDocuments has a place for it, and what is planned. On this route two kinds of record carry across, three kinds need mapping, six kinds have no place in NetDocuments and are archived and two kinds are 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 place in partAs a client and matter value with its workspace. Other matter details stay in practice management. | Carried with mapping |
| 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 placeImported with profile values, folder, dates and access set per document. | 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 placeLoaded as email items profiled to the matter. | Carried across |
| NotesFile notes, matter notes and contact notes | HeldMatter comments. | No placeFile notes are loaded as documents in the matter workspace. | Kept as a readable archive |
| 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. | To be confirmed | Confirmed in the analysis |
| 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. | Has a placeAs custom profile attributes, created in the repository before the load. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldAdvoDoc templates, budget templates and activity plan templates. | Has a place in partLoaded as documents in a precedents cabinet or workspace. Automation is set up afresh. | 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
- NetDocuments has a place for this kind of record. It is loaded there and checked against Mitratech CaseCloud.
- Carried with mapping
- NetDocuments 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
- NetDocuments 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
The documents move. The accounts do not.
Moving from a matter system into a document management system is a documents job. NetDocuments has no place for time, invoices or trust, so there is no financial cutover on this route. What it does want is structure. Every document from Mitratech CaseCloud is filed into a workspace or folder for its client and matter, with a profile that says what it is. The client and matter list becomes that structure, which is why it is cleaned before any file is copied.
A document’s own details count for more here than anywhere. Created and modified dates, author, document type and version become searchable profile fields, and a wrong date on a few thousand files is hard to undo. Email filed to matters is carried as messages. Document copies can be run again, so the trial is repeated until counts and dates agree. Matter data that NetDocuments cannot hold goes to whatever replaces Mitratech CaseCloud for matters and billing, or into an archive.
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 NetDocuments 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 NetDocuments
Loading into NetDocuments means every document arrives with a profile. The cabinet, its profile attributes and the client and matter lookup tables are built first. Documents are then imported with an instruction file that says, line by line, which file gets which client, matter, author, document type, folder and access. Preparing that file from the old system’s data is most of the work.
Lookup tables before documents
Client and matter are validated attributes, with matter the child of client. A value missing from the lookup table cannot be used to profile a document. The tables are loaded from the practice management system first, closed matters included, and each matter is flagged open or closed so old ones stay out of pick lists.
Workspaces come from the profile
A workspace shows whatever is profiled to its matter. So the question is not where to put a folder tree but how to profile each file. Old folder names are often turned into a document type attribute, or kept as a workspace folder, and the mapping decides which for each one.
Import files are unforgiving
The import file is comma-separated text, and NetDocuments itself warns that opening one in Excel can strip leading zeros from numbers and alter dates. A matter number of 00123 that becomes 123 will not match its lookup value. The files are kept as plain text from start to finish and are not opened in a spreadsheet.
Folder limits and depth
A folder can hold any number of documents but no more than 500 subfolders. Deep trees copied from a file server also work against the way the system is searched. Where a matter arrives with hundreds of nested folders, the plan flattens them and keeps the lost path in the document name or an attribute.
Security at the right level
Access can be set on the cabinet, by profile value, on a workspace or on a single document. Restricted matters are best carried as workspace or profile-based security, so that new documents pick it up. Document-by-document access lists copied from an old system are loaded only where the restriction was real.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in NetDocuments 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 NetDocuments. 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 NetDocuments 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 NetDocuments. 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 NetDocuments
Loaded data is not yet a working system. This is what NewLaw sets up in NetDocuments, beyond the migration, so that people can work in it from the first day.
Beyond the load, NetDocuments has to be designed: how many cabinets the firm needs, which profile attributes every document must carry, and what a new matter’s workspace looks like on its first day. After that it is connected to the practice management system so client and matter lists stay current, and ndOffice and the email filing tools are set up for each person, with training on profiling.
Set-up decisions in NetDocuments
- Cabinet design: one for the firm, or several by purpose
- Profile attributes, lookup tables and the client and matter hierarchy
- Workspace layout with default folders, filters and saved searches
- User groups, cabinet membership and security for restricted matters
- A feed of new clients and matters from practice management
- ndOffice, ndMail and Outlook filing on every desk, with training
Questions
Mitratech CaseCloud to NetDocuments: 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 NetDocuments?
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 NetDocuments 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 NetDocuments has no place for?
On this route that is contacts, notes, calendar entries, time entries, billing records 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 NetDocuments?
Matters, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Tasks and 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 NetDocuments
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 NetDocuments are the names and marks of their owners, used here only to identify the two systems.
Moving from Mitratech CaseCloud to NetDocuments?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.