Data migration route
BillQuick to Server drives migration
BillQuick is a desktop accounting and billing system, and Server drives are plain files on equipment the firm controls. What moves is the files, plus a readable export of everything else the old system holds.
BillQuickDesktop- Templates: Carried with mapping
- Documents: Confirmed in the analysis
- Emails: Confirmed in the analysis
- Notes: Confirmed in the analysis
- Calendar: Confirmed in the analysis
Server drivesFiles- Matters: Kept as a readable archive
- Contacts: Kept as a readable archive
- Tasks: Kept as a readable archive
- Time and expenses: Kept as a readable archive
- Billing: Kept as a readable archive
- Trust money: Kept as a readable archive
- Firm accounts: Kept as a readable archive
- Custom fields: Kept as a readable archive
- 1 mapped
- 4 to confirm
- 8 archived
What moves
What moves from BillQuick to Server drives
Each row is a kind of record BillQuick holds, whether Server drives have a place for it, and what is planned. On this route one kind needs mapping, eight kinds have no place in Server drives and are archived and four 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. | No placeA matter becomes a folder; its details survive only in an index file. | Kept as a readable archive |
| ContactsClients, other parties and referrers | HeldClients with a contact each, employees and vendors. | No placeCan be kept only as an exported spreadsheet. | Kept as a readable archive |
| DocumentsFiles stored in or linked from the system | To be confirmed | Has a placeFiles in folders, named and dated during the load. | Confirmed in the analysis |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a place in partAs .msg or .eml files in each matter’s correspondence folder. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | To be confirmed | Has a place in partAs a text or PDF file per matter, not as separate records. | Confirmed in the analysis |
| CalendarAppointments, court dates and deadlines | To be confirmed | No place | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | Held in partTask allocation, forecasting and Gantt charts on projects. | No place | Kept as a readable archive |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime cards, timesheets, timers and expense sheets, with submit and approve. | No placeOnly as exported reports or spreadsheets. | Kept as a readable archive |
| BillingInvoices, payments and debtor balances | HeldManual, batch and joint invoices, statements, payments and credit memos. | Has a place in partInvoices as PDF files; no ledger. | Kept as a readable archive |
| Trust moneyTrust or client account ledgers and balances | Held in partRetainers are tracked against clients; no trust ledger appears in BQE’s feature list. | No placeOnly as exported ledger reports kept as files. | Kept as a readable archive |
| Firm accountsGeneral ledger, office account and payables | HeldChart of accounts, vendor bills, checks, general journal and reconciliation. | No place | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | Held in partCustom labels, plus custom report and invoice templates. | No place | Kept as a readable archive |
| TemplatesPrecedents, document templates and automation | Held in partInvoice and report templates only. | Has a place in partPrecedents as Word files; merge fields tied to the old system stop working. | Carried with mapping |
What the plans mean
- Carried with mapping
- Server drives 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
- Server drives 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.
Server drives hold 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 Server drives is limited before the export is copied in.
Both ends are on equipment the firm controls, so the work is done on the firm’s own network with its IT provider. Disk space for a second full copy is checked first. The original in BillQuick stays untouched until the copy in Server drives has been checked.
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 Server drives
Some firms leave a practice or document system and keep their documents on a server drive, either as the working store or as the archive of a system being switched off. The files will arrive without the database that described them. Everything the firm wants to keep knowing about a document has to be put into its path, its name or an index file.
Agree the tree and the names
A fixed pattern is chosen, for example client name and number, then matter number and short description, then a standard set of subfolders. Document titles from the old system become file names. Where two documents share a title, a date or sequence number is added so nothing is overwritten.
Budget the path length
Share name, client, matter, subfolder and file name all count towards the 260 character limit that many Windows programs still apply. The pattern is tested against the firm’s longest client names and document titles before the load. Descriptions are trimmed by rule, never by cutting off the file extension.
Dates have to be set deliberately
A file written to the server today is dated today unless its modified date is set from the old system’s record. Document dates are how lawyers find things in a folder. Which date each file is to carry is agreed in the analysis, and the trial load checks a sample.
Emails become message files
Emails filed to matters in the old system are written out as .msg or .eml files in a correspondence folder, named by date, sender and subject so they sort in order. Attachments stay inside the message. Subjects with characters Windows forbids are cleaned, and long ones cut.
Keep an index beside the files
A spreadsheet or small database listing every document with its matter, author, original date, document type and new path is the only place the old system’s profile data survives. It lets someone find a document by something other than its name. What the index records, and who keeps it, is decided in the analysis.
How NewLaw runs it
Four steps, in this order.
Nothing financial lands in Server drives on this route, which makes it repeatable: a load can be run again until it is right.
Analysis
We read what BillQuick holds and how it is organised, then agree with you where each kind of record will sit in Server drives. Anything with no place there stays behind or is archived, and you see which before the move.
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.
Trial load
A trial is loaded into Server drives 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.
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
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 Server drives. 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
Structure, permissions and handover
Server drives are 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.
A server drive does only what the firm and its IT provider make it do. Setting one up as a document store means building the share, deciding who can open which folders, and arranging the protections a document system would have supplied: backups, earlier versions and a way to recover a deleted folder. The filing rule is written down and taught.
What is agreed and set up
- Share and top-level folders for clients, precedents and administration
- Security groups and folder permissions, with restricted matters separate
- Drive letter mapped for every user at sign-in
- Backup schedule and shadow copies for earlier versions
- Written naming rule for client, matter and document names
- Read-only area for closed matters and archived system exports
Questions
BillQuick to Server drives: 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 Server drives?
No. Server drives do not keep trust ledgers. Only as exported ledger reports kept as files. 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 Server drives have no place for?
On this route that is matters, contacts, tasks, time entries, billing records, trust ledgers, the firm’s accounts and custom fields. 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 Server drives?
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.
Other routes
Other routes from BillQuick and into Server drives
Other destinations from BillQuick
Other systems that move into Server drives
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 Server drives are the names and marks of their owners, used here only to identify the two systems.
Moving from BillQuick to Server drives?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.