Data migration route
MyCase to SharePoint migration
MyCase 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.
MyCaseCloud- Documents: Carried across
- Matters: Carried with mapping
- Contacts: Carried with mapping
- Emails: Carried with mapping
- Notes: Carried with mapping
- Calendar: Carried with mapping
- Tasks: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
SharePointCloud- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Trust money: Kept as a readable archive
- Firm accounts: Kept as a readable archive
- Intake: Kept as a readable archive
- 1 carried
- 8 mapped
- 5 archived
What moves
What moves from MyCase to SharePoint
Each row is a kind of record MyCase 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 and five kinds have no place in SharePoint and are archived.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldCalled cases. Each has a unique name, an optional case number, a practice area and an open or closed state. | 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 referrers | HeldContacts (people) and companies are separate record types, linked to cases. | Has a place in partOnly as rows in a list built for the purpose. | Carried with mapping |
| DocumentsFiles stored in or linked from the system | HeldStored against cases in folders, with version tracking and unlimited storage. | Has a placeFiles in libraries, with columns and versions. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partOnly emails linked through the Outlook or Gmail add-ins or a forwarding address. | 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 notes | Held | Has a place in partAs documents, or as rows in a notes list if one is built. | Carried with mapping |
| CalendarAppointments, court dates and deadlines | HeldCan sync with Google Calendar and Outlook. | Has a place in partPossible as a list; usually left in Outlook. | Carried with mapping |
| TasksTo-dos and workflow steps assigned to people | HeldTasks can be created by workflow automation. | Has a place in partPossible as a list; no legal workflow built in. | Carried with mapping |
| Time and expensesTime and expense entries, billed and unbilled | Held | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | Held | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | Held | No place | Kept as a readable archive |
| Firm accountsGeneral ledger, office account and payables | Held in partMyCase Accounting is an add-on; a QuickBooks sync is the alternative. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | HeldCustom fields on cases and on contacts. | Has a placeColumns and content types on libraries and lists. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldWord-based document templates and automation. | Has a place in partPrecedents as files; templates can be offered from a library. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldLeads in a Kanban view, with intake forms that can be embedded on a website. | No place | Kept 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 MyCase.
- 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.
- Kept as a readable archive
- SharePoint has no place for it. It is exported in a format that opens without MyCase 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 MyCase 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 MyCase.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of MyCase 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 MyCase is kept running until the checks on SharePoint are finished.
Where the data is now
Leaving MyCase
A firm leaving MyCase is moving a set of cases with everything tied to them, and the first job is working out which of those ties the next system can hold. Documents, time, invoices and trust balances have obvious homes. Portal messages, text conversations and the lead pipeline often do not, so each is given a destination or a reason to stay behind before any data is extracted.
Cases, contacts and companies
MyCase says case where most systems say matter, and it keeps people and companies as two separate record types. A destination that has one contact card for both, or that insists on a client record above each matter, needs a rule for which MyCase contact becomes the client when a case has several linked to it.
Case numbers are optional
The case number is a free-text field that a firm can leave empty or fill with a court file number. If the new system wants a unique matter number on every record, the analysis finds the cases with no number or a shared one, and the firm agrees how those are numbered.
Only linked emails are there
Emails reach a case through the Gmail or Outlook add-ins, or by forwarding to a personal MyCase address. Anything nobody linked is still in a mailbox, and emails the software could not match wait in an Unresolved Emails queue. That queue is worth clearing before extraction, because unmatched emails have no case to travel with.
Books may sit elsewhere
Invoices, payments and trust ledgers are inside MyCase. The general ledger is either the MyCase Accounting add-on or QuickBooks fed by a sync. Where QuickBooks is in use, debtor and trust totals are taken from both and compared before cutover, so the opening figures in the new system are ones the bookkeeper recognises.
Messages and texts
Client portal messages and text conversations are saved against the case. Few systems have a matching record type. They are usually carried as a dated note or a single document on each matter, and the firm sees an example of how that reads before deciding whether it is enough.
Where it is going
Arriving in SharePoint
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.
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.
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.
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.
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.
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.
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.
Analysis
We read what MyCase 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.
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 SharePoint and checked against MyCase: 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 MyCase, a final pass over a weekend picks up what changed since the trial. MyCase 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 MyCase 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 MyCase 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.
- 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
MyCase to SharePoint: what firms ask
Can we keep our existing matter numbers when we move to MyCase?
Yes. The case number field accepts letters, digits and special characters, so numbers can go in exactly as they are. MyCase does not require the number to follow a pattern. What it does require is a unique case name, so the naming rule usually takes more discussion than the numbering.
We are leaving MyCase. Do our client portal messages come with us?
They can be kept, but rarely as live messages. Most systems have no record that matches a MyCase portal thread, so the messages are carried as dated notes or one document per matter. Whether the destination has anything closer is confirmed in the analysis, and the firm sees a sample first.
What happens to closed cases?
They move as closed, with their closed date, documents and billing history where the destination has a place for it. Some firms bring across only matters closed within a set number of years and keep the older ones in the read-only copy of the old system. That choice is made before the trial load.
Do trust balances in MyCase have a place in SharePoint?
No. SharePoint does not keep trust ledgers. Trust records from MyCase are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.
What happens to records SharePoint has no place for?
On this route that is time entries, billing records, trust ledgers, the firm’s accounts and intake records. They are exported from MyCase 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 MyCase 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. The firm also decides which closed matters and how many versions of a document are in scope.
Other routes
Other routes from MyCase and into SharePoint
Other destinations from MyCase
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.
MyCase and SharePoint are the names and marks of their owners, used here only to identify the two systems.
Moving from MyCase 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.