Data migration route
BillQuick to Litify migration
BillQuick is a desktop accounting and billing system, and Litify is a cloud case management system. 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.
BillQuickDesktop- Matters: Carried across
- Contacts: Carried across
- Tasks: Carried across
- Time and expenses: Carried across
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Documents: Confirmed in the analysis
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Calendar: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
LitifyCloud- 4 carried
- 3 mapped
- 6 to confirm
What moves
What moves from BillQuick to Litify
Each row is a kind of record BillQuick holds, whether Litify has a place for it, and what is planned. On this route four kinds of record carry across, three kinds need mapping and six kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partWork is tracked as projects under clients; there is no matter record as such. | Has a placeMatters, by case type. | Carried across |
| ContactsClients, other parties and referrers | HeldClients with a contact each, employees and vendors. | Has a placeLoaded as parties and connected by roles. | Carried across |
| DocumentsFiles stored in or linked from the system | To be confirmed | Has a placeLoaded to the document component and attached to matters. | Confirmed in the analysis |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partShown on the activity timeline. How old email is loaded is confirmed in the analysis. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | To be confirmed | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a placeCalendar events on the matter. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | Held in partTask allocation, forecasting and Gantt charts on projects. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime cards, timesheets, timers and expense sheets, with submit and approve. | Has a placeTime entries on the matter. | Carried across |
| BillingInvoices, payments and debtor balances | HeldManual, batch and joint invoices, statements, payments and credit memos. | 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 balances | Held in partRetainers are tracked against clients; no trust ledger appears in BQE’s feature list. | To be confirmed | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | HeldChart of accounts, vendor bills, checks, general journal and reconciliation. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | Held in partCustom labels, plus custom report and invoice templates. | Has a placeCustom fields are created before loading. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held in partInvoice and report templates only. | 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 BillQuick.
- 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. BillQuick 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 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. 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
Leaving BillQuick
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.
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.
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.
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.
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.
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.
Where it is going
Arriving in Litify
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.
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.
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.
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.
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.
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.
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 BillQuick and checking each trial against BillQuick.
Analysis
We read what BillQuick 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.
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.
Trial load
The data is loaded into Litify as a trial and checked against BillQuick: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in BillQuick 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 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
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 BillQuick 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.
- 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
BillQuick to Litify: 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 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 BillQuick 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 BillQuick have a place in Litify?
Most of it does on paper. Documents, emails, notes, calendar entries, trust ledgers and the firm’s accounts 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 BillQuick data is loaded into Litify?
Billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Documents, emails, notes, calendar entries, trust ledgers and the firm’s accounts 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 BillQuick and into Litify
Other destinations from BillQuick
Other systems that move into Litify
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.
BillQuick and Litify are the names and marks of their owners, used here only to identify the two systems.
Moving from BillQuick 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.