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

Data migration route

Tabs3 Accounts Payable to SmartAdvocate migration

Tabs3 Accounts Payable is a server-based accounting and billing system, and SmartAdvocate is a cloud case management system for personal injury work. Only part of what Tabs3 Accounts Payable holds has a place in a case file: clients and jobs move, and the table shows how much of the billing side does.

FromTabs3 Accounts PayableServer
  1. Contacts: Carried across
  2. Notes: Confirmed in the analysis
  3. Firm accounts: Confirmed in the analysis
  4. Custom fields: Confirmed in the analysis
  5. Templates: Confirmed in the analysis
ToSmartAdvocateCloud
  • 1 carried
  • 4 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Tabs3 Accounts Payable to SmartAdvocate

Each row is a kind of record Tabs3 Accounts Payable holds, whether SmartAdvocate has a place for it, and what is planned. On this route one kind of record carries across and four kinds are confirmed in the analysis.

Records in Tabs3 Accounts Payable and their place in SmartAdvocate
RecordIn Tabs3 Accounts PayableIn SmartAdvocateWhat is planned
ContactsClients, other parties and referrersHeld in partVendors.Has a placeCarried across
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldVendor invoices, cheques and EFTs, recurring entries and 1099s; posts to Tabs3 General Ledger.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a place in partConfirmed in the analysis for each field with no standard home.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partTemplates are rebuilt with SmartAdvocate merge codes.Confirmed in the analysis

What the plans mean

Carried across
SmartAdvocate has a place for this kind of record. It is loaded there and checked against Tabs3 Accounts Payable.
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 Accounts Payable knows clients, jobs, time and invoices. SmartAdvocate 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 SmartAdvocate are loaded and checked there. The rest is exported from Tabs3 Accounts Payable as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If Tabs3 Accounts Payable 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 Accounts Payable 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. SmartAdvocate 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

Payables is a small module with a narrow job, and moving it is mostly a question of where it goes. Few practice management systems pay suppliers, so the vendor list, unpaid invoices and recurring bills usually land in the firm’s accounting package. What has to be right on the day is the list of unpaid invoices and the payables balance in the ledger.

  1. It rarely has a twin

    Practice systems mostly leave supplier bills to Xero, QuickBooks or a similar package. So this module’s data usually goes to a different destination from the matters. The analysis names that destination, and the vendor list is set up there before unpaid invoices are loaded against it.

  2. Unposted items

    Invoices and cheques are entered first and posted to the general ledger later, by running the post programs. Anything entered but not yet posted is in payables and not in the ledger. All postings are run before the final extraction, so the unpaid invoice list and the ledger’s payables account agree.

  3. Vendor numbers and key length

    Vendors are numbered, and the firm set the key length in the module’s customisation. Other accounting packages identify suppliers by name or by their own code. The Tabs3 vendor number is kept as a reference on each supplier, so earlier payments can still be traced back.

  4. Recurring entries

    Rent, subscriptions and other regular bills are stored as recurring entries that the firm posts each period. They are not invoices yet, so they do not appear on the unpaid list. Each one is recreated as a recurring bill in the destination, with its next due date checked against the last one posted in Tabs3.

  5. 1099 totals mid-year

    The module produces 1099 forms from the year’s vendor payments and can combine them with trust payees. If the move happens during a tax year, year-to-date payments per vendor are carried across as figures, so the forms can be produced from one place in January.

More about moving off Tabs3 Accounts Payable

Where it is going

SmartAdvocate keeps injury detail in structured fields and screens, so mapping counts for more than usual: the more precisely the old data is placed, the more of those screens are filled on the first day. Parties, incidents, insurers, providers and bills are loaded to their own screens, and the vendor’s implementation team runs conversions into it.

  1. Map to fields, not notes

    The case summary, dashboards and settlement screen read from structured fields. Injury details, insurance limits and provider bills dumped into a note leave those screens empty. The mapping takes each old field to its SmartAdvocate counterpart, and only what truly has no counterpart is loaded as a note.

  2. Case types and statuses

    Cases are loaded against case types and statuses that drive WorkPlans and reports. These are agreed with the firm before the trial load, and old statuses are translated to the new list. A status with no match is not guessed at. It is listed, and someone who knows the files decides.

  3. Document categories

    Documents are searched by category, subcategory, sender, recipient and date as well as by folder. The old system’s folders are translated into categories on the way in. Files that arrive uncategorised can still be found by description, but they fall outside the category views staff are trained to use.

  4. Working with the vendor’s conversion

    SmartAdvocate’s implementation team converts client data into the system and trains staff through its own classes. The firm’s side of that is supplying a clean source, checking the converted cases against the old system, and deciding what to do with the exceptions. Independent help is used on those tasks.

  5. Choosing Server or Cloud

    The firm decides before loading whether it will run the Server edition on its own Windows server or use the hosted Cloud edition. Either way the data load is the same. What differs is who looks after backups, updates and remote access afterwards, and that is settled with the firm’s IT provider.

More about moving into SmartAdvocate

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

  1. Analysis

    We read what Tabs3 Accounts Payable holds and how it is organised, then agree with you where each kind of record will sit in SmartAdvocate. 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 SmartAdvocate and checked against Tabs3 Accounts Payable: 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 Accounts Payable, 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 Accounts Payable 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 Accounts Payable 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 Accounts Payable
Moving toSmartAdvocate

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 Accounts Payable holds

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

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

Setting up SmartAdvocate is a matter of deciding how much of its detail the firm will use from the start. Case types, statuses and WorkPlans come first because they drive everything else. Templates follow. The vendor trains staff through its own classes, and the decisions below are best made before the first of those.

Set-up decisions in SmartAdvocate

  • Choose the Server or Cloud edition with IT
  • Define case types, statuses and staff roles
  • Build WorkPlans and Automated Procedures for each case type
  • Convert letters and forms into templates with merge codes
  • Install the Outlook plugin and agree email filing habits
  • Set up intake screens, lead sources and dashboards

Questions

Tabs3 Accounts Payable to SmartAdvocate: what firms ask

Do paid invoices need to come across?

Usually not as transactions. Paid supplier invoices are already reflected in the ledger balances. Firms keep the paid history readable in Tabs3 and carry over open invoices, the vendor list and the current year’s payment totals. If the accountant wants prior-year detail in the new package, that is agreed during the analysis.

Where do client costs paid through payables go?

A supplier invoice for a client’s matter is both a payable and a cost to recover. In the new set-up the supplier side goes to the accounting package and the recoverable cost goes to the matter as an unbilled disbursement. Open items are checked on both sides, so none is paid twice or left unbilled.

Can payables move before the rest of Tabs3?

It can, because suppliers do not depend on the matter data. Where the module is integrated with Tabs3 General Ledger, though, every invoice and cheque posts there. If the ledger is moving to a new package, payables moves with it at the same period end, or someone posts by hand in between.

Do contacts from Tabs3 Accounts Payable arrive in SmartAdvocate without duplicates?

SmartAdvocate has a place for contacts. Duplicates are merged in Tabs3 Accounts Payable before extraction where they can be identified, and the list is matched against contacts already in SmartAdvocate. It is not always possible to find every one, so some may carry across.

Does everything in Tabs3 Accounts Payable have a place in SmartAdvocate?

Most of it does on paper. Notes, the firm’s accounts, 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 SmartAdvocate is kept as a readable archive, and you see which before the move.

What has to be decided before Tabs3 Accounts Payable data is loaded into SmartAdvocate?

Notes, the firm’s accounts, 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 Accounts Payable and SmartAdvocate are the names and marks of their owners, used here only to identify the two systems.

Moving from Tabs3 Accounts Payable to SmartAdvocate?

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

We reply within one business day.