Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

Tabs3 Trust Accounting to Filevine migration

Tabs3 Trust Accounting is a server-based accounting and billing system, and Filevine is a cloud case management system. Only part of what Tabs3 Trust Accounting holds has a place in a case file: clients and jobs move, and the table shows how much of the billing side does.

FromTabs3 Trust AccountingServer
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Trust money: Carried with mapping
  4. Notes: Confirmed in the analysis
  5. Custom fields: Confirmed in the analysis
  6. Templates: Confirmed in the analysis
ToFilevineCloud
  • 2 carried
  • 1 mapped
  • 3 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Tabs3 Trust Accounting to Filevine

Each row is a kind of record Tabs3 Trust Accounting holds, whether Filevine has a place for it, and what is planned. On this route two kinds of record carry across, one kind needs mapping and three kinds are confirmed in the analysis.

Records in Tabs3 Trust Accounting and their place in Filevine
RecordIn Tabs3 Trust AccountingIn FilevineWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partTrust accounts are keyed by a Trust ID in the same format as client numbers.Has a placeLoaded as projects of a defined project type.Carried across
ContactsClients, other parties and referrersHeld in partShares client and contact details with Billing and PracticeMaster.Has a placeContact cards, linked to projects.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeHeld as notes in the activity feed.Confirmed in the analysis
Trust moneyTrust or client account ledgers and balancesHeldTrust ledgers, cheques and EFTs, bank reconciliation and a 3-Way Reconciliation Report.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 itselfTo be confirmedHas a placeCustom sections and fields per project type.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas 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 Trust Accounting.
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 Trust Accounting 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 Trust Accounting as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If Tabs3 Trust Accounting 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 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. 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

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving off Tabs3 Trust Accounting

Where it is going

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving into Filevine

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.

  1. Analysis

    We read what Tabs3 Trust Accounting 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.

  2. Clean-up

    Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Tabs3 Trust Accounting, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into Filevine as a trial and checked against Tabs3 Trust Accounting: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Tabs3 Trust Accounting 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 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

Step 1 of 5: Start with the route

Moving fromTabs3 Trust Accounting
Moving toFilevine

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what Tabs3 Trust Accounting 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.

  3. 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 Trust Accounting to Filevine: 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 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 Trust Accounting have a place in Filevine?

Most of it does on paper. Notes, 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 Trust Accounting data is loaded into Filevine?

Trust ledgers 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 sets the cutover date and how much financial history comes across as live records.

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.

How we do itDiscovery to rollout, step by step

Tabs3 Trust Accounting and Filevine are the names and marks of their owners, used here only to identify the two systems.

Moving from Tabs3 Trust Accounting 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.