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

Data migration route

BillQuick to SharePoint migration

BillQuick is a desktop accounting and billing system, and SharePoint is cloud file storage. What moves is the files, plus a readable export of everything else the old system holds.

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

What moves

What moves from BillQuick to SharePoint

Each row is a kind of record BillQuick holds, whether SharePoint has a place for it, and what is planned. On this route five kinds need mapping, four kinds have no place in SharePoint and are archived and four kinds are confirmed in the analysis.

Records in BillQuick and their place in SharePoint
RecordIn BillQuickIn SharePointWhat 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 place in partAs a site, library, folder or list row the firm designs; no built-in matter record.Carried with mapping
ContactsClients, other parties and referrersHeldClients with a contact each, employees and vendors.Has a place in partOnly as rows in a list built for the purpose.Carried with mapping
DocumentsFiles stored in or linked from the systemTo be confirmedHas a placeFiles in libraries, with columns and versions.Confirmed in the analysis
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partAs .msg or .eml files, with columns for sender and date if set up.Confirmed in the analysis
NotesFile notes, matter notes and contact notesTo be confirmedHas a place in partAs documents, or as rows in a notes list if one is built.Confirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a place in partPossible as a list; usually left in Outlook.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeld in partTask allocation, forecasting and Gantt charts on projects.Has a place in partPossible as a list; no legal workflow built in.Carried with mapping
Time and expensesTime and expense entries, billed and unbilledHeldTime cards, timesheets, timers and expense sheets, with submit and approve.No placeKept as a readable archive
BillingInvoices, payments and debtor balancesHeldManual, batch and joint invoices, statements, payments and credit memos.No placeKept as a readable archive
Trust moneyTrust or client account ledgers and balancesHeld in partRetainers are tracked against clients; no trust ledger appears in BQE’s feature list.No placeKept as a readable archive
Firm accountsGeneral ledger, office account and payablesHeldChart of accounts, vendor bills, checks, general journal and reconciliation.No placeKept as a readable archive
Custom fieldsFields and record types the firm added itselfHeld in partCustom labels, plus custom report and invoice templates.Has a placeColumns and content types on libraries and lists.Carried with mapping
TemplatesPrecedents, document templates and automationHeld in partInvoice and report templates only.Has a place in partPrecedents as files; templates can be offered from a library.Carried with mapping

What the plans mean

Carried with mapping
SharePoint 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
SharePoint 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

An export the firm can open without the system.

SharePoint holds files, and most of what BillQuick holds is records. This route is therefore an export job. Each kind of record is written out in a format that opens without the system it came from: lists as spreadsheets, statements and invoices as PDFs, attachments as the files they were. The export is laid out in folders that make sense to someone who never used BillQuick, by client or by year, with a short index file saying what is where.

Firms do this when a subscription is ending, when a system is being retired, or to meet a retention rule. The test of the result is whether a question can still be answered from it years later: what was this client invoiced, who signed this agreement and when. So the trial export is checked by asking those questions of it. Totals are agreed to the system’s own reports, and access to the folder in SharePoint is limited before the export is copied in.

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

SharePoint will take a firm’s documents in almost any arrangement, which is the difficulty. The structure has to be chosen before the load: what a client is, what a matter is, and where security is applied. Changing it afterwards means moving every file again. Most of the effort goes into that design and into the columns that describe each document.

  1. Site, library or folder per matter

    A matter can be a site, a library within a client site, or a folder in one large library. Each choice has consequences for permissions, for search and for how a new matter is opened. The firm makes that decision, and the people who open matters every day should be part of it.

  2. Columns are built before content

    If documents are to carry matter number, client, document type or author as columns, those columns and any content types exist before loading, so each file can be tagged as it arrives. Tagging hundreds of thousands of documents afterwards is a second project that seldom gets finished.

  3. The 400 character path

    SharePoint limits the full decoded path, site and library and folders and file name, to 400 characters. A deep tree copied from a server drive under a long site name can cross it. Path lengths are calculated against the planned structure, not the old one, before any file moves.

  4. Large libraries and the view threshold

    A library can hold millions of files, but a view that tries to show more than 5,000 items at once runs into the list view threshold. One flat library with a folder per matter needs indexed columns and filtered views from the start, or views begin to fail as the library fills.

  5. Security by library, not by file

    Microsoft supports up to 50,000 unique permissions in a library and recommends staying under 5,000. Restricting matters one folder at a time reaches that sooner than firms expect. Restricted work is better grouped into its own site or library, so the permission is set once.

More about moving into SharePoint

How NewLaw runs it

Four steps, in this order.

Nothing financial lands in SharePoint on this route, which makes it repeatable: a load can be run again until it is right.

  1. Analysis

    We read what BillQuick holds and how it is organised, then agree with you where each kind of record will sit in SharePoint. Anything with no place there stays behind or is archived, and you see which before the move.

  2. Clean-up

    Duplicate clients, matters and folders are merged where they can be identified, and naming is put into one format, before anything is copied. It is not always possible to find every one, so some may carry across.

  3. Trial load

    A trial is loaded into SharePoint and checked against BillQuick: record and file counts, the links between records, document dates, and a sample opened by your own people. Exceptions are listed for you to decide.

  4. Cutover

    There is no financial cutover on this route. After a short freeze on changes in BillQuick, a final pass over a weekend picks up what changed since the trial. 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 toSharePoint

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

SharePoint is storage, not an application, so there is no product to configure. What is agreed and set up is the folder structure, who can open what, and how the result is handed to the firm.

Making SharePoint work as a firm’s document store is a design and build job in its own right. The sites, libraries, columns and permission groups are created, a way of opening a new matter is put in place so the structure repeats itself, and the Outlook and Teams habits around it are agreed. Search is tested with real questions from fee earners.

What is agreed and set up

  • Site and library structure for clients and matters
  • Columns and content types for matter number and document type
  • Permission groups, with restricted matters in their own libraries
  • A repeatable way to create each new matter’s workspace
  • Version history limits and retention labels for closed matters
  • Views, indexed columns and search tested on loaded data

Questions

BillQuick to SharePoint: 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 SharePoint?

No. SharePoint does not keep trust ledgers. Trust records from BillQuick are exported as ledgers and statements that open without it, and the firm settles where its trust accounting runs from the cutover date before the move is planned.

What happens to records SharePoint has no place for?

On this route that is time entries, billing records, trust ledgers and 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 SharePoint?

Matters, contacts, tasks, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Documents, emails, notes and calendar entries are confirmed in the analysis. The firm also decides which closed matters and how many versions of a document are in scope.

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

Moving from BillQuick to SharePoint?

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

We reply within one business day.