Data migration route
Lawcus to SharePoint migration
Lawcus 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.
LawcusCloud- 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
- Intake: Kept as a readable archive
- 1 carried
- 8 mapped
- 4 archived
What moves
What moves from Lawcus to SharePoint
Each row is a kind of record Lawcus 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 four kinds have no place in SharePoint and are archived.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldShown as cards on boards with a stage, or as a list; numbers come from a saved scheme. | 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 with custom fields and field groups. | 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 | HeldFolders in Lawcus, with two-way sync to Google Drive and links to Dropbox, Box or OneDrive. | Has a placeFiles in libraries, with columns and versions. | Carried across |
| EmailsEmails saved to matters or to the store | Held in partEmails and attachments logged to a matter through the Gmail or Outlook add-ins. | 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 | HeldNotes and interactions on a matter can be pinned or starred. | 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 | Held | Has a place in partPossible as a list; usually left in Outlook. | Carried with mapping |
| TasksTo-dos and workflow steps assigned to people | HeldNo-code workflows can create tasks when a matter changes. | 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 | HeldHourly, flat fee and contingency; invoice templates per currency; credit notes. | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | HeldTrust balances and a minimum retainer threshold per matter. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | HeldCustom fields and field groups for contacts and matters. | Has a placeColumns and content types on libraries and lists. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | HeldDocument automation and reusable invoice templates. | Has a place in partPrecedents as files; templates can be offered from a library. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | HeldLeads on a Kanban board, with client-facing and internal forms. | 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 Lawcus.
- 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 Lawcus 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 Lawcus 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 Lawcus.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of Lawcus 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 Lawcus is kept running until the checks on SharePoint are finished.
Where the data is now
Leaving Lawcus
In Lawcus a matter’s position on a board says as much about it as any field. Stages, boards and the automations attached to them are how a firm on Lawcus knows where every file stands. A move off it has to turn that visual arrangement into something the destination can store, and it has to do so without losing the difference between a lead and a matter.
Stages are the status
Each board has its own stages, and a matter’s stage is what staff look at to see progress. A conveyancing board and a litigation board will not share stage names. Destinations tend to offer one status list, or a status per matter type. Every board’s stages are mapped separately, and the firm approves the mapping.
Leads sit on boards too
Prospects are tracked on a Kanban board of their own before they become clients. A lead and a matter can look alike in the interface. The extraction keeps them apart, and leads that were never converted are loaded as intake records or left as an exported list, depending on what the destination offers.
Automations are not data
No-code workflows send emails, create tasks and produce documents when a matter changes stage or a form comes in. None of that is a record that can be moved. The workflows are documented as rules during the analysis, and the firm chooses which ones to rebuild in the new system’s own automation.
QuickBooks was fed one way
Lawcus pushes invoices, payments and expenses to QuickBooks Online and takes nothing back. An edit made directly in QuickBooks is therefore unknown to Lawcus. The two can drift apart. Receivables are compared on both sides before cutover, and the firm decides which figure is right where they differ.
More than one currency
Invoice templates can be set up for clients billed in different currencies. A destination that works in one currency cannot hold those balances as they are. Foreign-currency clients are identified early, and the firm decides whether their history is converted at a stated rate or kept in the old system.
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 Lawcus 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 Lawcus: 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 Lawcus, a final pass over a weekend picks up what changed since the trial. Lawcus 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 Lawcus 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 Lawcus 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
Lawcus to SharePoint: what firms ask
Our documents sync between Lawcus and Google Drive. Which copy is moved?
The Google Drive copy is usually the easier source, because it is in the firm’s own account and the sync keeps the two alike. Lawcus supplies the link between each folder and its matter. A sample of matters is compared on both sides first to confirm nothing is missing from the Drive.
Can our matter numbers be kept?
Yes. Lawcus generates matter numbers from a numbering scheme the firm saved, so the numbers are consistent and can be carried as they are. If the destination produces numbers in another format, the Lawcus number is kept in a reference field and new matters follow the new format.
What happens to forms our clients filled in?
Answers that were saved to fields on a contact or matter are data and move with that record. Forms marked internal are treated the same way. The form designs are specific to Lawcus. If the new system has intake forms, they are rebuilt there from the same questions.
Do trust balances in Lawcus have a place in SharePoint?
No. SharePoint does not keep trust ledgers. Trust records from Lawcus 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 and intake records. They are exported from Lawcus 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 Lawcus 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 Lawcus and into SharePoint
Other destinations from Lawcus
Other systems that move into SharePoint
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.
Lawcus and SharePoint are the names and marks of their owners, used here only to identify the two systems.
Moving from Lawcus 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.