Data migration route
Abacus Accounting to Clio Manage migration
Abacus Accounting is a server-based accounting and billing system, and Clio Manage is a cloud practice management system. The financial records lead: balances and open items move, and the matters in Clio Manage are built around them.
Abacus AccountingServer- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Time and expenses: Carried with mapping
- Billing: Carried with mapping
- Trust money: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
Clio ManageCloud- Firm accounts: Kept as a readable archive
- 3 carried
- 4 mapped
- 2 to confirm
- 1 archived
What moves
What moves from Abacus Accounting to Clio Manage
Each row is a kind of record Abacus Accounting holds, whether Clio Manage has a place for it, and what is planned. On this route three kinds of record carry across, four kinds need mapping, one kind has no place in Clio Manage and is archived and two kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partOnly matters sent from AbacusLaw with a BILLTO link appear. | Has a placeImported from a matters template, after contacts. | Carried across |
| ContactsClients, other parties and referrers | Held in partBill-to names and vendors. | Has a placePeople and companies, with related contacts linked to matters by a separate template. | Carried across |
| DocumentsFiles stored in or linked from the system | Held in partCopies of invoices and posting reports are saved as files in a Bills folder. | Has a placeFiled under the matter; Clio scopes document migration separately from data. | Carried across |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a placeMatter notes and contact notes each have a template. | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | Held | Has a place in partUnbilled time entries load; billed time entries do not, by Clio’s migration guide. | Carried with mapping |
| BillingInvoices, payments and debtor balances | HeldIncludes split billing, rate cards and interest on late accounts. | Has a place in partAn outstanding balance loads as one line per matter; past invoices do not. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | HeldTrust by client and matter, including IOLTA accounts. | Has a place in partA trust balance loads as one line per matter or contact; past transactions do not. | Carried with mapping |
| Firm accountsGeneral ledger, office account and payables | HeldGeneral ledger, vendor bills and bank reconciliation, with month-end and year-end closing. | No placeNot in Clio Manage. Books sit in a linked accounting package, or in Clio Accounting where Clio offers it. | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeCreated first, then filled from the custom field templates. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | Held in partBilling templates set the layout of invoices. | Has a placeRebuilt as Clio document templates with its merge fields. | Carried with mapping |
What the plans mean
- Carried across
- Clio Manage has a place for this kind of record. It is loaded there and checked against Abacus Accounting.
- Carried with mapping
- Clio Manage 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.
- Kept as a readable archive
- Clio Manage has no place for it. It is exported in a format that opens without Abacus Accounting 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 Abacus Accounting 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 Abacus Accounting. Most firms bring open items and a period of history, and keep the rest as reports. Opening balances in Clio Manage are agreed to the trial balance and aged debtors from Abacus Accounting as at the cutover date, and that load is rehearsed before it is done for real.
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. Clio Manage 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
Leaving Abacus Accounting
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.
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.
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.
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.
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.
Where it is going
Arriving in Clio Manage
Clio Manage is loaded through its migration templates, one spreadsheet per kind of record, imported in a fixed order with contacts first. Clio’s own migration guide is plain about the limit: balances come across, financial history does not. So a load into Clio is planned as records plus opening positions, with the old system kept for the history behind them.
Matters link by client name
The matters template ties each matter to its client by an exact match on first name, last name or company name. A client spelt two ways in the old system becomes two contacts, or a matter assigned to an unknown client. This is why contact clean-up is finished before the first trial load, not after it.
Decide the numbering scheme first
Clio numbers imported matters itself unless the account is set to manual numbering, in which case the old number is supplied in the template. That setting and the firm’s preferred scheme are decided before any matter is loaded. The Client Reference field is available for an old file number the firm still wants to see.
Balances, one line each
Under Clio’s standard migration, an outstanding balance arrives as one line per matter and a trust balance as one line per matter or contact. Past invoices, billed time, payments and trust transactions are listed as data that cannot be migrated. The trust total is reconciled against the old system’s closing report on the trial load.
Custom fields must exist
Matter and contact custom fields are created in Clio before their values are imported, each with a field type. Accounts set up for a particular practice area come with preconfigured fields and matter templates, which affects the mapping. We compare those with the old system’s fields and add only what is missing.
Rates and permissions by hand
Billable rates for users, clients and matters are not part of an import. Neither are user permissions or settings. They are entered in Clio during set-up from a schedule the firm confirms, and a sample of imported unbilled time is checked against that schedule before the trial load is signed off.
How NewLaw runs it
Four steps, in this order.
Trust money moves on this route, so the trust cutover gets a rehearsal of its own.
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 Clio Manage. Anything with no place there comes across as a note or stays behind, and you see which before the move.
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.
Trial load
The data is loaded into Clio Manage as a trial and checked against Abacus Accounting: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in Abacus Accounting are frozen for an agreed window, the data is collected a final time and Clio Manage goes live over a weekend. The trust and financial cutover is rehearsed on a full trial load first, because it cannot be re-run the way a document load can. 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
What happens after you send it
- A free first call
We go through your answers with you and ask about anything they leave open.
- An analysis of what Abacus Accounting holds
What is in it, how its records link, and where each piece would sit in Clio Manage. Anything with no place there comes across as a note or stays behind, and you see which before the move.
- 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 Clio Manage
Loaded data is not yet a working system. This is what NewLaw sets up in Clio Manage, beyond the migration, so that people can work in it from the first day.
Much of a Clio Manage set-up is firm-wide settings. The numbering scheme, practice areas, matter stages, billing preferences and trust accounts apply to everyone, so they are agreed once and early. Trust and accounting features are not the same in every country Clio sells in, so the firm’s own region is checked first. Document templates and custom fields follow. Email and document integrations are then installed for each user and tested on a real matter.
Set-up decisions in Clio Manage
- Matter numbering scheme, practice areas and matter stages
- Custom fields for matters and contacts, by practice area
- Document templates with merge fields, uploaded from Word or PDF
- Billing settings, user and client rates, and trust accounts
- Roles and permissions for each user
- Outlook add-in, Clio Drive and the accounting connection
Questions
Abacus Accounting to Clio Manage: 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 Clio Manage?
In part. A trust balance loads as one line per matter or contact; past transactions do not. The analysis sets out which trust records have a place in Clio Manage and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.
What happens to records Clio Manage has no place for?
On this route that is the firm’s accounts. They are exported from Abacus Accounting 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 Abacus Accounting data is loaded into Clio Manage?
Time entries, billing records, trust ledgers and templates are carried with mapping, so each mapping is agreed with you first. Notes 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.
Other routes
Other routes from Abacus Accounting and into Clio Manage
Other destinations from Abacus Accounting
Other systems that move into Clio Manage
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.
Choose your systems
Technology stack selection
Decide which practice management system your firm runs, with the evidence and the cost beside it.
About four weeks for a firm of about 15 people. Fixed price, set after a free first call.
Move your data
Data migration
Your data is cleaned up before anything moves, then a trial load is checked against the old system.
Fixed price, agreed after the analysis.
Set up your new system
Implementation
Your new system set up around the way your firm works: configuration, document automation and training.
A small firm of 1 to 10 users typically takes 4 to 8 weeks. A mid-sized firm of 10 to 50 users takes 8 to 16 weeks.
Put AI to work
AI advisory and enablement
A small group of your people learn to use an approved AI tool on real work, under written rules.
Two to four weeks for a small first group. Fixed price, set after a free first call.
Abacus Accounting and Clio Manage are the names and marks of their owners, used here only to identify the two systems.
Moving from Abacus Accounting to Clio Manage?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.