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

Data migration route

QuickBooks Online data to SQLite

QuickBooks Online is a cloud 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 Online holds and keeps it readable and open to queries.

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

What moves

What moves from QuickBooks Online to SQLite

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

Records in QuickBooks Online and their place in SQLite
RecordIn QuickBooks OnlineIn SQLiteWhat is planned
MattersMatters or cases, with their numbers, types, parties and statusHeld in partNo matter record; firms use sub-customers or projects under a customer.Has a placeA matters table keyed by matter number.Exported in full
ContactsClients, other parties and referrersHeld in partCustomers, vendors and employees.Has a placeContacts and their roles on matters as linked tables.Exported in full
DocumentsFiles stored in or linked from the systemHeld in partFiles attached to transactions and customer records.Has a place in partListed in a table; the files themselves stay in folders beside the database.Exported with mapping
NotesFile notes, matter notes and contact notesHeld in partInternal notes on customer records and memos on transactions.Has a placeA notes table linked to matters.Exported in full
TasksTo-dos and workflow steps assigned to peopleTo be confirmedHas a placeA table of tasks and their status at the final date.Confirmed in the analysis
Time and expensesTime and expense entries, billed and unbilledHeldTime activities by employee and customer, with billable hours added to invoices.Has a placeA table of time and expense entries.Exported in full
BillingInvoices, payments and debtor balancesHeldEstimates, invoices, sales receipts, payments and receivables reports.Has a placeInvoice and receipt tables; invoice PDFs kept as files.Exported in full
Trust moneyTrust or client account ledgers and balancesHeld in partTrust and general retainers are tracked through the chart of 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, bills, expenses, bank feeds and journal entries.Has a placeLedger journals as rows, where the source held them.Exported in full
Custom fieldsFields and record types the firm added itselfHeld in partEnhanced custom fields on forms and profiles in the Advanced plan.Has a placeColumns added to the table they belonged to.Exported with mapping
TemplatesPrecedents, document templates and automationHeld in partInvoice templates and recurring invoices.No placePrecedent files are kept in folders, not in the database.Kept as a readable archive
IntakeLeads, enquiries, intake forms and pipelinesTo be confirmedHas a placeAn enquiries table, where the source tracked them.Confirmed in the analysis

What the plans mean

Exported in full
SQLite has a place for this kind of record. It is loaded there and checked against QuickBooks Online.
Exported with mapping
SQLite 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
SQLite has no place for it. It is exported in a format that opens without QuickBooks Online 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 Online 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 Online 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.

QuickBooks Online is hosted by its maker and SQLite sits on equipment the firm controls. The data leaves a service that was backed up for the firm and arrives somewhere the firm must back up itself, so backup and access are arranged before the export is copied in. What QuickBooks Online will release depends on its export tools, and that is confirmed in the analysis.

Where the data is now

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.

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

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

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

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

More about moving off QuickBooks Online

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 Online holds, table by table, and agree with you what the copy in SQLite must be able to answer later. Everything QuickBooks Online 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 Online: record counts, totals where QuickBooks Online 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 Online, the export is run a final time and checked again. There is nothing to go live. QuickBooks Online 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 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

Step 1 of 5: Start with the route

Moving fromQuickBooks Online
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 Online 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 Online to SQLite: 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.

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

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 Online 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 Online 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 Online is written out to SQLite?

Documents and custom fields are exported with mapping, so each mapping is agreed with you first. Tasks and intake records 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 Online and SQLite are the names and marks of their owners, used here only to identify the two systems.

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