Data migration route
LeanLaw to SharePoint migration
LeanLaw is a cloud accounting and billing system, and SharePoint is cloud file storage. What moves is the files, plus a readable export of everything else the old system holds.
LeanLawCloud- Matters: Carried with mapping
- Contacts: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Intake: Confirmed in the analysis
SharePointCloud- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Trust money: Kept as a readable archive
- 3 mapped
- 4 to confirm
- 3 archived
What moves
What moves from LeanLaw to SharePoint
Each row is a kind of record LeanLaw holds, whether SharePoint has a place for it, and what is planned. On this route three kinds need mapping, three kinds have no place in SharePoint and are archived and four kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldClients and matters as billing records, with budgets, rates and fee arrangements. | 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 | Held in partClients and billing contacts only. | Has a place in partOnly as rows in a list built for the purpose. | Carried with mapping |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place in partAs documents, or as rows in a notes list if one is built. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a place in partPossible as a list; no legal workflow built in. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime and expenses tied to client and matter. | No place | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | HeldHourly, flat fee and recurring fixed fees; LEDES on some plans. | No place | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | HeldClient and matter trust ledgers, with the trust bank account kept in QuickBooks Online. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeColumns and content types on libraries and lists. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | Held in partInvoice templates. | Has a place in partPrecedents as files; templates can be offered from a library. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | No place | Confirmed in the analysis |
What the plans mean
- 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 LeanLaw 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
An export the firm can open without the system.
SharePoint holds files, and most of what LeanLaw holds is records. This route is therefore an export job. Each kind of record is written out in a format that opens without the system it came from: lists as spreadsheets, statements and invoices as PDFs, attachments as the files they were. The export is laid out in folders that make sense to someone who never used LeanLaw, by client or by year, with a short index file saying what is where.
Firms do this when a subscription is ending, when a system is being retired, or to meet a retention rule. The test of the result is whether a question can still be answered from it years later: what was this client invoiced, who signed this agreement and when. So the trial export is checked by asking those questions of it. Totals are agreed to the system’s own reports, and access to the folder in SharePoint is limited before the export is copied in.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of LeanLaw 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 LeanLaw is kept running until the checks on SharePoint are finished.
Where the data is now
Leaving LeanLaw
LeanLaw and QuickBooks Online hold two halves of the same financial record, kept in step by a live sync. A firm leaving LeanLaw is usually keeping QuickBooks, at least at first. So the question is less what to extract than how to change the system feeding QuickBooks without posting anything twice, and where the matter-level detail that only LeanLaw holds will live afterwards.
QuickBooks keeps the ledger
Every invoice, payment and trust transaction entered in LeanLaw is also in QuickBooks Online. If the destination connects to the same QuickBooks company, it must start from an agreed date and recognise what is already there. Where the destination has its own general ledger, QuickBooks is closed off at a period end and balances are carried in.
Matter detail lives in LeanLaw
QuickBooks knows the totals. LeanLaw knows which timekeeper did what on which matter, at what rate, and against what budget. That is the part to extract: time and expense entries with their narratives, and the invoice lines they became. The sums are checked back to the QuickBooks figures client by client.
Trust in two places
The trust bank account is an account in QuickBooks Online, and the ledger for each client and matter is in LeanLaw. Both have to agree with the bank statement. The three-way reconciliation is completed and saved for the last period before cutover, and opening trust balances are taken from it.
Compensation and origination
LeanLaw tracks attorney compensation and origination credit as time is billed and collected, and partners may be paid on those reports. Not every system records origination against a matter. The firm checks early whether the destination can, and saves the historic compensation reports whatever the answer.
It was never the case file
Parties, deadlines, documents and correspondence were never in LeanLaw. Some firms pair it with Clio or MyCase for those, and others use folders and Outlook. A move to an all-in-one system therefore draws on several sources, and the matter list from LeanLaw is used as the index that ties them together.
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 LeanLaw 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 LeanLaw: 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 LeanLaw, a final pass over a weekend picks up what changed since the trial. LeanLaw 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 LeanLaw 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 LeanLaw 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
LeanLaw to SharePoint: what firms ask
If we stop using LeanLaw, do we lose our QuickBooks Online data?
No. QuickBooks Online is a separate subscription in the firm’s own name, and the invoices, payments and trust entries that synced into it stay there. What goes when LeanLaw goes is the legal layer on top: time narratives, matter ledgers and the reports built from them, which is why those are extracted.
Can the new system take over the same QuickBooks company?
Often, yes. It needs to be told which customers and open invoices already exist so that it links to them and does not create a second set. The switch is made at an agreed date, with LeanLaw’s sync turned off first and the receivables total compared on both sides.
We use LeanLaw with Clio for case management. Which is the source for matters?
Both, for different things. Clio would hold the case detail, documents and calendar, and LeanLaw the time, bills and trust ledgers. The two matter lists are compared in the analysis. A matter that appears in one and not the other is traced and resolved before anything is loaded.
Do trust balances in LeanLaw have a place in SharePoint?
No. SharePoint does not keep trust ledgers. Trust records from LeanLaw 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 and trust ledgers. They are exported from LeanLaw 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 LeanLaw data is loaded into SharePoint?
Matters, contacts and templates are carried with mapping, so each mapping is agreed with you first. Notes, tasks, custom fields and intake records 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 LeanLaw and into SharePoint
Other destinations from LeanLaw
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.
LeanLaw and SharePoint are the names and marks of their owners, used here only to identify the two systems.
Moving from LeanLaw 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.