Data migration route
Tabs3 Billing to Lawmatics migration
Tabs3 Billing is a server-based accounting and billing system, and Lawmatics is a cloud CRM and intake system. Lawmatics is built around people and enquiries, so the contact list leads this move, and the table shows what else has a place.
Tabs3 BillingServer- Matters: Carried across
- Contacts: Carried across
- Time and expenses: Carried with mapping
- Billing: Carried with mapping
- Trust money: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
LawmaticsCloud- 2 carried
- 4 mapped
- 2 to confirm
What moves
What moves from Tabs3 Billing to Lawmatics
Each row is a kind of record Tabs3 Billing holds, whether Lawmatics has a place for it, and what is planned. On this route two kinds of record carry across, four kinds need mapping and two kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | HeldEach matter is a Client ID; the digits after the decimal point are the matter. | Has a placeLoaded from CSV with a status of PNC, Hired or Lost and a pipeline stage. | Carried across |
| ContactsClients, other parties and referrers | Held in partClient names and addresses; fuller contact records are in PracticeMaster. | Has a placeContacts and companies load from CSV; relationships link further parties to a matter. | Carried across |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeNotes on matters, contacts and companies. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldFees with hours worked and hours to bill, plus costs. | Has a place in partTime entries and expenses, where the Time & Billing module is enabled. | Carried with mapping |
| BillingInvoices, payments and debtor balances | HeldDraft and final statements, payments and a client ledger. | Has a place in partInvoices and payments; a past invoice is entered as sent, then marked paid. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | Held in partClient funds for retainers; trust ledgers are in the Trust Accounting module. | Has a place in partA trust account with a running balance; deposits are allocated to a contact and matter. | Carried with mapping |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeMatter, contact and company fields. A field must exist before data is imported into it. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldStatement layouts built in the Statement Designer. | Has a place in partDocument and email templates are rebuilt with Lawmatics merge fields. | Carried with mapping |
What the plans mean
- Carried across
- Lawmatics has a place for this kind of record. It is loaded there and checked against Tabs3 Billing.
- Carried with mapping
- Lawmatics 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.
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
Mostly a contact list, cleaned before it lands.
Lawmatics is built for contacts, leads and the conversations around them. What Tabs3 Billing can offer it first is a list of people and companies, and sometimes a history that can be attached as notes. Whether anything else it holds has a place depends on what Lawmatics keeps besides contacts, and the table above shows that kind by kind. What has no place stays where it is or is archived.
A contact list taken from a system that was never a CRM needs work before it is useful. Names are split or joined differently, the same client appears under several spellings, and there is no record of who agreed to be contacted. The list is cleaned and de-duplicated, matched against what Lawmatics already holds, and loaded with a source tag, so the firm can tell these contacts from the ones that came through intake.
Tabs3 Billing 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. Lawmatics 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 Billing
Billing is where a Tabs3 firm’s money history sits. A move takes unbilled fees and costs, open statements, payments, client funds and the receivable ledger, and agrees each to a Tabs3 report at a statement cut-off. The archive of billed transactions is large and is handled as its own decision. Trust and the general ledger are other modules and move alongside.
Work in process and archive
Updating a final statement moves its fees, costs and payments out of the working files into archive files named T3ARCH. So unbilled work is in one place and billed history in another. Unbilled items are loaded as unbilled. The archive is loaded as history only where the destination can hold billed entries without billing them again.
Statements can be undone
Tabs3 can undo an updated statement, which moves its transactions back from the archive to work in process. Before the final extraction, the firm confirms that no statements are waiting to be undone or run again. A statement reversed after the data is taken would leave the two systems disagreeing about what has been billed.
Client funds are not trust
The client funds feature tracks non-refundable retainers and similar money kept in the firm’s general account, apart from the receivable balance. It is a different thing from the Trust Accounting module. Each client funds balance is mapped on purpose, usually to a retainer or credit on the matter, and not to the trust ledger.
Courtesy discounts change history
When a client is billed with a courtesy discount, each archived fee is reduced by its share of the discount. The archive therefore shows fees net of discount, not as first recorded. History loaded elsewhere is compared with Tabs3 on that basis, or the totals look wrong when they are not.
Deleted clients take history
Deleting a client in Tabs3 deletes its archived transactions too. A firm that tidied its client list years ago may hold less history than it expects. The analysis reports the earliest transaction date for each client, so nobody plans around records that are no longer there.
Where it is going
Arriving in Lawmatics
Lawmatics takes matters, contacts and companies from CSV files, and its API accepts notes, tasks, appointments, files, time entries and invoices. It is an intake and client relationship system, so a firm arriving from full practice management has to decide what it is for. People and matters load well. There is no general ledger, and years of billing history have no natural home.
Contacts and matters load separately
The import expects two spreadsheets: one for contacts or companies with no case, such as referrers and other lawyers, and one for matters. A matter import creates the matter and its primary contact together. Every matter has exactly one primary contact, so joint clients are loaded as one primary and one relationship.
Set up before loading
Owner, stage, practice area, source and campaign are matched by name. A value on the spreadsheet that does not match one in Lawmatics exactly creates a new one, which is how a firm ends up with two spellings of the same practice area. Users, pipelines, practice areas and marketing sources are set up first, and custom fields must exist before data is loaded into them.
Statuses and matter numbers
Each imported matter must be PNC (potential new client), Hired or Lost, with open and closed handled as sub-statuses the firm creates. The case number is a system field assigned by an auto-numbering pattern and cannot be edited by hand afterwards. Whether old matter numbers can be loaded into it, or belong in a custom field, is tested in the trial load.
Duplicates are matched by email
With Match Contacts by Email switched on, a contact whose email already exists is skipped or updated, never doubled. Names and phone numbers are not checked. Matters are not deduplicated at all, so two rows with one email create two matters on one contact. Clean-up therefore happens in the spreadsheet, and automations are switched off for every load.
What has no place
There is no general ledger. The Time & Billing module holds time entries, expenses, invoices and a trust account with a running balance per matter, and past invoices are entered as already sent and then marked paid. A firm that needs its full accounting history keeps the old system read only or carries the books in an accounting package.
How NewLaw runs it
Four steps, in this order.
Trust money moves on this route, so the trust cutover gets a rehearsal of its own.
Analysis
We read what Tabs3 Billing holds and how its records link, then agree with you, field by field, where each piece will sit in Lawmatics. Anything with no place there comes across as a note or stays behind, and you see which before the move.
Clean-up
Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Tabs3 Billing, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Lawmatics as a trial and checked against Tabs3 Billing: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Tabs3 Billing are frozen for an agreed window, the data is collected a final time and Lawmatics goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. Tabs3 Billing 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 Billing 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 Billing holds
What is in it, how its records link, and where each piece would sit in Lawmatics. 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
Setting up Lawmatics
Loaded data is not yet a working system. This is what NewLaw sets up in Lawmatics, beyond the migration, so that people can work in it from the first day.
In Lawmatics the design comes before the data. The pipeline stages, practice areas, custom fields and relationship types decide what the import can hold, and the forms and automations decide what the firm’s intake looks like from the first day. If a practice system sits behind it, the field mapping between the two is part of the same job.
Set-up decisions in Lawmatics
- Pipelines and stages for intake and for open matters
- Practice areas, sub-statuses, relationship types and the matter numbering pattern
- Custom fields on matters, contacts and companies
- Intake forms, booking links and e-signature document templates
- Follow-up automations, with marketing sources and campaigns
- Mail and calendar sync, user roles and practice system integration
Questions
Tabs3 Billing to Lawmatics: what firms ask
Can billed fee history be loaded, or only balances?
Open statements and their balances are loaded, because the firm still has to collect them. Whether every billed fee line from the archive comes across depends on the destination: some accept billed time as history, others only take invoice totals. Where detail cannot be loaded, the archive stays readable in Tabs3, which is kept read only.
What about our statement templates?
Statement layouts are built in the Tabs3 Statement Designer and do not open in another product. The firm picks the layouts it still uses, and those are rebuilt as invoice templates in the new system. A side-by-side print of one real client’s bill from each system is the test.
Do timekeeper rates and billing categories move?
Timekeepers, rate tables and transaction codes are extracted as lists and set up in the destination before any time is loaded, because every fee entry refers to them. Client and matter rate exceptions are loaded with the matter. Codes nobody has used in years are left out by agreement.
Do trust balances in Tabs3 Billing have a place in Lawmatics?
In part. A trust account with a running balance; deposits are allocated to a contact and matter. The analysis sets out which trust records have a place in Lawmatics and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.
Does everything in Tabs3 Billing have a place in Lawmatics?
Most of it does on paper. Notes and custom fields could not be confirmed from the two products’ own material, so those are checked in the analysis. Anything that turns out to have no place in Lawmatics is kept as a readable archive, and you see which before the move.
What has to be decided before Tabs3 Billing data is loaded into Lawmatics?
Time entries, billing records, trust ledgers and templates are carried with mapping, so each mapping is agreed with you first. Notes and custom fields are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.
Other routes
Other routes from Tabs3 Billing and into Lawmatics
Other destinations from Tabs3 Billing
Other systems that move into Lawmatics
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 Billing and Lawmatics are the names and marks of their owners, used here only to identify the two systems.
Moving from Tabs3 Billing to Lawmatics?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.