Skip to content
NEWLAW.COM
+61 1300 495 281
Let’s talk

Data migration route

QuickBooks Desktop to Litify migration

QuickBooks Desktop is a desktop accounting and billing system, and Litify 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.

FromQuickBooks DesktopDesktop
  1. Matters: Carried across
  2. Contacts: Carried across
  3. Tasks: Carried across
  4. Time and expenses: Carried across
  5. Billing: Carried with mapping
  6. Templates: Carried with mapping
  7. Documents: Confirmed in the analysis
  8. Emails: Confirmed in the analysis
  9. Notes: Confirmed in the analysis
  10. Calendar: Confirmed in the analysis
  11. Trust money: Confirmed in the analysis
  12. Firm accounts: Confirmed in the analysis
  13. Custom fields: Confirmed in the analysis
ToLitifyCloud
  • 4 carried
  • 2 mapped
  • 7 to confirm
What the two products hold. The analysis confirms it field by field.

What moves

What moves from QuickBooks Desktop to Litify

Each row is a kind of record QuickBooks Desktop holds, whether Litify has a place for it, and what is planned. On this route four kinds of record carry across, two kinds need mapping and seven kinds are confirmed in the analysis.

Records in QuickBooks Desktop and their place in Litify
RecordIn QuickBooks DesktopIn LitifyWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partNo matter record; clients and matters are kept as customers and customer jobs.Has a placeMatters, by case type.Carried across
ContactsClients, other parties and referrersHeldCustomers, vendors, employees and other names.Has a placeLoaded as parties and connected by roles.Carried across
DocumentsFiles stored in or linked from the systemTo be confirmedHas a placeLoaded to the document component and attached to matters.Confirmed in the analysis
EmailsEmails saved to matters or to the storeTo be confirmedHas 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 notesHeld in partNotes are one of the lists kept in the company file.To be confirmedConfirmed in the analysis
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeCalendar events on the matter.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeld in partA to-do list.Has a placeCarried across
Time and expensesTime and expense entries, billed and unbilledHeldTime against customers and jobs, billable or not.Has a placeTime entries on the matter.Carried across
BillingInvoices, payments and debtor balancesHeldEstimates, invoices, credit memos and customer payments.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 balancesHeld in partNo trust ledger; client funds are tracked through bank and liability accounts.To be confirmedConfirmed in the analysis
Firm accountsGeneral ledger, office account and payablesHeldChart of accounts, vendor bills, checks, deposits and general journal entries.To be confirmedConfirmed in the analysis
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeCustom fields are created before loading.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partInvoice and form templates, which can be exported and imported.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 QuickBooks Desktop.
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 Desktop 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 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. 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 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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving off QuickBooks Desktop

Where it is going

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

More about moving into Litify

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 Desktop and checking each trial against QuickBooks Desktop.

  1. 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 Litify. Anything with no place there comes across as a note or stays behind, and you see which before the move.

  2. 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.

  3. Trial load

    The data is loaded into Litify as a trial and checked against QuickBooks Desktop: record counts, financial totals, the links between records, document dates. Exceptions are listed for you to decide.

  4. Cutover

    Changes in QuickBooks Desktop 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 Desktop as at the cutover date. 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

Step 1 of 5: Start with the route

Moving fromQuickBooks Desktop
Moving toLitify

The route comes from this page. Four short steps follow. Nothing you send commits your firm to anything.

What happens after you send it

  1. A free first call

    We go through your answers with you and ask about anything they leave open.

  2. An analysis of what QuickBooks Desktop 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.

  3. 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 Desktop to Litify: 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 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 Desktop 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 Desktop have a place in Litify?

Most of it does on paper. Documents, emails, notes, calendar entries, trust ledgers, 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 Litify 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 Litify?

Billing records and templates are carried with mapping, so each mapping is agreed with you first. Documents, emails, notes, calendar entries, trust ledgers, 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.

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.

How we do itDiscovery to rollout, step by step

QuickBooks Desktop and Litify are the names and marks of their owners, used here only to identify the two systems.

Moving from QuickBooks Desktop 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.