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

Data migration route

Tabs3 Trust Accounting to Server drives migration

Tabs3 Trust Accounting is a server-based accounting and billing system, and Server drives are plain files on equipment the firm controls. What moves is the files, plus a readable export of everything else the old system holds.

FromTabs3 Trust AccountingServer
  1. Notes: Confirmed in the analysis
  2. Custom fields: Confirmed in the analysis
  3. Templates: Confirmed in the analysis
ToServer drivesFiles
  1. Matters: Kept as a readable archive
  2. Contacts: Kept as a readable archive
  3. Trust money: Kept as a readable archive
Readable archiveNo place in Server drives
  • 3 to confirm
  • 3 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Tabs3 Trust Accounting to Server drives

Each row is a kind of record Tabs3 Trust Accounting holds, whether Server drives have a place for it, and what is planned. On this route three kinds have no place in Server drives and are archived and three kinds are confirmed in the analysis.

Records in Tabs3 Trust Accounting and their place in Server drives
RecordIn Tabs3 Trust AccountingIn Server drivesWhat 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.No placeA matter becomes a folder; its details survive only in an index file.Kept as a readable archive
ContactsClients, other parties and referrersHeld in partShares client and contact details with Billing and PracticeMaster.No placeCan be kept only as an exported spreadsheet.Kept as a readable archive
NotesFile notes, matter notes and contact notesTo be confirmedHas a place in partAs a text or PDF file per matter, not as separate records.Confirmed in the analysis
Trust moneyTrust or client account ledgers and balancesHeldTrust ledgers, cheques and EFTs, bank reconciliation and a 3-Way Reconciliation Report.No placeOnly as exported ledger reports kept as files.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedNo placeConfirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partPrecedents as Word files; merge fields tied to the old system stop working.Confirmed in the analysis

What the plans mean

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.
Kept as a readable archive
Server drives has no place for it. It is exported in a format that opens without Tabs3 Trust Accounting and handed to the firm as a read-only archive.

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

An export the firm can open without the system.

Server drives hold files, and most of what Tabs3 Trust Accounting holds is records. This route is therefore an export job. Each kind of record is written out in a format that opens without the system it came from: lists as spreadsheets, statements and invoices as PDFs, attachments as the files they were. The export is laid out in folders that make sense to someone who never used Tabs3 Trust Accounting, by client or by year, with a short index file saying what is where.

Firms do this when a subscription is ending, when a system is being retired, or to meet a retention rule. The test of the result is whether a question can still be answered from it years later: what was this client invoiced, who signed this agreement and when. So the trial export is checked by asking those questions of it. Totals are agreed to the system’s own reports, and access to the folder in Server drives is limited before the export is copied in.

Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in Tabs3 Trust Accounting stays untouched until the copy in Server drives has been checked.

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

Some firms leave a practice or document system and keep their documents on a server drive, either as the working store or as the archive of a system being switched off. The files will arrive without the database that described them. Everything the firm wants to keep knowing about a document has to be put into its path, its name or an index file.

  1. Agree the tree and the names

    A fixed pattern is chosen, for example client name and number, then matter number and short description, then a standard set of subfolders. Document titles from the old system become file names. Where two documents share a title, a date or sequence number is added so nothing is overwritten.

  2. Budget the path length

    Share name, client, matter, subfolder and file name all count towards the 260 character limit that many Windows programs still apply. The pattern is tested against the firm’s longest client names and document titles before the load. Descriptions are trimmed by rule, never by cutting off the file extension.

  3. Dates have to be set deliberately

    A file written to the server today is dated today unless its modified date is set from the old system’s record. Document dates are how lawyers find things in a folder. Which date each file is to carry is agreed in the analysis, and the trial load checks a sample.

  4. Emails become message files

    Emails filed to matters in the old system are written out as .msg or .eml files in a correspondence folder, named by date, sender and subject so they sort in order. Attachments stay inside the message. Subjects with characters Windows forbids are cleaned, and long ones cut.

  5. Keep an index beside the files

    A spreadsheet or small database listing every document with its matter, author, original date, document type and new path is the only place the old system’s profile data survives. It lets someone find a document by something other than its name. What the index records, and who keeps it, is decided in the analysis.

More about moving into Server drives

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Server drives on this route, which makes it repeatable: a load can be run again until it is right.

  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 Server drives. 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 Server drives 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

    There is no financial cutover on this route. After a short freeze on changes in Tabs3 Trust Accounting, a final pass over a weekend picks up what changed since the trial. 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 toServer drives

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 Server drives. 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

Structure, permissions and handover

Server drives are storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.

A server drive does only what the firm and its IT provider make it do. Setting one up as a document store means building the share, deciding who can open which folders, and arranging the protections a document system would have supplied: backups, earlier versions and a way to recover a deleted folder. The filing rule is written down and taught.

What is agreed and set up

  • Share and top-level folders for clients, precedents and administration
  • Security groups and folder permissions, with restricted matters separate
  • Drive letter mapped for every user at sign-in
  • Backup schedule and shadow copies for earlier versions
  • Written naming rule for client, matter and document names
  • Read-only area for closed matters and archived system exports

Questions

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

No. Server drives do not keep trust ledgers. Only as exported ledger reports kept as files. Trust records from Tabs3 Trust Accounting are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.

What happens to records Server drives have no place for?

On this route that is matters, contacts and trust ledgers. They are exported from Tabs3 Trust Accounting in formats that open without it, spreadsheets and PDFs, and handed to the firm as a read-only archive. You see the list before the move.

What has to be decided before Tabs3 Trust Accounting data is loaded into Server drives?

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

Moving from Tabs3 Trust Accounting to Server drives?

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

We reply within one business day.