Data migration route
Tabs3 Billing to Filevine migration
Tabs3 Billing is a server-based accounting and billing system, and Filevine is a cloud case management system. 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 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
FilevineCloud- 2 carried
- 4 mapped
- 2 to confirm
What moves
What moves from Tabs3 Billing to Filevine
Each row is a kind of record Tabs3 Billing holds, whether Filevine 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 as projects of a defined project type. | Carried across |
| ContactsClients, other parties and referrers | Held in partClient names and addresses; fuller contact records are in PracticeMaster. | Has a placeContact cards, linked to projects. | Carried across |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeHeld as notes in the activity feed. | 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 partNeeds the Billing product enabled. | Carried with mapping |
| BillingInvoices, payments and debtor balances | HeldDraft and final statements, payments and a client ledger. | Has a place in partNeeds the Billing product enabled. | 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 partTrust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis. | Carried with mapping |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeCustom sections and fields per project type. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | HeldStatement layouts built in the Statement Designer. | Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted. | Carried with mapping |
What the plans mean
- Carried across
- Filevine has a place for this kind of record. It is loaded there and checked against Tabs3 Billing.
- Carried with mapping
- Filevine 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. Filevine 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 Filevine 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. Filevine 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 Filevine
Loading a firm into Filevine depends on the project types being built first. Until the sections and fields exist there is nowhere for the data to go, so configuration and migration are planned together. The old system’s parties, insurers, providers and key dates are mapped to sections, and its notes and emails are loaded into each project’s activity feed.
Project types before data
Each area of practice needs a project type with its sections, fields and phases defined in the Customs Editor. Changes made there apply to every project of that type. The types are drafted from the old system’s data, tested with a few real cases, and only then is the bulk load run.
One contact card per person
Contacts are held as contact cards. A doctor or adjuster who appears on many projects is best loaded as one card, not one for each project. Duplicates in the old system are merged before loading where they can be identified. Loading them as they are produces several cards for the same person, and staff then pick the wrong one when adding a party.
Lists become collection items
Anything the old system held as a list against a matter, such as providers, liens, insurance policies or expenses, is loaded as items in a collection section. Each column needs a matching field. Totals per project are compared with the old system afterwards, since those figures feed the settlement and disbursal sheets.
History goes into the feed
File notes, emails and completed tasks from the old system are loaded into the activity feed with their original dates and authors. Authors must exist as users or be recorded in the text. The feed is long on an old case, so staff are shown how to filter it before go-live.
Billing is a separate switch
The Billing section only appears once Billing is enabled for the firm. Time entries, invoices and trust balances from the old system need that in place before they can be loaded. A firm that leaves it off can still record case costs in a collection section built for the purpose.
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 Filevine. 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 Filevine 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 Filevine 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 Filevine. 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 Filevine
Loaded data is not yet a working system. This is what NewLaw sets up in Filevine, beyond the migration, so that people can work in it from the first day.
Filevine arrives as a platform to be configured, and most of the implementation is design. Someone has to decide what a project looks like for each kind of work the firm does, what moves it from one phase to the next, and who can see what. Those decisions are made with the people who run the files, then built and tested.
Set-up decisions in Filevine
- Design project types, sections and fields for each practice area
- Define phases and the tasks each phase should trigger
- Build document templates that fill from project fields
- Set teams, permissions and protected sections for restricted matters
- Decide whether Billing and Payments are switched on
- Connect Lead Docket so signed leads become projects
Questions
Tabs3 Billing to Filevine: 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 Filevine?
In part. Trust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis. The analysis sets out which trust records have a place in Filevine 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 Filevine?
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 Filevine 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 Filevine?
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 Filevine
Other destinations from Tabs3 Billing
Other systems that move into Filevine
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 Filevine are the names and marks of their owners, used here only to identify the two systems.
Moving from Tabs3 Billing to Filevine?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.