Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

Mitratech CaseCloud to SharePoint migration

Mitratech CaseCloud is a cloud practice management system, and SharePoint is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.

FromMitratech CaseCloudCloud
  1. Documents: Carried across
  2. Matters: Carried with mapping
  3. Contacts: Carried with mapping
  4. Emails: Carried with mapping
  5. Notes: Carried with mapping
  6. Calendar: Carried with mapping
  7. Tasks: Carried with mapping
  8. Custom fields: Carried with mapping
  9. Templates: Carried with mapping
  10. Trust money: Confirmed in the analysis
ToSharePointCloud
  1. Time and expenses: Kept as a readable archive
  2. Billing: Kept as a readable archive
  3. Intake: Kept as a readable archive
Readable archiveNo place in SharePoint
  • 1 carried
  • 8 mapped
  • 1 to confirm
  • 3 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Mitratech CaseCloud to SharePoint

Each row is a kind of record Mitratech CaseCloud holds, whether SharePoint has a place for it, and what is planned. On this route one kind of record carries across, eight kinds need mapping, three kinds have no place in SharePoint and are archived and one kind is confirmed in the analysis.

Records in Mitratech CaseCloud and their place in SharePoint
RecordIn Mitratech CaseCloudIn SharePointWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldMatters, each with a stage, a status and its participants.Has a place in partAs a site, library, folder or list row the firm designs; no built-in matter record.Carried with mapping
ContactsClients, other parties and referrersHeldAccounts and contacts in Salesforce, attached to matters by participant role.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemHeldRelated Files on the matter, or an integrated document system.Has a placeFiles in libraries, with columns and versions.Carried across
EmailsEmails saved to matters or to the storeHeld 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, with columns for sender and date if set up.Carried with mapping
NotesFile notes, matter notes and contact notesHeldMatter comments.Has a place in partAs documents, or as rows in a notes list if one is built.Carried with mapping
CalendarAppointments, court dates and deadlinesHeldMatter Calendar. CalendarRules is listed for court rules dates.Has a place in partPossible as a list; usually left in Outlook.Carried with mapping
TasksTo-dos and workflow steps assigned to peopleHeldTask checklists and activity plans with dependencies.Has a place in partPossible as a list; no legal workflow built in.Carried with mapping
Time and expensesTime and expense entries, billed and unbilledHeldTimekeepers, rates, UTBMS codes and batch time entry.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeld in partBillings are generated from time, expenses and fee arrangements.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesTo be confirmedNo placeConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfHeldFields can be added to matters, participants and time layouts.Has a placeColumns and content types on libraries and lists.Carried with mapping
TemplatesPrecedents, document templates and automationHeldAdvoDoc templates, budget templates and activity plan templates.Has a place in partPrecedents as files; templates can be offered from a library.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeldIntakes and intake forms with a convert-to-matter action.No placeKept as a readable archive

What the plans mean

Carried across
SharePoint has a place for this kind of record. It is loaded there and checked against Mitratech CaseCloud.
Carried with mapping
SharePoint 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
SharePoint 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 SharePoint 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 SharePoint 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 SharePoint are finished.

Where the data is now

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving off Mitratech CaseCloud

Where it is going

SharePoint will take a firm’s documents in almost any arrangement, which is the difficulty. The structure has to be chosen before the load: what a client is, what a matter is, and where security is applied. Changing it afterwards means moving every file again. Most of the effort goes into that design and into the columns that describe each document.

  1. Site, library or folder per matter

    A matter can be a site, a library within a client site, or a folder in one large library. Each choice has consequences for permissions, for search and for how a new matter is opened. The firm makes that decision, and the people who open matters every day should be part of it.

  2. Columns are built before content

    If documents are to carry matter number, client, document type or author as columns, those columns and any content types exist before loading, so each file can be tagged as it arrives. Tagging hundreds of thousands of documents afterwards is a second project that seldom gets finished.

  3. The 400 character path

    SharePoint limits the full decoded path, site and library and folders and file name, to 400 characters. A deep tree copied from a server drive under a long site name can cross it. Path lengths are calculated against the planned structure, not the old one, before any file moves.

  4. Large libraries and the view threshold

    A library can hold millions of files, but a view that tries to show more than 5,000 items at once runs into the list view threshold. One flat library with a folder per matter needs indexed columns and filtered views from the start, or views begin to fail as the library fills.

  5. Security by library, not by file

    Microsoft supports up to 50,000 unique permissions in a library and recommends staying under 5,000. Restricting matters one folder at a time reaches that sooner than firms expect. Restricted work is better grouped into its own site or library, so the permission is set once.

More about moving into SharePoint

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in SharePoint on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what Mitratech CaseCloud holds and how it is organised, then agree with you where each kind of record will sit in SharePoint. Anything with no place there stays behind or is archived, and you see which before the move.

  2. 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.

  3. Trial load

    A trial is loaded into SharePoint 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.

  4. 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

Step 1 of 5: Start with the route

Moving fromMitratech CaseCloud
Moving toSharePoint

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what Mitratech CaseCloud holds

    What is in it, how its records link, and where each piece would sit in SharePoint. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  3. 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

SharePoint 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.

Making SharePoint work as a firm’s document store is a design and build job in its own right. The sites, libraries, columns and permission groups are created, a way of opening a new matter is put in place so the structure repeats itself, and the Outlook and Teams habits around it are agreed. Search is tested with real questions from fee earners.

What is agreed and set up

  • Site and library structure for clients and matters
  • Columns and content types for matter number and document type
  • Permission groups, with restricted matters in their own libraries
  • A repeatable way to create each new matter’s workspace
  • Version history limits and retention labels for closed matters
  • Views, indexed columns and search tested on loaded data

Questions

Mitratech CaseCloud to SharePoint: 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 SharePoint?

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 SharePoint 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 SharePoint has no place for?

On this route that is 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 SharePoint?

Matters, contacts, emails, notes, calendar entries, tasks, custom fields 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.

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.

How we do itDiscovery to rollout, step by step

Mitratech CaseCloud and SharePoint are the names and marks of their owners, used here only to identify the two systems.

Moving from Mitratech CaseCloud to SharePoint?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.