If you run a chiropractic practice on ChiroTouch, the system quietly accumulates a large volume of patient-specific information that would be genuinely difficult to reconstruct from memory. Demographics, SOAP and treatment notes, appointment history, insurance details, charges, and the ledger all live in one database. On top of that, the Records module lets your team file X-rays, treatment photos, videos, and scanned documents into per-patient electronic folders with nested sub-directories. For a practice that has seen the same patients for five or ten years, that folder tree represents years of clinical context that simply does not exist anywhere else. Treating that data as a single, replaceable file is a risk most office managers underestimate until something goes wrong.

Understanding What a ChiroTouch Backup Actually Covers

One area that catches practices off guard is the patient-file transfer workflow, which ChiroTouch uses when a patient moves between two offices that share the same platform. When an administrator triggers the export, the system bundles the patient's front-desk information, patient notes, treatment notes, and any attached records—photos, videos, X-rays, documents—into a single folder on the server. What is deliberately left out, however, includes chart notes, diagnosis codes, charges, the ledger, insurance information, and the full appointment history. In other words, the transfer gives the receiving office a working snapshot but not the complete financial and scheduling record. If you are the receiving practice and you assume the incoming folder contains everything, you will have gaps in billing history and scheduling context that can take weeks to rebuild. A reliable ChiroTouch backup of your own database, taken before and after any inter-office transfer, is the simplest way to make sure neither side is left with an incomplete picture.

The Records screen adds another layer of complexity. Your team can create a default folder structure that ChiroTouch automatically replicates for every new patient, and individual files can be dragged into sub-folders, previewed, printed, or e-mailed from that same window. Over time, those folders accumulate a mix of intake forms, imaging studies, consent documents, and progress photos. Because the naming convention for default folders is restricted to letters, numerals, and spaces, a single misnamed directory can make a file nearly impossible to locate during an audit or a patient request. Keeping an off-system copy of the entire records tree—rather than relying solely on the live database—gives you a second reference point when you need to pull a specific document quickly.

For practices that are evaluating a switch to a different platform or consolidating locations, the export options deserve a closer look. ChiroTouch can produce reports in PDF, Excel, or Rich Text format, and the patient-file transfer dialog lets you save an export report in any of those three formats before handing credentials to the receiving office. The receiving side must have an identically configured server path and the same license-credential setup before the import will complete. In our experience, the most common failure point in a multi-office data handoff is not the software itself but the assumption that both servers are set up the same way. Before you schedule a transfer, verify that the destination folder exists, that the license ID and access password from the export report are in hand, and that the receiving team has tested their import path with a single dummy patient file.

A practical weekly routine for office managers looks like this: confirm that the ChiroTouch backup job completed without errors, spot-check that the latest patient record and at least one document file are present in the backup, and log the backup date in your internal operations sheet. If you operate more than one location, run the same check at each site and keep a short change log noting any patient transfers, new default-folder additions, or staff account modifications. You do not need a separate IT department to do this; you need a consistent habit, a clear understanding of what data lives where in the system, and a copy of that data that does not depend on the same server holding the live database. That combination is what turns a ChiroTouch backup from a line item in your software contract into a genuine safety net for the practice and the patients who trust you with their records.

Sources and further reading