Data migration route
QuickBooks Online to Litify migration
QuickBooks Online is a cloud accounting and billing system, and Litify is a cloud case management system. Only part of what QuickBooks Online holds has a place in a case file: clients and jobs move, and the table shows how much of the billing side does.
QuickBooks OnlineCloud- Matters: Carried across
- Contacts: Carried across
- Documents: Carried across
- Time and expenses: Carried across
- Billing: Carried with mapping
- Custom fields: Carried with mapping
- Templates: Carried with mapping
- Notes: Confirmed in the analysis
- Tasks: Confirmed in the analysis
- Trust money: Confirmed in the analysis
- Firm accounts: Confirmed in the analysis
- Intake: Confirmed in the analysis
LitifyCloud- 4 carried
- 3 mapped
- 5 to confirm
What moves
What moves from QuickBooks Online to Litify
Each row is a kind of record QuickBooks Online 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 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; firms use sub-customers or projects under a customer. | Has a placeMatters, by case type. | Carried across |
| ContactsClients, other parties and referrers | Held in partCustomers, vendors and employees. | Has a placeLoaded as parties and connected by roles. | Carried across |
| DocumentsFiles stored in or linked from the system | Held in partFiles attached to transactions and customer records. | Has a placeLoaded to the document component and attached to matters. | Carried across |
| NotesFile notes, matter notes and contact notes | Held in partInternal notes on customer records and memos on transactions. | To be confirmed | Confirmed in the analysis |
| TasksTo-dos and workflow steps assigned to people | To be confirmed | Has a place | Confirmed in the analysis |
| Time and expensesTime and expense entries, billed and unbilled | HeldTime activities by employee and customer, with billable hours added to invoices. | Has a placeTime entries on the matter. | Carried across |
| BillingInvoices, payments and debtor balances | HeldEstimates, invoices, sales receipts, payments and receivables reports. | 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 partTrust and general retainers are tracked through the chart of accounts. | To be confirmed | Confirmed in the analysis |
| Firm accountsGeneral ledger, office account and payables | HeldChart of accounts, bills, expenses, bank feeds and journal entries. | To be confirmed | Confirmed in the analysis |
| Custom fieldsFields and record types the firm added itself | Held in partEnhanced custom fields on forms and profiles in the Advanced plan. | Has a placeCustom fields are created before loading. | Carried with mapping |
| TemplatesPrecedents, document templates and automation | Held in partInvoice templates and recurring invoices. | Has a place in partTemplates are rebuilt in Litify’s document generation. | Carried with mapping |
| IntakeLeads, enquiries, intake forms and pipelines | To be confirmed | Has a placeLoaded as intakes. | Confirmed in the analysis |
What the plans mean
- Carried across
- Litify has a place for this kind of record. It is loaded there and checked against QuickBooks Online.
- 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. QuickBooks Online 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 QuickBooks Online as reports and ledgers that open without it, and the firm decides where its accounts run from then on. If QuickBooks Online 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.
Both are hosted by their makers, so nothing is collected from the firm’s office. What can be taken out of QuickBooks Online depends on its export tools and on what its maker provides on request, and that is confirmed during the analysis, before a date is set. The subscription to QuickBooks Online is kept running until the checks on Litify are finished.
Where the data is now
Leaving QuickBooks Online
A firm leaving QuickBooks Online is replacing its ledger or taking billing out of it into a practice system. The data is in Intuit’s cloud and comes out as lists and reports. Customers, sub-customers and projects have to be read as clients and matters, and any trust money has to be rebuilt per client from the accounts the firm set up for it.
Sub-customers and projects
Firms record matters as sub-customers, as projects, or not at all. Projects exist only on the Plus and Advanced plans, so a firm that upgraded part-way may have both. The mapping to clients and matters is written from what is actually in the customer list, not from how the firm describes its set-up.
Trust as a liability account
Client money sits in a bank account with a liability account against it, using the Trust Accounts - Liabilities detail type. The ledger gives the total owed to clients, and a balance for each client only if every posting named the customer. Per-client balances are derived from the transactions and agreed to the bank before they open as trust ledgers elsewhere.
Feeds from other systems
Invoices in the file may have been created by a connected time or practice system and copied in. Those are duplicates of records held elsewhere. Before anything is moved, each connected app is identified, so billing history is taken from the system that created it and the ledger keeps only its postings.
Reports are views
Lists and reports export to Excel or CSV. A report is a view, so the same invoice can appear in several. Extraction is planned around transaction-level reports with fixed date ranges, and each is totalled against the trial balance for the same period, which shows up anything counted twice or missed.
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 QuickBooks Online and checking each trial against QuickBooks Online.
Analysis
We read what QuickBooks Online 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 QuickBooks Online, 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 QuickBooks Online: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.
Cutover
Changes in QuickBooks Online 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 QuickBooks Online as at the cutover date. QuickBooks Online 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 Online 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 Online 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
QuickBooks Online to Litify: what firms ask
Can QuickBooks Online replace our practice management system?
Only the financial part of it. It will hold clients as customers, bill them, track what they owe and keep the firm’s ledger. It has no matter file, court diary or conflict search. Firms that move their books here usually keep or add a practice system for the legal work.
How is trust money handled in QuickBooks Online?
Through the chart of accounts. A separate bank account holds the money and a liability account shows that it belongs to clients, with each receipt and payment posted against the client’s customer record. Whether that satisfies the trust rules in your jurisdiction is checked with your accountant before any balances are loaded.
Do our matter numbers survive?
They can be kept as part of the sub-customer or project name. A consistent format is chosen first, for example client name with the matter number after it, so the customer list sorts sensibly and reports can be filtered by matter. Whether a separate field is also used is settled in the analysis.
Do trust balances in QuickBooks Online 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 QuickBooks Online 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 QuickBooks Online have a place in Litify?
Most of it does on paper. Notes, tasks, trust ledgers, the firm’s accounts and intake records 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 QuickBooks Online data is loaded into Litify?
Billing records, custom fields and templates are carried with mapping, so each mapping is agreed with you first. Notes, tasks, trust ledgers, the firm’s accounts and intake records 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 Online and into Litify
Other destinations from QuickBooks Online
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.
QuickBooks Online and Litify are the names and marks of their owners, used here only to identify the two systems.
Moving from QuickBooks Online 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.