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

Data migration route

Tabs3 Accounts Payable to SimpleLaw migration

Tabs3 Accounts Payable is a server-based accounting and billing system, and SimpleLaw is a cloud practice management system. The financial records lead: balances and open items move, and the matters in SimpleLaw are built around them.

FromTabs3 Accounts PayableServer
  1. Contacts: Carried across
  2. Notes: Confirmed in the analysis
  3. Custom fields: Confirmed in the analysis
  4. Templates: Confirmed in the analysis
ToSimpleLawCloud
  1. Firm accounts: Kept as a readable archive
Readable archiveNo place in SimpleLaw
  • 1 carried
  • 3 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Tabs3 Accounts Payable to SimpleLaw

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

Records in Tabs3 Accounts Payable and their place in SimpleLaw
RecordIn Tabs3 Accounts PayableIn SimpleLawWhat is planned
ContactsClients, other parties and referrersHeld in partVendors.Has a placeAs leads, clients or other contacts in the CRM.Carried 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.No placeGeneral ledger stays in QuickBooks or another accounting package.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeConfirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partTemplates are rebuilt using SimpleLaw’s own automation.Confirmed in the analysis

What the plans mean

Carried across
SimpleLaw 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.
Kept as a readable archive
SimpleLaw has no place for it. It is exported in a format that opens without Tabs3 Accounts Payable 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

Time, bills and balances move. How much history is a decision.

Coming from an accounting or billing system, the records that count are balances: unbilled time, unpaid invoices, client funds, the ledger. A practice management system takes these as opening positions on a matter. So every client and job in Tabs3 Accounts Payable needs a matter to land on, and the first piece of work is building that matter list, often from client and project codes that were never meant to be matter numbers.

How much history to bring is the main choice. Paid invoices from years ago can be loaded as records, kept as PDF copies on the matter, or left in a read-only copy of Tabs3 Accounts Payable. Most firms bring open items and a period of history, and keep the rest as reports. Opening balances in SimpleLaw are agreed to the trial balance and aged debtors from Tabs3 Accounts Payable as at the cutover date, and that load is rehearsed before it is done for real.

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

Loading a firm into SimpleLaw is mostly a job of sorting contacts and setting up each matter’s billing type. The CRM holds leads, clients and everyone else, so every incoming contact needs a status. Where documents will be stored is decided early as well, since that choice determines where the files are sent. Accounting history stays in QuickBooks or the old system.

  1. Lead, client or contact

    A person is tracked from first enquiry to client in one CRM, with tasks and appointments kept against the contact. Source systems that only ever held clients load simply. Systems with separate intake records need each enquiry classed as a live lead, a lost one or a duplicate of an existing client.

  2. Billing type on each matter

    Every matter is billed as hourly, flat fee, instalments, contingency, pro bono, trust or LEDES. The source may record this loosely or not at all. During the trial load a billing type is set on each matter and checked by the person who raises the bills, because it controls how the invoice is built.

  3. Storage chosen before loading

    If the firm stores documents with SimpleLaw, files are uploaded against each matter. Where it prefers Dropbox, Google Drive or OneDrive, the files go there, and what the connection does with folders already in place is checked first. Switching later means moving everything again, so the choice is made at the start with the firm’s IT support.

  4. Custom fields named for templates

    Custom fields supply intake forms and document automation as well as reports. A field brought across from the old system is only useful if templates can call on it. Fields are therefore named and typed with the firm’s main documents in mind, and one template is tested against loaded data.

  5. Portal access client by client

    The client portal is optional and the firm chooses who has access and what each client can see. Nothing is exposed by loading data. After go-live, access is switched on for chosen clients, starting with a few, once the firm has reviewed what their matters show.

More about moving into SimpleLaw

How NewLaw runs it

Four steps, in this order.

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

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

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

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

Loaded data is not yet a working system. This is what NewLaw sets up in SimpleLaw, beyond the migration, so that people can work in it from the first day.

The set-up work is in making the product reflect the firm. Labels are adjusted to the firm’s terms. Intake forms and the custom fields behind them are built for each practice area, then document templates are made to draw on those fields. Workflows are written for the case types that follow a standard path, and the QuickBooks and payment connections are made last.

Set-up decisions in SimpleLaw

  • Labels for documents, activities, expenses and contact IDs
  • Custom fields and intake forms for each practice area
  • Document templates and the attorney-client agreement
  • Workflows for case types that follow a standard process
  • User permission sets and client portal visibility
  • QuickBooks connection and the online payment processor

Questions

Tabs3 Accounts Payable to SimpleLaw: 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 SimpleLaw without duplicates?

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

What happens to records SimpleLaw has no place for?

On this route that is the firm’s accounts. They are exported from Tabs3 Accounts Payable 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 Accounts Payable data is loaded into SimpleLaw?

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

Moving from Tabs3 Accounts Payable to SimpleLaw?

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

We reply within one business day.