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

Data migration route

Tabs3 to Box migration

Tabs3 is a server-based practice management system, and Box is cloud file storage. Documents move into a folder for each client and matter, and the data behind them is kept as an export.

FromTabs3Server
  1. Documents: Carried across
  2. Emails: Carried with mapping
  3. Notes: Carried with mapping
  4. Custom fields: Carried with mapping
  5. Templates: Carried with mapping
ToBoxCloud
  1. Matters: Kept as a readable archive
  2. Contacts: Kept as a readable archive
  3. Calendar: Kept as a readable archive
  4. Tasks: Kept as a readable archive
  5. Time and expenses: Kept as a readable archive
  6. Billing: Kept as a readable archive
  7. Trust money: Kept as a readable archive
  8. Firm accounts: Kept as a readable archive
  9. Intake: Kept as a readable archive
Readable archiveNo place in Box
  • 1 carried
  • 4 mapped
  • 9 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Tabs3 to Box

Each row is a kind of record Tabs3 holds, whether Box has a place for it, and what is planned. On this route one kind of record carries across, four kinds need mapping and nine kinds have no place in Box and are archived.

Records in Tabs3 and their place in Box
RecordIn Tabs3In BoxWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeldA matter is the part of the Client ID after the decimal point.No placeA matter is a folder, optionally with metadata; there is no matter record.Kept as a readable archive
ContactsClients, other parties and referrersHeldNo placeKept as a readable archive
DocumentsFiles stored in or linked from the systemHeld in partPracticeMaster links documents to clients and contacts.Has a placeFiles and folders, named and dated as they are loaded.Carried across
EmailsEmails saved to matters or to the storeHeld in partPracticeMaster keeps email records in its Journal.Has a place in partAs .msg or .eml files in the matter folder.Carried with mapping
NotesFile notes, matter notes and contact notesHeld in partNote, phone and research records in the PracticeMaster Journal.Has a place in partAs documents in the matter folder, not as a notes record.Carried with mapping
CalendarAppointments, court dates and deadlinesHeld in partIn PracticeMaster.No placeKept as a readable archive
TasksTo-dos and workflow steps assigned to peopleHeld in partIn PracticeMaster.No placeKept as a readable archive
Time and expensesTime and expense entries, billed and unbilledHeldIn Tabs3 Billing, with timers in PracticeMaster.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldIn Tabs3 Billing.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeld in partWith the Trust Accounting module.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeld in partWith the General Ledger and Accounts Payable modules.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeld in partPracticeMaster Areas of Practice carry the firm’s own files and fields.Has a place in partMetadata templates can hold fields such as matter number and client.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partDocument assembly in PracticeMaster; statement layouts in Billing.Has a place in partPrecedents load as ordinary files; no document automation.Carried with mapping
IntakeLeads, enquiries, intake forms and pipelinesHeld in partTabs3 CRM covers leads and intake and works with PracticeMaster.No placeKept as a readable archive

What the plans mean

Carried across
Box has a place for this kind of record. It is loaded there and checked against Tabs3.
Carried with mapping
Box holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
Kept as a readable archive
Box has no place for it. It is exported in a format that opens without Tabs3 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

Out of the system, into folders the firm can read.

File storage has folders and files and nothing else. Moving from Tabs3 into Box means turning matters into a folder tree, usually client, then matter, then the folders used inside it. The naming rule is agreed first, because it is hard to change once thousands of folders exist: whether the matter number leads, how closed matters are separated, what happens to characters Box does not allow in a name.

Everything that is not a document needs somewhere to go. Contacts, notes, time, invoices and trust ledgers have no place in a folder, so they are exported as spreadsheets and reports and stored alongside, often as a summary file in each matter folder and a full set in an archive area. Firms choose this route to keep a readable copy of a system they are retiring, or as a staging step. The export is checked either way: folders against matters, files against the document register in Tabs3.

Tabs3 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. Box 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

The first question for a firm on Tabs3 is which modules it owns, because each one is a different set of records. Billing holds time, fees and receivables. PracticeMaster holds contacts, calendar, documents and the journal. Trust, payables and the ledger are separate programs again. All of them share the Client ID, which is what ties a move together.

  1. One ID for client and matter

    A Client ID is up to twelve characters including a decimal point. The part before the point is the client and the part after is the matter. Firms chose a numeric, alphabetic or mixed key type at set-up, and how many decimal places to allow. The ID is split on the way out and both halves are kept.

  2. Everything in one directory

    The modules integrate only when installed in the same directory, which the software calls the current working directory. Its data is a set of DAT and IDX files there. A complete copy of that directory, taken with all users out, is the source for every trial load.

  3. Standard and Platinum

    The Platinum edition adds a server component with scheduled HotBackup and SQL access to the data, and the standard edition has neither. Which edition the firm runs changes how a consistent copy is taken and what can read it, so it is established in the first conversation.

  4. Figures that are not stored

    The vendor’s own help notes that accounts receivable and work in process are calculated from ledger and fee records, not held as fields. So balances cannot be lifted out as a column. They are rebuilt from the transactions and then agreed to the reports the firm prints.

  5. Cloud or server

    Firms on Tabs3 Cloud use the suite as hosted by the vendor, and some on-premises firms run it with one of the vendor’s hosting partners. Where the files are, and who is able to copy them, is settled before a cutover date is set.

More about moving off Tabs3

Where it is going

Loading a firm’s files into Box means deciding the folder tree and its owners first, because permissions follow the tree. Box has no matter record. A matter is a folder, and anything else the firm knew about it, such as the matter number, client or status, survives only in the folder name or in metadata fields set up before the load.

  1. Decide who owns the top level

    Box’s own planning guidance sets out two models: users create their own top-level folders, or administrators own them all and invite people in. For matter files most later decisions depend on this one, including who can share outside the firm and whose storage allowance the files count against.

  2. Restricted matters go near the top

    Access in Box only flows downward. A person who can open a client folder can open every matter under it, and a subfolder cannot be hidden from them. Matters behind an information barrier therefore need their own top-level folders, and the list of those matters is agreed before the structure is built.

  3. Names Box will not accept

    Box rejects a slash or backslash anywhere in a file or folder name, and spaces at the start or end. Files from older systems and from Macs often have both. They are renamed by rule before loading and the firm receives the list, so that a document cited by its old name can still be found.

  4. Matter details become metadata

    A metadata template can hold the matter number, client name, practice area and closed date against each matter folder. The template has to exist before the files arrive so the values can be written during the load. Without it, the folder name is the only place that information lives.

  5. File size follows the owner’s plan

    The largest file Box accepts depends on the plan of whoever owns the folder. Litigation matters with video or forensic images are where this bites. Oversized files are found in the analysis, and the firm chooses between a higher plan and keeping those files somewhere else.

More about moving into Box

How NewLaw runs it

Four steps, in this order.

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

  1. Analysis

    We read what Tabs3 holds and how it is organised, then agree with you where each kind of record will sit in Box. 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 Box and checked against Tabs3: 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, a final pass over a weekend picks up what changed since the trial. Tabs3 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 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
Moving toBox

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 holds

    What is in it, how its records link, and where each piece would sit in Box. 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

Box is 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.

Most of a Box set-up is governance. The folder tree, the groups that are invited into it and the rules on sharing outside the firm are decided and built before any file is loaded. After the load, staff need Box Drive on their PCs and a short written guide to where a new matter folder is created and who creates it.

What is agreed and set up

  • Top-level folder structure and who owns each folder
  • Groups for teams, mapped to collaborator roles
  • Metadata template for matter number, client and status
  • Shared link defaults and rules for external collaborators
  • Box Drive installed and signed in on each PC
  • Version limits and retention agreed with the firm’s records policy

Questions

Tabs3 to Box: what firms ask

We only have Tabs3 Billing and PracticeMaster. Is that a problem?

No. It means trust and the general ledger are kept in some other program, and that program is added to the plan. The move covers what Tabs3 holds, and the analysis names the other systems that have to agree with it at cutover.

Can we keep the client dot matter numbering?

If the destination allows a firm-set matter number, the full ID can be kept as it is, decimal point included. Where clients and matters are numbered separately, the two halves go into their own fields. Either way the original ID stays searchable, because it is printed on years of statements.

How are the modules extracted together?

From one copy of the working directory, taken at one moment, so billing, trust and ledger all describe the same day. Taking them at different times is how totals end up disagreeing. For the final cutover the copy is taken after month-end procedures are run and before anyone posts again.

Do trust balances in Tabs3 have a place in Box?

No. Box does not keep trust ledgers. Trust records from Tabs3 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 Box has no place for?

On this route that is matters, contacts, calendar entries, tasks, time entries, billing records, trust ledgers, the firm’s accounts and intake records. They are exported from Tabs3 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 data is loaded into Box?

Emails, notes, custom fields and templates are carried with mapping, so each mapping is agreed with you first. 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 and Box are the names and marks of their owners, used here only to identify the two systems.

Moving from Tabs3 to Box?

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

We reply within one business day.