Data migration route
QuickBooks Desktop to Clio Manage migration
QuickBooks Desktop is a desktop accounting and billing system, and Clio Manage is a cloud practice management system. The financial records lead: balances and open items move, and the matters in Clio Manage are built around them.
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
- Custom fields: Confirmed in the analysis
Clio ManageCloud- Firm accounts: Kept as a readable archive
- 4 carried
- 4 mapped
- 4 to confirm
- 1 archived
What moves
What moves from QuickBooks Desktop to Clio Manage
Each row is a kind of record QuickBooks Desktop holds, whether Clio Manage has a place for it, and what is planned. On this route four kinds of record carry across, four kinds need mapping, one kind has no place in Clio Manage and is 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 partNo matter record; clients and matters are kept as customers and customer jobs. | Has a placeImported from a matters template, after contacts. | Carried across |
| ContactsClients, other parties and referrers | HeldCustomers, vendors, employees and other names. | Has a placePeople and companies, with related contacts linked to matters by a separate template. | Carried across |
| DocumentsFiles stored in or linked from the system | To be confirmed | Has a placeFiled under the matter; Clio scopes document migration separately from data. | Confirmed in the analysis |
| EmailsEmails saved to matters or to the store | To be confirmed | Has a placeHeld as communications on the matter, with phone logs. | 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 placeMatter notes and contact notes each have a template. | Carried across |
| CalendarAppointments, court dates and deadlines | To be confirmed | Has a placeCalendar events have a migration template. | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | Held in partA to-do list. | Has a placeTasks have a migration template. | Carried across |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime against customers and jobs, billable or not. | Has a place in partUnbilled time entries load; billed time entries do not, by Clio’s migration guide. | Carried with mapping |
| BillingInvoices, payments and debtor balances | HeldEstimates, invoices, credit memos and customer payments. | Has a place in partAn outstanding balance loads as one line per matter; past invoices do not. | 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 partA trust balance loads as one line per matter or contact; past transactions do not. | Carried with mapping |
| Firm accountsGeneral ledger, office account and payables | HeldChart of accounts, vendor bills, checks, deposits and general journal entries. | No placeNot in Clio Manage. Books sit in a linked accounting package, or in Clio Accounting where Clio offers it. | Kept as a readable archive |
| Custom fieldsFields and record types the firm added itself | To be confirmed | Has a placeCreated first, then filled from the custom field templates. | Confirmed in the analysis |
| TemplatesPrecedents, document templates and automation | Held in partInvoice and form templates, which can be exported and imported. | Has a placeRebuilt as Clio document templates with its merge fields. | Carried with mapping |
What the plans mean
- Carried across
- Clio Manage has a place for this kind of record. It is loaded there and checked against QuickBooks Desktop.
- Carried with mapping
- Clio Manage 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
- Clio Manage has no place for it. It is exported in a format that opens without QuickBooks Desktop 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
Time, bills and balances move. How much history is a decision.
Coming from an accounting or billing system, the records that count are balances: unbilled time, unpaid invoices, client funds, the ledger. A practice management system takes these as opening positions on a matter. So every client and job in QuickBooks Desktop needs a matter to land on, and the first piece of work is building that matter list, often from client and project codes that were never meant to be matter numbers.
How much history to bring is the main choice. Paid invoices from years ago can be loaded as records, kept as PDF copies on the matter, or left in a read-only copy of QuickBooks Desktop. Most firms bring open items and a period of history, and keep the rest as reports. Opening balances in Clio Manage are agreed to the trial balance and aged debtors from QuickBooks Desktop as at the cutover date, and that load is rehearsed before it is done for real.
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. Clio Manage 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 Clio Manage
Clio Manage is loaded through its migration templates, one spreadsheet per kind of record, imported in a fixed order with contacts first. Clio’s own migration guide is plain about the limit: balances come across, financial history does not. So a load into Clio is planned as records plus opening positions, with the old system kept for the history behind them.
Matters link by client name
The matters template ties each matter to its client by an exact match on first name, last name or company name. A client spelt two ways in the old system becomes two contacts, or a matter assigned to an unknown client. This is why contact clean-up is finished before the first trial load, not after it.
Decide the numbering scheme first
Clio numbers imported matters itself unless the account is set to manual numbering, in which case the old number is supplied in the template. That setting and the firm’s preferred scheme are decided before any matter is loaded. The Client Reference field is available for an old file number the firm still wants to see.
Balances, one line each
Under Clio’s standard migration, an outstanding balance arrives as one line per matter and a trust balance as one line per matter or contact. Past invoices, billed time, payments and trust transactions are listed as data that cannot be migrated. The trust total is reconciled against the old system’s closing report on the trial load.
Custom fields must exist
Matter and contact custom fields are created in Clio before their values are imported, each with a field type. Accounts set up for a particular practice area come with preconfigured fields and matter templates, which affects the mapping. We compare those with the old system’s fields and add only what is missing.
Rates and permissions by hand
Billable rates for users, clients and matters are not part of an import. Neither are user permissions or settings. They are entered in Clio during set-up from a schedule the firm confirms, and a sample of imported unbilled time is checked against that schedule before the trial load is signed off.
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 Clio Manage. 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 Clio Manage 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 Clio Manage 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 Clio Manage. 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 Clio Manage
Loaded data is not yet a working system. This is what NewLaw sets up in Clio Manage, beyond the migration, so that people can work in it from the first day.
Much of a Clio Manage set-up is firm-wide settings. The numbering scheme, practice areas, matter stages, billing preferences and trust accounts apply to everyone, so they are agreed once and early. Trust and accounting features are not the same in every country Clio sells in, so the firm’s own region is checked first. Document templates and custom fields follow. Email and document integrations are then installed for each user and tested on a real matter.
Set-up decisions in Clio Manage
- Matter numbering scheme, practice areas and matter stages
- Custom fields for matters and contacts, by practice area
- Document templates with merge fields, uploaded from Word or PDF
- Billing settings, user and client rates, and trust accounts
- Roles and permissions for each user
- Outlook add-in, Clio Drive and the accounting connection
Questions
QuickBooks Desktop to Clio Manage: 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 Clio Manage?
In part. A trust balance loads as one line per matter or contact; past transactions do not. The analysis sets out which trust records have a place in Clio Manage and which are kept as an archive, and the trust cutover is rehearsed on a full trial load before the real one.
What happens to records Clio Manage has no place for?
On this route that is the firm’s accounts. They are exported from QuickBooks Desktop 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 QuickBooks Desktop data is loaded into Clio Manage?
Time entries, billing records, trust ledgers and templates are carried with mapping, so each mapping is agreed with you first. Documents, emails, calendar entries 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 Clio Manage
Other destinations from QuickBooks Desktop
Other systems that move into Clio Manage
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 Clio Manage are the names and marks of their owners, used here only to identify the two systems.
Moving from QuickBooks Desktop to Clio Manage?
Tell us what you are moving. You get a plan and a fixed price after the analysis.
We reply within one business day.