Data migration route
Tabs3 Billing to SmartAdvocate migration
Tabs3 Billing is a server-based accounting and billing system, and SmartAdvocate is a cloud case management system for personal injury work. Only part of what Tabs3 Billing holds has a place in a case file: clients and jobs move, and the table shows how much of the billing side does.
Tabs3 BillingServer- Matters: Carried across
- Contacts: Carried across
- Time and expenses: Carried across
- Billing: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
SmartAdvocateCloud- 3 carried
- 2 mapped
- 3 to confirm
What moves
What moves from Tabs3 Billing to SmartAdvocate
Each row is a kind of record Tabs3 Billing holds, whether SmartAdvocate has a place for it, and what is planned. On this route three kinds of record carry across, two kinds need mapping and three 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 placeCases by case type, with master and member relationships. | Carried across |
| ContactsClients, other parties and referrers | Held in partClient names and addresses; fuller contact records are in PracticeMaster. | Has a place | Carried across |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place | 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 placeTracked time entries. | Carried across |
| BillingInvoices, payments and debtor balances | HeldDraft and final statements, payments and a client ledger. | Has a place in partInvoices for hourly matters. Past invoices are scoped in the analysis. | 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. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a place in partConfirmed in the analysis for each field with no standard home. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldStatement layouts built in the Statement Designer. | Has a place in partTemplates are rebuilt with SmartAdvocate merge codes. | Carried with mapping |
What the plans mean
- Carried across
- SmartAdvocate has a place for this kind of record. It is loaded there and checked against Tabs3 Billing.
- Carried with mapping
- SmartAdvocate 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
Clients and jobs move. The books stay books.
An accounting or billing system and a case management system overlap less than firms expect. Tabs3 Billing knows clients, jobs, time and invoices. SmartAdvocate knows cases, parties, documents and deadlines. The client list moves well, and jobs can seed the case list. Time and invoice history has a place only where the case system has a billing side, and the table above shows whether this one does. A general ledger does not belong in a case system.
So the plan has two halves. Records with a place in SmartAdvocate are loaded and checked there. The rest is exported from Tabs3 Billing as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If Tabs3 Billing is staying as the accounting system, nothing financial needs to move at all, and the job is to line up client and case numbers so the two can be reconciled.
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. SmartAdvocate 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 SmartAdvocate
SmartAdvocate keeps injury detail in structured fields and screens, so mapping counts for more than usual: the more precisely the old data is placed, the more of those screens are filled on the first day. Parties, incidents, insurers, providers and bills are loaded to their own screens, and the vendor’s implementation team runs conversions into it.
Map to fields, not notes
The case summary, dashboards and settlement screen read from structured fields. Injury details, insurance limits and provider bills dumped into a note leave those screens empty. The mapping takes each old field to its SmartAdvocate counterpart, and only what truly has no counterpart is loaded as a note.
Case types and statuses
Cases are loaded against case types and statuses that drive WorkPlans and reports. These are agreed with the firm before the trial load, and old statuses are translated to the new list. A status with no match is not guessed at. It is listed, and someone who knows the files decides.
Document categories
Documents are searched by category, subcategory, sender, recipient and date as well as by folder. The old system’s folders are translated into categories on the way in. Files that arrive uncategorised can still be found by description, but they fall outside the category views staff are trained to use.
Working with the vendor’s conversion
SmartAdvocate’s implementation team converts client data into the system and trains staff through its own classes. The firm’s side of that is supplying a clean source, checking the converted cases against the old system, and deciding what to do with the exceptions. Independent help is used on those tasks.
Choosing Server or Cloud
The firm decides before loading whether it will run the Server edition on its own Windows server or use the hosted Cloud edition. Either way the data load is the same. What differs is who looks after backups, updates and remote access afterwards, and that is settled with the firm’s IT provider.
How NewLaw runs it
Four steps, in this order.
Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of SmartAdvocate says that it, or its partners, load firms into the product. Where the firm uses that service, NewLaw’s part is the work around it: the analysis, the clean-up in Tabs3 Billing and checking each trial against Tabs3 Billing.
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 SmartAdvocate. 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 SmartAdvocate as a trial and checked against Tabs3 Billing: record counts, financial 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 SmartAdvocate goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in Tabs3 Billing as at the cutover date. 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 SmartAdvocate. 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 SmartAdvocate
Loaded data is not yet a working system. The maker of SmartAdvocate runs or arranges the set-up of its product, so this is what has to be decided and put in place in SmartAdvocate, whoever does the work, before people rely on it from the first day.
Setting up SmartAdvocate is a matter of deciding how much of its detail the firm will use from the start. Case types, statuses and WorkPlans come first because they drive everything else. Templates follow. The vendor trains staff through its own classes, and the decisions below are best made before the first of those.
Set-up decisions in SmartAdvocate
- Choose the Server or Cloud edition with IT
- Define case types, statuses and staff roles
- Build WorkPlans and Automated Procedures for each case type
- Convert letters and forms into templates with merge codes
- Install the Outlook plugin and agree email filing habits
- Set up intake screens, lead sources and dashboards
Questions
Tabs3 Billing to SmartAdvocate: 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 SmartAdvocate?
That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in Tabs3 Billing before the plan is fixed. If SmartAdvocate turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.
Does everything in Tabs3 Billing have a place in SmartAdvocate?
Most of it does on paper. Notes, trust ledgers 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 SmartAdvocate 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 SmartAdvocate?
Billing records and templates are carried with mapping, so each mapping is agreed with you first. Notes, trust ledgers 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 SmartAdvocate
Other destinations from Tabs3 Billing
Other systems that move into SmartAdvocate
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 SmartAdvocate are the names and marks of their owners, used here only to identify the two systems.
Moving from Tabs3 Billing to SmartAdvocate?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.