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

Data migration route

QuickBooks Desktop data to SQLite

QuickBooks Desktop is a desktop accounting and billing system, and SQLite is a store of data kept as files the firm holds. This is not a move to a new working system: the route writes out what QuickBooks Desktop holds and keeps it readable and open to queries.

FromQuickBooks DesktopDesktop
  1. Matters: Exported in full
  2. Contacts: Exported in full
  3. Notes: Exported in full
  4. Tasks: Exported in full
  5. Time and expenses: Exported in full
  6. Billing: Exported in full
  7. Trust money: Exported in full
  8. Firm accounts: Exported in full
  9. Documents: Confirmed in the analysis
  10. Emails: Confirmed in the analysis
  11. Calendar: Confirmed in the analysis
  12. Custom fields: Confirmed in the analysis
ToSQLiteFiles
  1. Templates: Kept as a readable archive
Readable archiveNo place in SQLite
  • 8 carried
  • 4 to confirm
  • 1 archived
What the two products hold. The analysis confirms it field by field.

What moves

What moves from QuickBooks Desktop to SQLite

Each row is a kind of record QuickBooks Desktop holds, whether SQLite has a place for it, and what is planned. On this route eight kinds of record carry across, one kind has no place in SQLite and is archived and four kinds are confirmed in the analysis.

Records in QuickBooks Desktop and their place in SQLite
RecordIn QuickBooks DesktopIn SQLiteWhat 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 placeA matters table keyed by matter number.Exported in full
ContactsClients, other parties and referrersHeldCustomers, vendors, employees and other names.Has a placeContacts and their roles on matters as linked tables.Exported in full
DocumentsFiles stored in or linked from the systemTo be confirmedHas a place in partListed in a table; the files themselves stay in folders beside the database.Confirmed in the analysis
EmailsEmails saved to matters or to the storeTo be confirmedHas a place in partAs message files in folders, indexed in a table.Confirmed in the analysis
NotesFile notes, matter notes and contact notesHeld in partNotes are one of the lists kept in the company file.Has a placeA notes table linked to matters.Exported in full
CalendarAppointments, court dates and deadlinesTo be confirmedHas a placeA table of dated entries, with no calendar view.Confirmed in the analysis
TasksTo-dos and workflow steps assigned to peopleHeld in partA to-do list.Has a placeA table of tasks and their status at the final date.Exported in full
Time and expensesTime and expense entries, billed and unbilledHeldTime against customers and jobs, billable or not.Has a placeA table of time and expense entries.Exported in full
BillingInvoices, payments and debtor balancesHeldEstimates, invoices, credit memos and customer payments.Has a placeInvoice and receipt tables; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesHeld in partNo trust ledger; client funds are tracked through bank and liability accounts.Has a placeTrust transactions as rows, for look-up and not for accounting.Exported in full
Firm accountsGeneral ledger, office account and payablesHeldChart of accounts, vendor bills, checks, deposits and general journal entries.Has a placeLedger journals as rows, where the source held them.Exported in full
Custom fieldsFields and record types the firm added itselfTo be confirmedHas a placeColumns added to the table they belonged to.Confirmed in the analysis
TemplatesPrecedents, document templates and automationHeld in partInvoice and form templates, which can be exported and imported.No placePrecedent files are kept in folders, not in the database.Kept as a readable archive

What the plans mean

Exported in full
SQLite has a place for this kind of record. It is loaded there and checked against QuickBooks Desktop.
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
SQLite 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

Not a new system. A complete copy the firm can query.

Writing QuickBooks Desktop out to SQLite is not a migration into a new working system. Nobody will open a matter there on Monday morning. The aim is a complete, faithful copy that can be queried and reported on after the old system is gone. So the rules change. Nothing is cleaned or merged unless the firm asks, because an archive should show the records as they were. Every table and field is carried, including those a new system would have had no place for.

What makes an archive usable is the description that goes with it. The export is delivered with a plain account of each table: what it holds, how it joins to the others, what the codes mean. Record counts and financial totals are agreed to the reports in QuickBooks Desktop as at the export date, so the archive can stand as the record. Documents are exported beside the data with a table linking each file to its matter. Access is restricted, since the archive holds everything the live system did.

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 QuickBooks Desktop stays untouched until the copy in SQLite has been checked.

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

A SQLite archive suits a firm that wants the old system’s records kept, seldom consulted, and free of any server or subscription. Everything structured goes into one file. That simplicity moves the responsibility elsewhere: the file has no security of its own and no administrator watching it, so where it is stored and who can reach it are the real decisions.

  1. One file, kept with the archive

    Matters, contacts, time, invoices and trust transactions become tables in a single file. It is stored with the firm’s closed-matter records and can be copied like any document. A checksum recorded when the file is finalised lets anyone confirm, years later, that the copy they hold has not been altered, and the firm decides whether to keep one.

  2. No logins inside the file

    SQLite has no users or passwords. Anyone who can open the file can read every client’s ledger. Protection comes from where it is kept, such as a restricted folder or an encrypted volume, and that choice is the firm’s. It can suit an archive consulted by two people, and it is said plainly so nobody assumes otherwise.

  3. Built for reading, not sharing

    Only one program can write to the file at a time, and SQLite’s authors point people to a client/server database where many users share data over a network. A finished archive never meets that limit. It is the reason SQLite is used here for records that are closed and not for anything staff still update.

  4. Documents stay outside it

    Documents remain ordinary files in matter folders, and a table in the database lists each one with its matter, title, dates and path. Keeping them as files means they open with a double-click and can be handed to a client. The table is how a file is found by matter number instead of by guessing its name.

  5. Someone has to open it

    SQLite publishes its own command-line program for opening a database file, and other tools read the format too. None of that helps if nobody remembers how. Saved queries for the usual look-ups and a short note on which tool to use can sit in the same folder as the file, and the firm decides what it needs.

More about moving into SQLite

How NewLaw runs it

Four steps, in this order.

This route produces an archive, not a working system, so the steps are about completeness and proof.

  1. Analysis

    We read what QuickBooks Desktop holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything QuickBooks Desktop holds is in scope unless you take it out.

  2. Clean-up, if you want it

    An archive should show the records as they were, so nothing is merged or corrected unless you ask. Where the copy is also meant for reporting, duplicate and inconsistent entries are tidied in a working copy and the original values are kept beside them.

  3. Trial export

    The data is written to SQLite as a trial and checked against QuickBooks Desktop: record counts, totals where QuickBooks Desktop holds money, the links between records, and a sample of documents opened from the export. Exceptions are listed for you to decide.

  4. Final export

    After the last day of work in QuickBooks Desktop, the export is run a final time and checked again. There is nothing to go live. QuickBooks Desktop is kept read only until you are satisfied the copy answers what you need, and it is handed over with a written description of its contents.

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 toSQLite

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

Structure, permissions and handover

SQLite is a place to keep data, not a system staff work in each day. What is agreed is how the data is laid out, who can reach it, and what is handed over with it.

There is nothing to install on a server and nothing to license. The work is in making the file usable and safe to keep: naming it, documenting its tables, storing it where the firm’s records policy says archives go, and checking that a member of staff can open it and find a matter. Whether a second copy is held somewhere separate is the firm’s call.

What is agreed and set up

  • File name, storage location and whether a second copy exists
  • Whether a checksum is recorded for later verification
  • Saved queries for matter, ledger and document look-ups
  • Which tool staff will use to open the file
  • Who may open the folder the file sits in
  • Retention period and destruction date noted beside the file

Questions

QuickBooks Desktop to SQLite: 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.

Does the copy in SQLite hold trust ledgers from QuickBooks Desktop?

Yes. Trust transactions as rows, for look-up and not for accounting. Trust ledgers are written out with the rest, and counts and totals are agreed to the reports in QuickBooks Desktop as at the export date.

What happens to records SQLite has no place for?

On this route that is templates. 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 is written out to SQLite?

Documents, emails, calendar entries and custom fields are confirmed in the analysis. The firm also decides who may open the archive and how long it is kept.

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 SQLite are the names and marks of their owners, used here only to identify the two systems.

Moving from QuickBooks Desktop to SQLite?

Tell us what you are moving. You get a plan and a fixed price after the analysis.

We reply within one business day.