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

Data migration route

Tabs3 Accounts Payable to Neos migration

Tabs3 Accounts Payable is a server-based accounting and billing system, and Neos 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. Custom fields: Confirmed in the analysis
  4. Templates: Confirmed in the analysis
ToNeosCloud
  1. Firm accounts: Kept as a readable archive
Readable archiveNo place in Neos
  • 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 Neos

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

Records in Tabs3 Accounts Payable and their place in Neos
RecordIn Tabs3 Accounts PayableIn NeosWhat is planned
ContactsClients, other parties and referrersHeld in partVendors.Has a placeParties, providers and case contacts. Contacts can be imported from CSV.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 placeThe general ledger stays in QuickBooks.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeUser-defined fields are created on the relevant tab first.Confirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedHas a place in partTemplates are rebuilt for Neos document generation.Confirmed in the analysis

What the plans mean

Carried across
Neos 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
Neos 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

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

Neos expects personal injury data in its own tab structure, so loading a firm means deciding which tab each old record belongs on. Parties, insurance and counsel map directly from most injury systems. Money maps to value items. Anything the standard tabs lack becomes a user-defined field, which has to be created before the load.

  1. Every figure needs a value code

    Costs, medical bills, fees and settlement amounts are loaded as value items, and each carries a value code. The code list is agreed with the firm’s accounts staff first. A figure loaded under the wrong code is reported in the wrong place, so the list is tested on real cases before the bulk load.

  2. Lists are set up first

    Cases are loaded against case types, statuses and staff assignments that already exist in Neos. Those lists are set up, and the old system’s values tidied to match, before the trial load. Misspelt attorney names and unused case types in the source are cleaned out at the same stage.

  3. Documents go to sub-tabs

    Files land on the Case Docs tab under sub-tabs, which staff can view as a list or as folders. The old system’s folders or categories are mapped to a fixed set of sub-tabs. Without that, every personal habit of naming folders is reproduced and the folder view becomes hard to read.

  4. Reminders split two ways

    Neos fills its dashboards from checklists and case calendars. Old diary entries and tasks are sorted between them: dated appointments and court events to the calendar, and to-dos to the checklist. An item assigned to several people in the old system may need one named owner, and the firm chooses who.

  5. Assembly runs its own conversions

    Assembly migrates firms into Neos with its own team and tooling, and offers routes from self-service templates to a full conversion. Where the firm uses that service, outside help goes on the work around it: cleaning the source, checking the converted cases against the old system, and listing exceptions.

More about moving into Neos

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in Neos on this route, which makes it repeatable: a load can be run again until it is right. The maker of Neos 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 Neos. 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 Neos 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 toNeos

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

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

Neos comes set up for injury work, so implementation is mostly choosing among its options and connecting the firm’s other tools. The lists that drive reporting are decided first, then checklists, then documents. Assembly provides its own implementation team, and the firm’s internal lead still has to make the decisions listed below.

Set-up decisions in Neos

  • Set case types, statuses and staff roles
  • Agree the value code list with accounts staff
  • Build checklists for each case type and stage
  • Create user-defined fields for data the tabs lack
  • Prepare document templates for the generation wizard
  • Connect Microsoft 365, QuickBooks and the phone system

Questions

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

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

What happens to records Neos 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 Neos?

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

Moving from Tabs3 Accounts Payable to Neos?

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

We reply within one business day.