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

Data migration route

Tabs3 Billing to Server drives migration

Tabs3 Billing 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 BillingServer
  1. Templates: Carried with mapping
  2. Notes: Confirmed in the analysis
  3. Custom fields: Confirmed in the analysis
ToServer drivesFiles
  1. Matters: Kept as a readable archive
  2. Contacts: Kept as a readable archive
  3. Time and expenses: Kept as a readable archive
  4. Billing: Kept as a readable archive
  5. Trust money: Kept as a readable archive
Readable archiveNo place in Server drives
  • 1 mapped
  • 2 to confirm
  • 5 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Tabs3 Billing to Server drives

Each row is a kind of record Tabs3 Billing holds, whether Server drives have a place for it, and what is planned. On this route one kind needs mapping, five kinds have no place in Server drives and are archived and two kinds are confirmed in the analysis.

Records in Tabs3 Billing and their place in Server drives
RecordIn Tabs3 BillingIn Server drivesWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldEach matter is a Client ID; the digits after the decimal point are the matter.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 partClient names and addresses; fuller contact records are in 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
Time and expensesTime and expense entries, billed and unbilledHeldFees with hours worked and hours to bill, plus costs.No placeOnly as exported reports or spreadsheets.Kept as a readable archive
BillingInvoices, payments and debtor balancesHeldDraft and final statements, payments and a client ledger.Has a place in partInvoices as PDF files; no ledger.Kept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeld in partClient funds for retainers; trust ledgers are in the Trust Accounting module.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 automationHeldStatement layouts built in the Statement Designer.Has a place in partPrecedents as Word files; merge fields tied to the old system stop working.Carried with mapping

What the plans mean

Carried with mapping
Server drives 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.
Kept as a readable archive
Server drives has no place for it. It is exported in a format that opens without Tabs3 Billing 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 Billing 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 Billing, 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 Billing stays untouched until the copy in Server drives has been checked.

Where the data is now

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.

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

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

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

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

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

More about moving off Tabs3 Billing

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 Billing 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 Billing: 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 Billing, a final pass over a weekend picks up what changed since the trial. 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

Step 1 of 5: Start with the route

Moving fromTabs3 Billing
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 Billing 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 Billing to Server drives: 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 Server drives?

No. Server drives do not keep trust ledgers. Only as exported ledger reports kept as files. Trust records from Tabs3 Billing 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, time entries, billing records and trust ledgers. They are exported from Tabs3 Billing 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 Billing data is loaded into Server drives?

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

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