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

Data migration route

Abacus Accounting data to Microsoft SQL Server

Abacus Accounting is a server-based accounting and billing system, and Microsoft SQL Server is a database on a server the firm runs. This is not a move to a new working system: the route writes out what Abacus Accounting holds and keeps it readable and open to queries.

FromAbacus AccountingServer
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Time and expenses: Exported in full
  4. Billing: Exported in full
  5. Trust money: Exported in full
  6. Firm accounts: Exported in full
  7. Documents: Exported with mapping
  8. Templates: Exported with mapping
  9. Notes: Confirmed in the analysis
  10. Custom fields: Confirmed in the analysis
ToMicrosoft SQL ServerServer
  • 6 carried
  • 2 mapped
  • 2 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from Abacus Accounting to Microsoft SQL Server

Each row is a kind of record Abacus Accounting holds, whether Microsoft SQL Server has a place for it, and what is planned. On this route six kinds of record carry across, two kinds need mapping and two kinds are confirmed in the analysis.

Records in Abacus Accounting and their place in Microsoft SQL Server
RecordIn Abacus AccountingIn Microsoft SQL ServerWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partOnly matters sent from AbacusLaw with a BILLTO link appear.Has a placeA table of matters linked to clients, parties and fee earners.Exported in full
ContactsClients, other parties and referrersHeld in partBill-to names and vendors.Has a placePeople and companies, with their roles on each matter.Exported in full
DocumentsFiles stored in or linked from the systemHeld in partCopies of invoices and posting reports are saved as files in a Bills folder.Has a place in partAs files in folders with an index table; storing files in the database is possible.Exported with mapping
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeRows of text linked to matters and contacts.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldHas a placeTime and expense rows with rates and billed status.Exported in full
BillingInvoices, payments and debtor balancesHeldIncludes split billing, rate cards and interest on late accounts.Has a placeInvoices, lines and receipts as rows; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesHeldTrust by client and matter, including IOLTA accounts.Has a placeTransactions and balances for look-up; it is not a trust accounting system.Exported in full
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger, vendor bills and bank reconciliation, with month-end and year-end closing.Has a placeGeneral ledger journals and balances, where the source held them.Exported in full
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeAs added columns, or a table of field names and values.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partBilling templates set the layout of invoices.Has a place in partPrecedent files can be stored; automation does not run here.Exported with mapping

What the plans mean

Exported in full
Microsoft SQL Server has a place for this kind of record. It is loaded there and checked against Abacus Accounting.
Exported with mapping
Microsoft SQL Server holds this differently, or in part. Each field or value is matched to its place before loading, and you see the mapping first.
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

Not a new system. A complete copy the firm can query.

Writing Abacus Accounting out to Microsoft SQL Server is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.

What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in Abacus Accounting as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.

Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in Abacus Accounting stays untouched until the copy in Microsoft SQL Server has been checked.

Where the data is now

Moving the books out of Abacus Accounting is a ledger job more than a document job. Unbilled time and costs, open invoices, trust balances by client and matter, and the general ledger each have to arrive agreeing with a report run on the last day. The matters themselves come from AbacusLaw, so the two are extracted together and matched on the matter.

  1. Only billed matters appear

    A matter exists in accounting only after someone linked a name to it in AbacusLaw with the link type BILLTO. So the list of matters with money on them is shorter than the list of matters. The two lists are reconciled first, which also finds matters that were billed under the wrong name.

  2. Soft closes and hard closes

    A month-end close in this module can be undone later, and it closes every earlier month with it. The year-end close is the firmer one. Opening balances for the new system are taken at a closed period end so they agree with printed reports, and the firm leaves that period closed.

  3. Saved bills are files

    Copies of invoices and posting reports are kept as files in the Abacus\Bills folder, outside the tables. Those are the bills as the client received them. They can be filed against each matter in the destination even where invoice history is loaded only as balances.

  4. Trust by matter and by bank

    Trust money is held by client and matter, and a firm may run more than one trust bank account, IOLTA among them. The trial load is checked against the trust listing for each bank account, matter by matter. A matter with a trust balance but no open file in the new system is listed for the firm to decide.

More about moving off Abacus Accounting

Where it is going

There are two ways to put a retired system into SQL Server, and they suit different firms. The old system’s own database can be restored as it is. Or the data can be loaded into a new set of tables designed to be read by people. The first is quicker and harder to use. Which suits is worked out in the analysis, and the choice is the firm’s.

  1. Restored copy or rebuilt schema

    Where the old practice system already kept its data in SQL Server, a backup can be restored onto a new server. The tables keep the vendor’s names and codes, which can be cryptic, and reading them takes someone who knows that product’s database. A rebuilt schema uses plain names such as Matter and TrustTransaction.

  2. No screens come with it

    A database has no matter screen. Someone has to ask it questions in SQL or through a reporting tool. Saved views can be set up for the things the firm will really look up: a matter with its parties, its ledger, its time entries and its list of documents. Which are worth having is agreed in the analysis.

  3. Documents sit beside the database

    Files are normally kept in folders on the same server, with a table recording each document’s matter, title, dates and path. Storing the files inside the database is possible but makes it far larger. On the Express edition, the cap on database size rules that out for most firms’ document stores.

  4. The edition follows the size

    A firm’s tables may fit within the Express limit once documents are kept outside the database. A long trust and time history at a larger firm may not. The size of the source data is measured in the analysis, and the edition is chosen from that figure with the firm’s IT provider.

  5. Backups and a test restore

    An archive that is never backed up is one disk failure from gone. Backups belong to the firm’s IT provider: a full one once the load is finished, and a schedule if anything is still being added. It is worth restoring one to a second machine as a test, because a backup that has never been restored is only a hope.

More about moving into Microsoft SQL Server

How NewLaw runs it

Four steps, in this order.

This route produces an archive, not a working system, so the steps are about completeness and proof.

  1. Analysis

    We read what Abacus Accounting holds, table by table, and agree with you what the copy in Microsoft SQL Server must be able to answer later. Everything Abacus Accounting holds is in scope unless you take it out.

  2. Clean-up, if you want it

    An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.

  3. Trial export

    The data is written to Microsoft SQL Server as a trial and checked against Abacus Accounting: record counts, totals where Abacus Accounting holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in Abacus Accounting, the export is run a final time and checked again. There is nothing to go live. Abacus Accounting is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.

Fixed price, agreed after the analysis. How NewLaw moves legal data

Start

Start this migration

Tell us what is in Abacus Accounting 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 fromAbacus Accounting
Moving toMicrosoft SQL Server

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 Abacus Accounting holds

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

Microsoft SQL Server is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.

Standing up SQL Server as an archive is IT work shared with the firm’s provider. A server or instance is chosen, logins are created for the few people who need to read the data, and nobody is given rights to change it. Views and a handful of reports are built for the common questions, and the IT provider owns the backup routine.

What is agreed and set up

  • Server, instance and edition agreed with the IT provider
  • Read-only logins and roles for named staff
  • Views for matter, ledger, time and document look-ups
  • Backup schedule and who tests a restore
  • Plain names and descriptions for tables and columns
  • Excel or Power BI connected for reporting

Questions

Abacus Accounting to Microsoft SQL Server: what firms ask

Can we bring across full transaction history or only balances?

It depends on what the destination can take. Many systems accept opening balances, unbilled time and costs and open invoices, but not years of posted ledger entries. The usual answer is balances and open items loaded, with older detail kept in the read-only copy and in the saved bill files.

Does the general ledger move too?

Only if the new system has a general ledger of its own. If it posts to a separate accounting package, the chart of accounts and closing balances go there instead, as an opening journal the firm’s accountant approves. The analysis settles which before any data is taken.

What if our trust ledger does not reconcile today?

Then it is fixed in Abacus before extraction, not after. Unreconciled items, old uncleared cheques and balances on finished matters are listed during the analysis. The firm clears what it can, and anything left is carried across as a named exception with the same figure on both sides.

Does the copy in Microsoft SQL Server hold trust ledgers from Abacus Accounting?

Yes. Transactions and balances for look-up; it is not a trust accounting system. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in Abacus Accounting as at the export date.

Does everything in Abacus Accounting have a place in Microsoft SQL Server?

Most of it does on paper. Notes and custom fields 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 Microsoft SQL Server is kept as a readable archive, and you see which before the move.

What has to be decided before Abacus Accounting is written out to Microsoft SQL Server?

Documents and templates are exported with mapping, so each mapping is agreed with you first. Notes and custom fields are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.

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

Abacus Accounting and Microsoft SQL Server are the names and marks of their owners, used here only to identify the two systems.

Moving from Abacus Accounting to Microsoft SQL Server?

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

We reply within one business day.