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

Data migration route

BillQuick to Neos migration

BillQuick is a desktop accounting and billing system, and Neos is a cloud case management system for personal injury work. Only part of what BillQuick holds has a place in a case file: clients and jobs move, and the table shows how much of the billing side does.

FromBillQuickDesktop
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Tasks: Carried across
  4. Time and expenses: Carried with mapping
  5. Billing: Carried with mapping
  6. Custom fields: Carried with mapping
  7. Templates: Carried with mapping
  8. Documents: Confirmed in the analysis
  9. Emails: Confirmed in the analysis
  10. Notes: Confirmed in the analysis
  11. Calendar: Confirmed in the analysis
  12. Trust money: Confirmed in the analysis
ToNeosCloud
  1. Firm accounts: Kept as a readable archive
Readable archiveNo place in Neos
  • 3 carried
  • 4 mapped
  • 5 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from BillQuick to Neos

Each row is a kind of record BillQuick holds, whether Neos 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 Neos and is archived and five kinds are confirmed in the analysis.

Records in BillQuick and their place in Neos
RecordIn BillQuickIn NeosWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partWork is tracked as projects under clients; there is no matter record as such.Has a placeCases by case type.Carried across
ContactsClients, other parties and referrersHeldClients with a contact each, employees and vendors.Has a placeParties, providers and case contacts. Contacts can be imported from CSV.Carried across
DocumentsFiles stored in or linked from the systemTo be confirmedHas a placeCase Docs tab, organised in sub-tabs.Confirmed in the analysis
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partEmails tagged to a case are held. Loading old mail is scoped in the analysis.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a placeConfirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeCase calendar entries.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeld in partTask allocation, forecasting and Gantt charts on projects.Has a placeLoaded as checklist items.Carried across
Time and expensesTime and expense entries, billed and unbilledHeldTime cards, timesheets, timers and expense sheets, with submit and approve.Has a place in partTime can be held as value items. The treatment of old entries is confirmed in the analysis.Carried with mapping
BillingInvoices, payments and debtor balancesHeldManual, batch and joint invoices, statements, payments and credit memos.Has a place in partInvoices exist in Neos. Loading past invoices is confirmed in the analysis.Carried with mapping
Trust moneyTrust or client account ledgers and balancesHeld in partRetainers are tracked against clients; no trust ledger appears in BQE’s feature list.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldChart of accounts, vendor bills, checks, general journal and reconciliation.No placeThe general ledger stays in QuickBooks.Kept as a readable archive
Custom fieldsFields and record types the firm added itselfHeld in partCustom labels, plus custom report and invoice templates.Has a placeUser-defined fields are created on the relevant tab first.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partInvoice and report templates only.Has a place in partTemplates are rebuilt for Neos document generation.Carried with mapping

What the plans mean

Carried across
Neos has a place for this kind of record. It is loaded there and checked against BillQuick.
Carried with mapping
Neos 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
Neos has no place for it. It is exported in a format that opens without BillQuick 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. BillQuick 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 BillQuick as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If BillQuick 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.

BillQuick 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

BillQuick has no matters. A law office that used it has been treating projects as matters, with its own habits about how they were named and numbered. Moving to a legal practice system means turning each client and project into a client and matter, and deciding what to do with the accounting that BillQuick may also have been doing.

  1. One project, one matter

    Every time entry and invoice hangs off a project under a client. Project names and IDs follow whatever convention the firm adopted, so some will carry a matter number, some a description, and a few will cover several pieces of work. Each project is mapped to one matter before any time or billing is loaded.

  2. Activity and expense items

    Time is recorded against activity items and costs against expense items, each with its own tax setting. A legal system expects activity codes or task codes in their place. The item list is usually longer than anyone remembers, so it is cut down and mapped before the trial load.

  3. Contract types and fee schedules

    BillQuick bills a project according to its contract type and can apply a fee schedule, a budget and a billing schedule. Hourly work is the simple case. Fixed fee and recurring arrangements need a matching billing set-up in the destination, or the next invoice will be calculated differently from the last.

  4. Retainers and retainage

    Client retainers are held as retainer balances, and some firms also used retainage on invoices. Neither is a trust ledger. Where retainer money is in fact client money, each balance is reconciled to the bank account that holds it before it is opened as trust in the new system.

  5. Was it the firm’s ledger?

    The program has a chart of accounts, vendor bills, cheque writing and bank reconciliation, and it can also pass data to QuickBooks Desktop or Sage 50. Which of those the firm relied on decides where the general ledger history is taken from. That is checked in the data, not assumed.

More about moving off BillQuick

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.

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

  1. Analysis

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

  3. Trial load

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

  4. Cutover

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

BillQuick to Neos: what firms ask

We used BillQuick projects as matters. Will that carry over?

It will, as long as each project maps to one matter. The client stays the client, the project becomes the matter, and the project ID is kept as the matter number or as a reference. Projects that held several pieces of work under one name are split during clean-up, before extraction.

Can unbilled time come across?

Unbilled time and expenses can be read with their dates, staff member, hours and description. Whether they arrive as live unbilled entries depends on the destination accepting time at the original rates. The alternative is to bill everything possible before cutover and bring the remainder across as a short list.

Is BillQuick still supported?

BQE counts BillQuick among its legacy products and describes BQE CORE as the next step for existing users. Whether BillQuick itself is still supported should be confirmed with BQE. For a firm moving to a legal system the practical point is to keep the BillQuick company file and a working installation as the read only record.

Do trust balances in BillQuick have a place in Neos?

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 BillQuick before the plan is fixed. If Neos turns out to have no place for trust ledgers, they are kept as a readable archive and the firm decides where trust accounting runs.

What happens to records Neos has no place for?

On this route that is the firm’s accounts. They are exported from BillQuick 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 BillQuick data is loaded into Neos?

Time entries, billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Documents, emails, notes, calendar entries and trust ledgers 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

BillQuick and Neos are the names and marks of their owners, used here only to identify the two systems.

Moving from BillQuick 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.