Independent resource: Not affiliated with, endorsed by, sponsored by or associated with Intuit Inc. Intuit and QuickBooks are registered trademarks of Intuit Inc.
Home Support for QuickBooks Desktop Users Back Up and Restore QuickBooks Desktop Data
Technical resource

Back Up and Restore QuickBooks Desktop Data

A backup is useful only if it can be located, identified and restored. Keep at least one copy outside the computer that runs QuickBooks software before troubleshooting risky changes.

Last reviewed 2026-09-05IndependentNo official-support claim
Quick answer

Back Up and Restore QuickBooks Desktop Data

A backup is useful only if it can be located, identified and restored. Keep at least one copy outside the computer that runs QuickBooks software before troubleshooting risky changes.

Start with these checks

  1. Identify the live company-file location
  2. Create a dated backup
  3. Store a second copy off the local machine
  4. Verify the backup file exists and has a plausible size
  5. Document the restore destination before restoring

Use a diagnostic path, not random fixes

Write down what changed immediately before the problem, the exact product year/edition, Windows version, company-file location and whether the symptom affects one user, one file or every user. That information often identifies the failing layer faster than reinstalling software.

Protect business data first. Before repair, rebuild, reinstall, migration or bulk payroll/accounting changes, make a verified backup and preserve the original company file where practical.

When to stop and escalate

Stop self-troubleshooting when the next step could alter payroll filings, tax calculations, bank transfers, subscription ownership, data integrity or a production server you cannot restore. For account, entitlement or official product-service issues, use the official provider channel rather than sharing credentials with third parties.

What to record for a useful support request

  • Exact QuickBooks software product, year and edition.
  • Windows version and whether the file is local, hosted or on a server.
  • Exact error text or code and the action that triggered it.
  • Whether the issue affects one file/user or all files/users.
  • Recent updates, migrations, permission or network changes.