Data migration route
Tabs3 Trust Accounting to SharePoint migration
Tabs3 Trust Accounting is a server-based 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.
Tabs3 Trust AccountingServer- Matters: Carried with mapping
- Contacts: Carried with mapping
- Notes: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
SharePointCloud- Trust money: Kept as a readable archive
- 2 mapped
- 3 to confirm
- 1 archived
What moves
What moves from Tabs3 Trust Accounting to SharePoint
Each row is a kind of record Tabs3 Trust Accounting holds, whether SharePoint has a place for it, and what is planned. On this route two kinds need mapping, one kind has no place in SharePoint and is archived and three kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partTrust accounts are keyed by a Trust ID in the same format as client numbers. | 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 partShares client and contact details with Billing and PracticeMaster. | 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 |
| Trust moneyTrust or client account ledgers and balances | HeldTrust ledgers, cheques and EFTs, bank reconciliation and a 3-Way Reconciliation Report. | 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 | To be confirmed | Has a place in partPrecedents as files; templates can be offered from a library. | 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 Tabs3 Trust Accounting 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 Tabs3 Trust Accounting 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 Tabs3 Trust Accounting, 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.
Tabs3 Trust Accounting runs on the firm’s own equipment, so the data is collected there: a copy of the database and the folders its documents sit in, taken with the firm’s IT provider or over a remote session. SharePoint is hosted by its maker, so loading depends on the import tools and access it provides. The old machine is kept, read only, as the fall-back record.
Where the data is now
Leaving Tabs3 Trust Accounting
Trust is the one part of a Tabs3 move that cannot be re-run casually. Each trust account balance is taken at an agreed date, by Trust ID and by bank account, and proved against a completed three-way reconciliation. The same figures are rehearsed on a full trial load. Only then is the cutover booked, and the old program is kept so past ledgers can be printed.
A trust account is a ledger
In this program a trust account means one client’s ledger, and a bank account is a separate record. Many trust accounts sit in one bank account. A destination that uses the words differently needs the mapping written down: Trust ID to matter, bank account to bank account.
Trust IDs mirror Client IDs
Trust IDs use the same key type and decimal places as client numbers, so a trust account normally lines up with a client and matter in Billing. Where a firm opened extra trust accounts for one matter, or one for several, those are found in the analysis and the firm decides which matter each balance belongs to.
Payments to the firm
A trust cheque or EFT marked as a payment to the firm posts to the client’s statement in Billing, or to General Ledger where Billing is not installed. Cutover falls between those two sides. The freeze begins only after every such payment has posted both ways, so no fee is paid in one system and unpaid in the other.
Uncleared items at cutover
Opening balances in the new system are ledger balances, but the first bank reconciliation there needs the uncleared cheques and deposits as well. Those are extracted as a list from the last Tabs3 reconciliation, for each bank account, and entered so the opening bank position agrees to the statement.
1099 totals and year end
Trust payees can be reported on 1099 forms, combined with Accounts Payable vendors. A mid-year move leaves part of the year’s payments in each system. Year-to-date totals for each payee are extracted so the firm’s year-end 1099 run is complete.
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 Tabs3 Trust Accounting 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 Tabs3 Trust Accounting: 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 Tabs3 Trust Accounting, a final pass over a weekend picks up what changed since the trial. Tabs3 Trust Accounting 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 Tabs3 Trust Accounting 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 Tabs3 Trust Accounting 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
Tabs3 Trust Accounting to SharePoint: what firms ask
Can trust be moved at a different time from billing?
It can, though it is rarely worth it. Trust balances show on statements and trust payments settle bills, so the two modules lean on each other. Moving them on the same weekend keeps one cut-off date. If they must be staged, the manual steps in between are agreed first.
Do closed trust ledgers come across?
Zero-balance trust accounts for finished matters carry history a regulator may ask for. Their transactions can be loaded where the destination accepts historical trust entries. Otherwise the ledgers are printed to PDF per client and filed to the matter, and Tabs3 is kept read only for the retention period.
What if the three-way reconciliation is out?
Then the difference is found and fixed in Tabs3 first. Loading an unreconciled trust ledger only moves the problem into a system nobody knows yet. The analysis includes the latest reconciliation, and cutover is not scheduled until bank, book and client ledger totals agree.
Do trust balances in Tabs3 Trust Accounting have a place in SharePoint?
No. SharePoint does not keep trust ledgers. Trust records from Tabs3 Trust Accounting 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 trust ledgers. They are exported from Tabs3 Trust Accounting 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 Tabs3 Trust Accounting data is loaded into SharePoint?
Matters and contacts are carried with mapping, so each mapping is agreed with you first. Notes, custom fields and templates 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 Tabs3 Trust Accounting and into SharePoint
Other destinations from Tabs3 Trust Accounting
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.
Tabs3 Trust Accounting and SharePoint are the names and marks of their owners, used here only to identify the two systems.
Moving from Tabs3 Trust Accounting 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.