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

Data migration route

Tabs3 Trust Accounting to Litify migration

Tabs3 Trust Accounting is a server-based accounting and billing system, and Litify 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. Notes: Confirmed in the analysis
  4. Trust money: Confirmed in the analysis
  5. Custom fields: Confirmed in the analysis
  6. Templates: Confirmed in the analysis
ToLitifyCloud
  • 2 carried
  • 4 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Tabs3 Trust Accounting to Litify

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

Records in Tabs3 Trust Accounting and their place in Litify
RecordIn Tabs3 Trust AccountingIn LitifyWhat 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 placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeld in partShares client and contact details with Billing and PracticeMaster.Has a placeLoaded as parties and connected by roles.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedTo be confirmedConfirmed in the analysis
Trust moneyTrust or client account ledgers and balancesHeldTrust ledgers, cheques and EFTs, bank reconciliation and a 3-Way Reconciliation Report.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeCustom fields are created before loading.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partTemplates are rebuilt in Litify’s document generation.Confirmed in the analysis

What the plans mean

Carried across
Litify has a place for this kind of record. It is loaded there and checked against Tabs3 Trust Accounting.
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. Litify 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 Litify 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. Litify 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 Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.

  1. The design comes first

    Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.

  2. One party, many roles

    Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.

  3. Open enquiries load as intakes

    Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.

  4. Documents load after records

    Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.

  5. Validation rules reject bad rows

    A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.

More about moving into Litify

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 Litify, they get a rehearsed cutover of their own. The maker of Litify 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 Trust Accounting and checking each trial against Tabs3 Trust Accounting.

  1. Analysis

    We read what Tabs3 Trust Accounting holds and how it is organised, then agree with you where each kind of record will sit in Litify. Anything with no place there stays behind or is archived, and you see which before the move.

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

  3. Trial load

    A trial is loaded into Litify and checked against Tabs3 Trust Accounting: 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.

  4. Cutover

    After a short freeze on changes in Tabs3 Trust Accounting, 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 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 toLitify

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

Loaded data is not yet a working system. The maker of Litify runs or arranges the set-up of its product, so this is what has to be decided and put in place in Litify, whoever does the work, before people rely on it from the first day.

A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.

Set-up decisions in Litify

  • Define intake questionnaires and the rules for conversion
  • Set case types, matter stages and page layouts
  • Build matter plans that create tasks at each stage
  • Design document folders and generation templates per case type
  • Configure user roles and sharing for restricted matters
  • Decide on timekeeping, billing and accounting integrations

Questions

Tabs3 Trust Accounting to Litify: 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 Litify?

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 Trust Accounting before the plan is fixed. If Litify 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 Trust Accounting have a place in Litify?

Most of it does on paper. Notes, trust ledgers, 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 Litify 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 Litify?

Notes, trust ledgers, 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.

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 Litify are the names and marks of their owners, used here only to identify the two systems.

Moving from Tabs3 Trust Accounting to Litify?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.