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

Data migration route

Abacus Accounting to Litify migration

Abacus Accounting is a server-based accounting and billing system, and Litify is a cloud case management system. Only part of what Abacus Accounting holds has a place in a case file: clients and jobs move, and the table shows how much of the billing side does.

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

What moves

What moves from Abacus Accounting to Litify

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

Records in Abacus Accounting and their place in Litify
RecordIn Abacus AccountingIn LitifyWhat 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 placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeld in partBill-to names and vendors.Has a placeLoaded as parties and connected by roles.Carried across
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 placeLoaded to the document component and attached to matters.Carried across
NotesFile notes, matter notes and contact notesTo be confirmedTo be confirmedConfirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldHas a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeldIncludes split billing, rate cards and interest on late accounts.Has a place in partBilling is part of the product. Loading past invoices is scoped in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeldTrust by client and matter, including IOLTA accounts.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldGeneral ledger, vendor bills and bank reconciliation, with month-end and year-end closing.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeCustom fields are created before loading.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partBilling templates set the layout of invoices.Has a place in partTemplates are rebuilt in Litify’s document generation.Carried with mapping

What the plans mean

Carried across
Litify has a place for this kind of record. It is loaded there and checked against Abacus Accounting.
Carried with mapping
Litify 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

Clients and jobs move. The books stay books.

An accounting or billing system and a case management system overlap less than firms expect. Abacus Accounting knows clients, jobs, time and invoices. Litify 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 Litify are loaded and checked there. The rest is exported from Abacus Accounting as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If Abacus Accounting 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.

Abacus Accounting 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. Litify 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

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

Loading a firm into Litify is done inside a Salesforce environment that has been configured for that firm, normally by Litify or one of its implementation partners. The data work fits around that project. Old records are mapped to parties, roles, intakes and matters and loaded into the Salesforce objects behind them, and documents are loaded separately and attached.

  1. The design comes first

    Case types, stages and page layouts are decided during discovery, before any load. A load into a half-configured environment has to be repeated when a field changes. The data mapping is written against the agreed design and updated whenever the design moves, so the two stay in step.

  2. One party, many roles

    Contacts from the old system become parties, and each appearance on a matter becomes a role. Duplicate contacts turn into duplicate parties with their roles divided between them. Duplicates are merged before the load where they can be identified, since separating them afterwards means pointing every role at the right party again.

  3. Open enquiries load as intakes

    Leads and enquiries that have not signed belong in intakes, not matters. They are loaded with their source and status so that conversion reports start from a true position. Old declined enquiries are loaded only if the firm wants them for conflict checking, and are marked so they do not count as live.

  4. Documents load after records

    Files are loaded into the document component once the matters exist, because each one is attached to a matter record. Folder structure is set per case type beforehand. Large injury files with medical records and video take time to transfer, and that time is planned into the cutover weekend.

  5. Validation rules reject bad rows

    A configured environment enforces required fields and validation rules, and old data seldom satisfies all of them. Rows that fail are reported by the load. They are fixed in the source and run again, or the rule is relaxed for migrated records, and the firm decides which for each rule.

More about moving into Litify

How NewLaw runs it

Four steps, in this order.

Financial records move on this route, so the balances are rehearsed before the real cutover. The maker of Litify 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 Abacus Accounting and checking each trial against Abacus Accounting.

  1. Analysis

    We read what Abacus Accounting holds and how its records link, then agree with you, field by field, where each piece will sit in Litify. 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 Abacus Accounting, before extraction. It is not always possible to find every one, so some may carry across.

  3. Trial load

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

  4. Cutover

    Changes in Abacus Accounting are frozen for an agreed window, the data is collected a final time and Litify 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 Abacus Accounting as at the cutover date. Abacus Accounting 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 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 toLitify

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

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

A Litify implementation is a configuration project on Salesforce, run by Litify or an implementation partner with the firm’s own project team. Discovery sessions with each department come first. The decisions that follow shape the system: what an intake asks, how a matter moves through its stages, who sees what, and which other systems are connected.

Set-up decisions in Litify

  • Define intake questionnaires and the rules for conversion
  • Set case types, matter stages and page layouts
  • Build matter plans that create tasks at each stage
  • Design document folders and generation templates per case type
  • Configure user roles and sharing for restricted matters
  • Decide on timekeeping, billing and accounting integrations

Questions

Abacus Accounting to Litify: 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.

Do trust balances in Abacus Accounting have a place in Litify?

That is confirmed in the analysis. We could not establish it from the two products’ own material, so it is checked against your data in Abacus Accounting before the plan is fixed. If Litify turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

Does everything in Abacus Accounting have a place in Litify?

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

What has to be decided before Abacus Accounting data is loaded into Litify?

Billing records and templates are carried with mapping, so each mapping is agreed with you first. Notes, trust ledgers, the firm’s accounts and custom fields 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

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

Moving from Abacus Accounting to Litify?

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

We reply within one business day.