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

Data migration route

Tabs3 Accounts Payable to Soluno migration

Tabs3 Accounts Payable is a server-based accounting and billing system, and Soluno is a cloud one. This is a move of the books: chart of accounts, customers, open items and balances.

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

What moves

What moves from Tabs3 Accounts Payable to Soluno

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

Records in Tabs3 Accounts Payable and their place in Soluno
RecordIn Tabs3 Accounts PayableIn SolunoWhat is planned
ContactsClients, other parties and referrersHeld in partVendors.Has a placeEach contact is numbered; a file must have a primary contact.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedTo be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldVendor invoices, cheques and EFTs, recurring entries and 1099s; posts to Tabs3 General Ledger.Has a placeGeneral ledger; history is loaded into open periods that are then closed in order.Carried across
Custom fieldsFields and record types the firm added itselfTo be confirmedTo be confirmedConfirmed in the analysis
TemplatesPrecedents, document templates and automationTo be confirmedTo be confirmedConfirmed in the analysis

What the plans mean

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

Books to books, agreed to the trial balance.

An accounts move has a clear test: the trial balance in Soluno on its first day equals the trial balance in Tabs3 Accounts Payable on its last. Getting there starts with the chart of accounts. The two systems number and group accounts differently, so each account is mapped to its counterpart, and the firm’s accountant signs off the mapping. Customers, suppliers and open invoices follow, each tied back to an aged report from the old system.

History is the choice. The new books can start from opening balances and open items only, which is quick and clean, or take a period of transactions, which lets comparative reports run. Older years are usually kept as reports and a read-only copy of Tabs3 Accounts Payable. Time entries and rates move if Soluno has a place for them. The cutover is set for a period end, after the last bank reconciliation, so the two sets of books meet at a point both can prove.

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

Soluno, which Actionstep now sells as Actionstep Legal Accounting, is an accounting system first, and it expects accounting discipline from the data it is given. Contacts and files need numbers. Entries need dates that fall in open financial periods. Billing, rate and file groups should exist before files are created so that defaults apply. Where documents, calendars and case detail will live is settled alongside.

  1. Numbers for contacts and files

    Every contact has a number and every file has a file number, which Soluno can generate on its own or by contact. A firm can keep its old numbers by typing over the suggested value. The format is agreed first, since the help centre puts later number changes behind an administrator setting once NetDocuments is in use.

  2. Groups before files

    File, billing and rate groups set the defaults a new file picks up, and a file can override them. Loading thousands of files without the groups in place means fixing each one by hand later. The groups are designed from the source system’s rate tables and billing terms during the analysis.

  3. Periods must be open

    Soluno closes financial periods, and a file cannot be closed while it has entries dated after the last closed period. Historic transactions are loaded with the relevant periods open, checked, and then the periods are closed in order. That sequence is rehearsed on the full trial load with the firm’s accountant.

  4. Closed matters need zero balances

    A file closes only when it has no work in progress, no receivable and no retainer or trust balance. Old matters that the source system marked closed while still carrying a few dollars will not close here. Those small balances are written off or cleared in the source before extraction, with partner approval.

  5. Documents live beside it

    Its help centre covers accounting, banking, billing, contacts and files, and describes links to NetDocuments and to Actionstep practice management. It describes no matter document store. A firm arriving from an all-in-one product should expect to need a second destination for its documents, emails and calendar, and the two loads are planned together so matter numbers match in both.

More about moving into Soluno

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover.

  1. Analysis

    We read what Tabs3 Accounts Payable holds and how its records link, then agree with you, field by field, where each piece will sit in Soluno. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  2. Clean-up

    Duplicate contacts and matters are merged where they can be identified, and inconsistent entries are put into one format, in Tabs3 Accounts Payable, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

    The data is loaded into Soluno as a trial and checked against Tabs3 Accounts Payable: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in Tabs3 Accounts Payable are frozen for an agreed window, the data is collected a final time and Soluno goes live over a weekend. The financial cutover is rehearsed on a full trial load first, so that opening balances agree with the reports in Tabs3 Accounts Payable as at the cutover date. 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 toSoluno

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

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

Most of the set-up in Soluno is financial structure. The chart of accounts, bank accounts and financial periods come first, then the groups that control billing and rates, then users and what each group of users may do. Lawyers need task code shortcuts and rates before they can enter time. If NetDocuments or Actionstep practice management is to be linked, that connection is made once numbering is final.

Set-up decisions in Soluno

  • Chart of accounts, bank accounts and opening financial periods
  • File, billing and rate groups with their default arrangements
  • Contact and file numbering format, set firm-wide or by contact
  • User groups and what each group may see or do
  • Task and activity codes and each lawyer’s shortcuts
  • Link to NetDocuments or to Actionstep practice management

Questions

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

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

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

Most of it does on paper. Notes, 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 Soluno 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 Soluno?

Notes, custom fields and templates are confirmed in the analysis. The firm also sets the cutover date and how much financial history comes across as live records.

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

Moving from Tabs3 Accounts Payable to Soluno?

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

We reply within one business day.