Data migration route
Tabs3 Accounts Payable to Filevine migration
Tabs3 Accounts Payable is a server-based accounting and billing system, and Filevine is a cloud case management system. Only part of what Tabs3 Accounts Payable holds has a place in a case file: clients and jobs move, and the table shows how much of the billing side does.
Tabs3 Accounts PayableServer- Contacts: Carried across
- Notes: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
- Templates: Confirmed in the analysis
FilevineCloud- 1 carried
- 4 to confirm
What moves
What moves from Tabs3 Accounts Payable to Filevine
Each row is a kind of record Tabs3 Accounts Payable holds, whether Filevine has a place for it, and what is planned. On this route one kind of record carries across and four kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| ContactsClients, other parties and referrers | Held in partVendors. | 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 |
| Firm accountsGeneral ledger, office account and payables | HeldVendor invoices, cheques and EFTs, recurring entries and 1099s; posts to Tabs3 General Ledger. | To be confirmed | Confirmed in the analysis |
| 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 | To be confirmed | Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted. | Confirmed in the analysis |
What the plans mean
- Carried across
- Filevine has a place for this kind of record. It is loaded there and checked against Tabs3 Accounts Payable.
- 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 Accounts Payable 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 Accounts Payable as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If Tabs3 Accounts Payable 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 Accounts Payable 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 Accounts Payable
Payables is a small module with a narrow job, and moving it is mostly a question of where it goes. Few practice management systems pay suppliers, so the vendor list, unpaid invoices and recurring bills usually land in the firm’s accounting package. What has to be right on the day is the list of unpaid invoices and the payables balance in the ledger.
It rarely has a twin
Practice systems mostly leave supplier bills to Xero, QuickBooks or a similar package. So this module’s data usually goes to a different destination from the matters. The analysis names that destination, and the vendor list is set up there before unpaid invoices are loaded against it.
Unposted items
Invoices and cheques are entered first and posted to the general ledger later, by running the post programs. Anything entered but not yet posted is in payables and not in the ledger. All postings are run before the final extraction, so the unpaid invoice list and the ledger’s payables account agree.
Vendor numbers and key length
Vendors are numbered, and the firm set the key length in the module’s customisation. Other accounting packages identify suppliers by name or by their own code. The Tabs3 vendor number is kept as a reference on each supplier, so earlier payments can still be traced back.
Recurring entries
Rent, subscriptions and other regular bills are stored as recurring entries that the firm posts each period. They are not invoices yet, so they do not appear on the unpaid list. Each one is recreated as a recurring bill in the destination, with its next due date checked against the last one posted in Tabs3.
1099 totals mid-year
The module produces 1099 forms from the year’s vendor payments and can combine them with trust payees. If the move happens during a tax year, year-to-date payments per vendor are carried across as figures, so the forms can be produced from one place in January.
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.
No financial cutover is planned on this route, so a load can be run again until it is right. If the analysis finds financial records with a place in Filevine, they get a rehearsed cutover of their own.
Analysis
We read what Tabs3 Accounts Payable holds and how it is organised, then agree with you where each kind of record will sit in Filevine. 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 Filevine and checked against Tabs3 Accounts Payable: 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
After a short freeze on changes in Tabs3 Accounts Payable, a final pass over a weekend picks up what changed since the trial. If the analysis found financial records to move, their cutover is rehearsed on a full trial load first. Tabs3 Accounts Payable 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 Accounts Payable 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 Accounts Payable 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 Accounts Payable to Filevine: what firms ask
Do paid invoices need to come across?
Usually not as transactions. Paid supplier invoices are already reflected in the ledger balances. Firms keep the paid history readable in Tabs3 and carry over open invoices, the vendor list and the current year’s payment totals. If the accountant wants prior-year detail in the new package, that is agreed during the analysis.
Where do client costs paid through payables go?
A supplier invoice for a client’s matter is both a payable and a cost to recover. In the new set-up the supplier side goes to the accounting package and the recoverable cost goes to the matter as an unbilled disbursement. Open items are checked on both sides, so none is paid twice or left unbilled.
Can payables move before the rest of Tabs3?
It can, because suppliers do not depend on the matter data. Where the module is integrated with Tabs3 General Ledger, though, every invoice and cheque posts there. If the ledger is moving to a new package, payables moves with it at the same period end, or someone posts by hand in between.
Do contacts from Tabs3 Accounts Payable arrive in Filevine without duplicates?
Filevine has a place for contacts. Contact cards, linked to projects. Duplicates are merged in Tabs3 Accounts Payable before extraction where they can be identified, and the list is matched against contacts already in Filevine. It is not always possible to find every one, so some may carry across.
Does everything in Tabs3 Accounts Payable have a place in Filevine?
Most of it does on paper. Notes, the firm’s accounts, custom fields and templates 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 Accounts Payable data is loaded into Filevine?
Notes, the firm’s accounts, 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 Accounts Payable and into Filevine
Other destinations from Tabs3 Accounts Payable
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 Accounts Payable and Filevine are the names and marks of their owners, used here only to identify the two systems.
Moving from Tabs3 Accounts Payable 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.