Data migration route
QuickBooks Desktop to Filevine migration
QuickBooks Desktop is a desktop accounting and billing system, and Filevine is a cloud case management system. Only part of what QuickBooks Desktop holds has a place in a case file: clients and jobs move, and the table shows how much of the billing side does.
QuickBooks DesktopDesktop- Matters: Carried across
- Contacts: Carried across
- Notes: Carried across
- Tasks: Carried across
- Time and expenses: Carried with mapping
- Billing: Carried with mapping
- Trust money: Carried with mapping
- Templates: Carried with mapping
- Documents: Confirmed in the analysis
- Emails: Confirmed in the analysis
- Calendar: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Custom fields: Confirmed in the analysis
FilevineCloud- 4 carried
- 4 mapped
- 5 to confirm
What moves
What moves from QuickBooks Desktop to Filevine
Each row is a kind of record QuickBooks Desktop holds, whether Filevine has a place for it, and what is planned. On this route four kinds of record carry across, four kinds need mapping and five kinds are confirmed in the analysis.
| Record | What is planned | ||
|---|---|---|---|
| MattersMatters or cases, with their numbers, types, parties and status | Held in partNo matter record; clients and matters are kept as customers and customer jobs. | Has a placeLoaded as projects of a defined project type. | Carried across |
| ContactsClients, other parties and referrers | HeldCustomers, vendors, employees and other names. | Has a placeContact cards, linked to projects. | Carried across |
| DocumentsFiles stored in or linked from the system | To be confirmed | Has a placeDocs section with folders. Templated project folders can be set per type. | Confirmed in the analysis |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a placeHeld in the activity feed of the project. | Confirmed in the analysis |
| NotesFile notes, matter notes and contact notes | Held in partNotes are one of the lists kept in the company file. | Has a placeHeld as notes in the activity feed. | Carried across |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a placeDeadlines and calendar events. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | Held in partA to-do list. | Has a place | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime against customers and jobs, billable or not. | Has a place in partNeeds the Billing product enabled. | Carried with mapping |
| BillingInvoices, payments and debtor balances | HeldEstimates, invoices, credit memos and customer payments. | Has a place in partNeeds the Billing product enabled. | Carried with mapping |
| Trust moneyTrust or client account ledgers and balances | Held in partNo trust ledger; client funds are tracked through bank and liability accounts. | Has a place in partTrust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis. | Carried with mapping |
| Firm accountsGeneral ledger, office account and payables | HeldChart of accounts, vendor bills, checks, deposits and general journal entries. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeCustom sections and fields per project type. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | Held in partInvoice and form templates, which can be exported and imported. | Has a place in partTemplates are rebuilt as Filevine document templates. They are not converted. | Carried with mapping |
What the plans mean
- Carried across
- Filevine has a place for this kind of record. It is loaded there and checked against QuickBooks Desktop.
- Carried with mapping
- Filevine 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. QuickBooks Desktop knows clients, jobs, time and invoices. Filevine 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 Filevine are loaded and checked there. The rest is exported from QuickBooks Desktop as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If QuickBooks Desktop 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.
QuickBooks Desktop 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. Filevine 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 QuickBooks Desktop
Leaving QuickBooks Desktop means either moving the firm’s books to another ledger, or moving the client and billing side into a practice system while the books continue somewhere else. Those are different jobs. In both, the company file is read list by list and transaction type by transaction type, and what the firm has improvised inside it for matters and trust is untangled first.
Customers and jobs
QuickBooks has customers and, beneath them, jobs. Some firms made each client a customer and each matter a job. Others made every matter its own customer, or never used jobs at all. The convention is worked out from the file itself, because it decides how clients and matters are rebuilt in a legal system.
Trust held in ordinary accounts
There is no trust ledger in the product. Firms record client money through a bank account and a liability account, sometimes with a sub-account or job per client. The balance per client is rebuilt from those postings and agreed to the trust bank reconciliation before it opens in the new system.
Items drive the invoices
Invoice lines are items, and each item points to an income account. Time is billed through service items with a rate. In a practice system those become activity codes and rates per lawyer. The item list is mapped line by line, since it carries both the wording clients saw and the account the income went to.
One company file
Everything is in a single company file that can be backed up and copied. Working from a copy leaves the live file alone during the analysis. After cutover the last backup and a working installation are kept so prior-year reports and audit queries can still be answered from the original.
What Intuit’s own export covers
Intuit documents exports of lists and transactions to Excel, CSV and its IIF format, and a separate route that moves lists to QuickBooks Online without transaction history. For a practice system the invoices, payments and unbilled time matter more than the lists, so the transaction detail is taken as well.
Where it is going
Arriving in Filevine
Loading a firm into Filevine depends on the project types being built first. Until the sections and fields exist there is nowhere for the data to go, so configuration and migration are planned together. The old system’s parties, insurers, providers and key dates are mapped to sections, and its notes and emails are loaded into each project’s activity feed.
Project types before data
Each area of practice needs a project type with its sections, fields and phases defined in the Customs Editor. Changes made there apply to every project of that type. The types are drafted from the old system’s data, tested with a few real cases, and only then is the bulk load run.
One contact card per person
Contacts are held as contact cards. A doctor or adjuster who appears on many projects is best loaded as one card, not one for each project. Duplicates in the old system are merged before loading where they can be identified. Loading them as they are produces several cards for the same person, and staff then pick the wrong one when adding a party.
Lists become collection items
Anything the old system held as a list against a matter, such as providers, liens, insurance policies or expenses, is loaded as items in a collection section. Each column needs a matching field. Totals per project are compared with the old system afterwards, since those figures feed the settlement and disbursal sheets.
History goes into the feed
File notes, emails and completed tasks from the old system are loaded into the activity feed with their original dates and authors. Authors must exist as users or be recorded in the text. The feed is long on an old case, so staff are shown how to filter it before go-live.
Billing is a separate switch
The Billing section only appears once Billing is enabled for the firm. Time entries, invoices and trust balances from the old system need that in place before they can be loaded. A firm that leaves it off can still record case costs in a collection section built for the purpose.
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 QuickBooks Desktop holds and how its records link, then agree with you, field by field, where each piece will sit in Filevine. 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 QuickBooks Desktop, before extraction. It is not always possible to find every one, so some may carry across.
Trial load
The data is loaded into Filevine as a trial and checked against QuickBooks Desktop: record counts, trust and debtor totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in QuickBooks Desktop are frozen for an agreed window, the data is collected a final time and Filevine 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. QuickBooks Desktop 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 QuickBooks Desktop 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 QuickBooks Desktop holds
What is in it, how its records link, and where each piece would sit in Filevine. 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 Filevine
Loaded data is not yet a working system. This is what NewLaw sets up in Filevine, beyond the migration, so that people can work in it from the first day.
Filevine arrives as a platform to be configured, and most of the implementation is design. Someone has to decide what a project looks like for each kind of work the firm does, what moves it from one phase to the next, and who can see what. Those decisions are made with the people who run the files, then built and tested.
Set-up decisions in Filevine
- Design project types, sections and fields for each practice area
- Define phases and the tasks each phase should trigger
- Build document templates that fill from project fields
- Set teams, permissions and protected sections for restricted matters
- Decide whether Billing and Payments are switched on
- Connect Lead Docket so signed leads become projects
Questions
QuickBooks Desktop to Filevine: what firms ask
Should we keep QuickBooks for the books and only move billing?
That is a common arrangement. A practice system takes over time, invoices and trust, and posts summary entries to the ledger. What has to be clear is which system owns receivables from the cutover date, so the same invoice is not counted in both. That line is drawn in the analysis.
Can Desktop transaction history go into another system?
Lists and open balances are the straightforward part. Full transaction history depends on the destination: a ledger will take journals and invoices, a practice system generally wants only matter-related billing. Years that are closed are usually left in the company file, which stays readable for as long as the firm keeps a working copy of the program.
We tracked matters as jobs. Is that usable?
It is the best case. Each job has a customer above it and its own invoices, payments and billable time, which is close to a matter. Job names are tidied in QuickBooks first, since they were often typed freely, and then become matter names or numbers.
Do trust balances in QuickBooks Desktop have a place in Filevine?
In part. Trust accounts sit in Payments by Filevine. Loading history is confirmed in the analysis. The analysis sets out which trust records have a place in Filevine and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.
Does everything in QuickBooks Desktop have a place in Filevine?
Most of it does on paper. Documents, emails, calendar entries, the firm’s accounts and custom fields 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 Filevine is kept as a readable archive, and you see which before the move.
What has to be decided before QuickBooks Desktop data is loaded into Filevine?
Time entries, billing records, trust ledgers and templates are carried with mapping, so each mapping is agreed with you first. Documents, emails, calendar entries, the firm’s accounts 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 QuickBooks Desktop and into Filevine
Other destinations from QuickBooks Desktop
Other systems that move into Filevine
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.
QuickBooks Desktop and Filevine are the names and marks of their owners, used here only to identify the two systems.
Moving from QuickBooks Desktop to Filevine?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.