Disclaimer: QuickBooks.ninja is an independent site and is not affiliated with, endorsed by, or sponsored by Intuit Inc. "QuickBooks" is a registered trademark of Intuit Inc., used for identification and reference purposes only. See our Terms.

Guides / best-practices · 6 min read · Updated August 2026

How to Back Up QuickBooks Online to SQL Server

QuickBooks Online has no full-backup button. What the built-in exports cover, what they miss, and how to get a complete, verified SQL Server copy of your company that you own.

Your QuickBooks Online company holds years of financial history. You can use that history every day. You cannot hold it. There is no database file on your disk, and there is no full-backup button in the product.

Most businesses discover this at a bad moment: an audit request, a company sale, or the decision to leave the subscription. This guide explains what you can export yourself, what no export can reach, and when a SQL Server copy is the right answer.

What you can export yourself

QuickBooks Online gives you three built-in routes:

  1. Report exports. Any report can go to Excel. This is fine for one number on one day. It is not an archive. The exports are disconnected snapshots, and nothing ties them together.
  2. The Export Data tool. It produces a ZIP of Excel reports and some lists. It leaves out transaction line detail and the links between records.
  3. Online Backup and Restore. Only on the Advanced plan. It rolls the whole company back to an earlier point. It does not hand you a copy you can open.

What no export can reach

Some data never leaves QuickBooks Online, no matter which tool asks for it. The audit log, bank feed items still in For Review, your user and permission list, bank reconciliation status, tags, and mileage stay inside the product. Payroll detail lives in a separate closed subsystem. Plan for this: export payroll reports and key statements while you still have access, and keep them beside your archive.

When a SQL Server copy is the right answer

A relational copy in Microsoft SQL Server is the strongest form of a QuickBooks Online archive:

  • It is complete. Every list and every transaction, with line-level detail preserved in related tables.
  • It is queryable. Excel, Power BI, and any reporting tool can connect to it. No more exporting screens one report at a time.
  • It is verifiable. A proper delivery reconciles the database totals against a Trial Balance you export yourself. Totals that tie are proof; a vendor's word is not.
  • It is yours. A standard backup file restores on your own server. It needs no subscription and no login to read.

One rule matters before you order any SQL Server copy: a SQL Server backup restores only on the same version or a newer one, never older. Know which SQL Server version you will restore onto, and make sure the database is built for it.

Questions to ask any provider

  1. Which SQL Server versions can you build for, and do you verify mine first?
  2. How do you prove the copy is complete? Ask for reconciliation against your own Trial Balance and aging reports.
  3. Is every table and column documented? A data dictionary inside the database saves your team weeks of guessing.
  4. Is the access read-only? Nothing in your live company should change.
  5. What is excluded? A provider who claims to export the audit log or payroll detail through the API is overpromising. Those limits apply to everyone.

Where to get it done

Our sister site offers this exact service: a complete QuickBooks Online to SQL Server backup with a restorable version-matched backup file, a built-in data dictionary, reconciliation against your own reports, and restore instructions for your IT team. The engineering team behind it also documents the service at e-tech.ca.

Whatever provider you choose, take the copy while your access is healthy. After a cancellation, QuickBooks Online keeps your data read-only for a limited period and then deletes it. An archive you own has no expiry date.