AI Software for Chiropractors: A Data Export Checklist Before You Switch

Before switching AI practice software, a chiropractic clinic should confirm in writing that every patient record, note, image and invoice can leave in a usable format, that the clinic owns that data, and that the contract lets you exit on stated terms. Then run a migration test on twenty real patients before cancelling anything.

The switch itself is rarely what hurts. What hurts is discovering, after the old subscription lapses, that the "export" is a stack of PDFs with no dates in them, or that the templates you spent two years refining do not travel. A practice system holds a decade of clinical history, and AI features make the question sharper because they add new kinds of data: recordings, transcripts, prompts and automated messages. This checklist is for the clinic owner who is about to sign with a new vendor, or about to leave an old one.

Follow me on Instagram@sagnikteaches

Why chiropractic data is harder to move than a contact list

A chiropractic record is not one table. It is several kinds of information, each with its own export problem, and a generic "we can export your data" answer rarely covers all of them.

Connect on LinkedInSagnik Bhattacharya

• Demographics and contacts. Easy: names, addresses, dates of birth. But also consent status for marketing messages, which a new system must respect from day one.
• Clinical notes. SOAP notes, exam findings, outcome questionnaires, X-ray reports, care plans. Long free text with headings the old system supplied and the new one does not.
• Structured clinical fields. Diagnosis and procedure codes, spinal listings, range-of-motion values, pain scales. If these export as a blob of text, you lose the ability to report on them.
• Images and documents. X-rays, posture photos, signed consent forms, referral letters, insurance paperwork. Often stored separately, sometimes at reduced resolution, sometimes with the patient link in a separate file.
• Financial history. Invoices, payments, claims, balances, packages and prepaid visits. Mismatched balances are the commonest day-one complaint after a switch.
• Appointments. Past and future. Future bookings are the ones patients notice.
• AI-generated and AI-related data. Scribe recordings, transcripts, prompts, templates and macros, intake summaries, automated reminder history.

The export checklist, with a way to verify each item

Each question needs a yes shown to you, not told to you. Ask the vendor to produce a sample export from a test patient or from a copy of your data while you watch.

Subscribe on YouTube@sagnikteaches

Who owns the notes, and what the contract must say

As a rule of thumb the clinic is the record keeper and the vendor is a processor acting on your instructions, but the contract is what counts, and some vendors reserve rights over aggregated or de-identified data. Look for six clauses, in the order they matter.

1. Data ownership. States that customer data remains the customer's property and the vendor has no right to use it beyond providing the service.
2. Return of data on exit. Names the formats, the time limit (for example, within 30 days of request) and whether it is free.
3. Deletion on exit. Says how long after termination the vendor deletes data and backups, and provides written confirmation.
4. Notice and minimum term. A monthly rolling contract and an annual lock-in look the same on a pricing page and very different when you want out.
5. Price protection. Whether the price can rise mid-term, and whether AI features can be switched on, charged for and billed to you by default.
6. Use of data for AI. Whether your records or recordings are used to train models and whether this is off by default. For the general problem, how to stop AI tools training on your data explains the settings to look for.

Suggested wording to propose, which a lawyer can tidy up (illustrative, not legal advice):

"Within 30 days of written request, and at no extra charge, the Supplier will deliver a complete export of all Customer Data, including clinical notes, images, financial records, appointment history and templates, in a structured, commonly used, machine-readable format together with a human-readable copy. After the Customer confirms receipt, the Supplier will delete all Customer Data, including backups, within [60] days and confirm this in writing."

If a vendor will not agree to wording like that, ask what they will agree to. The reply is useful either way. For the questions to ask any vendor whose product touches patient data, what to ask before buying any AI tool for a medical practice covers more than this tutorial can.

AI features add three things to the checklist

Practice systems with AI built in, such as ChiroTouch, whose site lists an AI Scribe, custom SOAP templates and smart macros, or a system paired with a separate scribe like Heidi or Jane's add-on, bring data that did not exist in older systems. Ask about each.

• Recordings and transcripts. Are they stored, for how long, and do they come with you? A clinic should usually prefer that they are deleted soon after the note is signed, which also shrinks what has to be migrated. Jane, for example, lets a clinic choose to delete recordings immediately after a draft, after a set number of days, or keep them, so the setting exists to be used.
• Templates, macros and prompts. They represent hours of tuning to your technique and wording. Ask for them as text. If the vendor cannot export them, copy them out by hand into a document before you leave.
• Intake summaries and automated messages. These are generated from patient-entered data. Check whether the summary is saved as part of the record or recreated on demand, because a recreated summary will be gone with the subscription.

For the scribe side specifically, chiropractic tools compared with Heidi and Jane sets out how each handles notes, and consent and data checks before recording covers what patients must be told.

The migration test: twenty patients, five checks

Do not trust a full import until a small one has worked. Many new vendors offer import help: Jane's pricing page says data imports and migrations carry no extra cost and are booked about ten days ahead, and ChiroTouch lists data transfer with a dedicated support team as an onboarding step. Ask what "included" covers in each case (demographics only, or notes, images and balances too), then ask for a sample of twenty patients from your export to be imported into a test environment or a sandbox, and check them yourself.

1. Choose the twenty. Include a new patient, a long-term maintenance patient with hundreds of visits, a child with a guardian, a patient with a prepaid package, a patient with imaging, and one with an outstanding balance. Awkward cases surface the problems.
2. Compare demographics. Names, dates of birth, contact details and marketing consent, side by side with the old system.
3. Compare notes. For each patient open three notes: the first, a mid-course one and the latest. Check dates, headings, author and whether structured fields survived.
4. Compare money. Total balance, last three invoices and any prepaid visits remaining.
5. Compare images and documents. Open one X-ray and one signed form per patient that has them.

Record each check as pass or fail in a simple sheet. Illustrative scoring: 100 checks (20 patients across five areas), and you accept the import when at least 98 pass and every failure has a known cause and a fix. A pattern is more informative than a count. Five patients losing their last note suggests a date-handling bug; three losing prepaid balances suggests the packages table was skipped.

A worked example: a three-chiropractor clinic switching in six weeks

Illustration. A three-chiropractor clinic has 4,800 patient records, about 1,900 active in the last two years, and 31,000 notes. They pay for their current system monthly on a rolling contract, and they are moving to a system that includes an AI scribe. Their plan, week by week:

• Week 1. They ask the old vendor for the export formats, the cost and the lead time, in writing. They also ask the new vendor to confirm what it can import. The old vendor quotes a structured export plus PDFs for notes and images in separate folders; the lead time is ten working days.
• Week 2. They request the first export and, in parallel, copy out their six note templates and twelve macros by hand into a shared document.
• Week 3. The twenty-patient migration test runs in the new vendor's sandbox. Result: 93 of 100 checks pass. The seven failures are all prepaid package balances.
• Week 4. The vendor fixes the package mapping and re-imports. 99 of 100 pass; the failure is one patient's guardian link, fixed by hand.
• Week 5. Full import over a weekend, then the front desk compares the previous day's takings and next week's bookings across both systems. They run both systems side by side for the week with the old one read-only.
• Week 6. Cut over. The old system stays on a read-only plan for three months, then the clinic keeps a verified export on an encrypted drive and in a second secure location, and gives notice.

Total effort: roughly 25 staff hours across six weeks, plus the vendor's time. The clinic does not give notice on the old contract until week 6. That sequence is the point: notice is the last step, not the first.

Mapping old fields to new ones before the import

Most failed imports are mapping failures. The old system calls a field one thing, the new one expects another, and the import quietly drops what it cannot place. Before the test, build a one-page mapping sheet with the new vendor. Illustrative extract:

Keep the sheet. It doubles as documentation if a patient or insurer later asks how their record was transferred.

Retention: what you must still be able to produce

Clinical records often have to be kept for a set period, and for children usually longer. The period depends on where you practise and on your regulator and insurer, so look it up rather than assuming. What matters for a switch is that for that whole period you can produce a complete, readable record of any patient on request, including after the old vendor has gone. Two practical rules help.

1. Test the archive, not the backup. A backup you have never opened is a hope. Open your verified export on a different computer, find three random patients and check the notes, images and balances.
2. Store two copies in two places. An encrypted drive in a locked cabinet and an encrypted cloud store, with a named person who knows where the key is. Write the retention end date for each patient group on a sheet kept with the archive.

Some vendors offer a cheaper way to keep access after you leave. Jane, for example, suggests downgrading to its single-practitioner Balance plan if you will need frequent access after cancelling, and offers short-term access on request otherwise. Ask your old vendor the same question before you give notice, because a read-only option is far easier to negotiate while you are still a paying customer.

Treat the export as patient data in its own right: it has the same confidentiality duties as the live system. The confidentiality checklist for small practices covers access, encryption and who may open it.

A before and after: one macro across two systems

Templates and macros are the part of a chiropractic system that clinicians feel most when it goes missing. Illustration: a clinician has a macro in the old system that expands the shortcut "lbp1" into a full lower-back first-visit exam section.

Old macro (shortcut: lbp1)
Chief complaint: Low back pain, onset [__], mechanism [__].
Pain: [__]/10 at worst, [__]/10 now. Aggravated by [__]; eased by [__].
Exam: Lumbar ROM flexion [__] extension [__]; SLR [__] left [__] right; palpation [__].
Assessment: Mechanical low back pain, no red flags identified [confirm].
Plan: Adjustment [__], advice [__], review in [__] days.

If the new system has a scribe, you can paste the macro into its template field and ask it to fill each blank from the session. The risk is the line "no red flags identified [confirm]": a scribe may confirm it on its own. Rewrite that line as "Red flag screen: [clinician to complete]" in the new template so the tool leaves it blank. Same clinical content, safer behaviour, and a good example of a template that should be reviewed, not just moved.

What switching costs, with the staff time counted

A switch costs more than the subscription difference. Add the following for a realistic budget, using your own figures. Illustrative sum for the three-chiropractor clinic above, with example numbers only: export fee from the old vendor, say $0 to a few hundred dollars (ask); the new vendor's onboarding or import fee, if any (ask); 25 staff hours at the clinic's internal hourly cost; a week or two of reduced booking capacity while staff learn the system, say 10 per cent fewer slots; and an overlap month in which you pay both subscriptions. If the new system saves 30 minutes per clinician per working day on notes, three clinicians over 20 days is 30 hours a month, so the overlap cost is recovered within the first month or two. Do the sum with your own volumes before you decide; if the saving is small, the switch may not be worth it.

What to tell patients and staff

Patients mostly care about three things: appointments are still there, reminders still work, and their information is safe. Send one short message about a week before cut-over, and put the same wording on the front desk script.

"We are moving to a new booking and records system on [date]. Your appointments and records will move with you. You may receive a new confirmation message, and you may see a new patient portal link. If you notice any mistake in your details or appointments, please tell us at the front desk."

If the new system uses an AI scribe, explain that separately, with its own consent step; do not bury it in the migration message. Staff need a one-page cheat sheet of where things live in the new system, and a named person to ask in the first week. Keep a running list of the questions asked, because the same ten questions will come up for each new starter afterwards.

Four ways switches go wrong

• The PDF-only export. The old vendor's idea of "your data" is one PDF per patient. You can read it but not search, report or import it. Fix: insist on a structured export in the contract before you give notice, or keep paying until you have one.
• Notice given too early. The clinic cancels on day one and the old vendor deletes data thirty days later, before the new import is verified. Fix: ask for written confirmation of the deletion date and extend it if needed.
• Future bookings left behind. Patients turn up for appointments the new system never imported. Fix: export bookings last, on cut-over day, and reconcile counts.
• Consent status lost. The new system sends marketing to patients who had opted out. Fix: check marketing consent in the migration test; it is a compliance risk, not just an annoyance.

A written request to send the old and new vendor

Send this on day one. Replies tell you quickly who will be easy to deal with. Illustrative text:

Subject: Data export and exit terms, [clinic name]

Hello [first name],

We are reviewing our practice software and need the following in writing:
1. The formats available for a full export of patient demographics, clinical notes, structured fields, images and documents, invoices and payments, and appointments.
2. Whether recordings, transcripts, templates and macros are included.
3. The cost, the lead time and who performs the export.
4. Our contract's notice period, minimum term and data-deletion timeline after termination.
5. Whether you use customer data to train AI models and how to switch that off.

We will use the answers to plan a migration test before making any decision.

Kind regards,
[your name]

Cut-over day and the first fortnight

On cut-over day, freeze data entry in the old system for an hour, export appointments, import them, and check the day's list with the front desk. For the first fortnight, keep a short log of anything missing or wrong, and fix it while the old system is still available. After two weeks without a serious issue, move the old system to read-only. If you are also introducing a scribe, add it after the data has settled, not on the same day, so that a bad note is not confused with a bad import. The tutorial on reviewing AI-written SOAP notes gives a review routine for the scribe stage. If you would rather map the switch with someone, that is what my AI implementation consultation covers; use the contact page.

Questions chiropractors ask before switching

Can I get my notes out as PDFs only?

PDFs preserve how a record looks but not its structure, so they are a weak export on their own. Ask for a structured export as well, such as CSV or a database file, so patient details, dates, codes and notes can be searched and imported. Keep both, and check a sample of each.

Who owns the clinical notes in my practice software?

Usually the clinic, as the record keeper, owns or controls the clinical record and the vendor processes it for you. But the contract decides, so read the clauses on data ownership, return of data and deletion. If the wording is vague, ask for it to be clarified in writing before you sign.

How long should I keep the old system after switching?

Keep read access for at least as long as your record-retention rule requires, or keep a complete verified export in a safe place. Many clinics keep the old system on a cheaper read-only plan for a few months, then rely on an export they have tested opening.

Does moving to a system with an AI scribe change what I need to export?

Yes. Ask whether audio recordings and transcripts are kept and whether they leave with you, and whether your custom note templates and macros can be exported. Notes created by the scribe are normal clinical notes, but templates and prompts are yours and are easy to lose.

Further reads

• Jane App for Chiropractors: The AI Scribe and Online Booking — What Jane's scribe and booking do for a chiropractic clinic.
• AI Tools for Chiropractors: Report of Findings, Care Plans and Handouts — Report of findings, care plans and handouts.
• AI Scribe Security: Audio, Retention and BAA Vendor Questions — Security questions to ask any scribe vendor.
• Telling Patients You Use AI Note-Taking: Consent Wording That Works — Wording for telling patients about AI note-taking.
• AI Marketing for Chiropractors: Claim Limits and Review Replies — Marketing claim limits once the new system is live.
• A Worked AI Implementation Plan for a Small Medical Practice — A wider implementation plan for a small practice.
• AI Software for Psychologists: Practice Systems With AI Built In, Compared — SimplePractice, Carepatron and Jane compared for a solo psychologist: plan prices, what the AI adds, and the real monthly total for one clinician and three.
• Chiropractic Software With AI: Which Features Are Genuine? — ChiroTouch Rheo, Jane's AI Scribe and ChiroHD checked against their own pages, plus a ten-minute test for separating real AI from marketing.
• AI Contract Review Best Practices for a Private Practice Owner — Use AI as a first read of your lease, supplier and associate agreements: what to redact, which clauses to check, and when a solicitor takes over.
• ChatGPT for Chiropractors: What Is Safe Without a BAA? — A clear line for chiropractic clinics: which ChatGPT jobs are safe with no BAA, which involve PHI, and what a HIPAA-ready route looks like.
• Chiropractic AI for Clinic Owners: Which Admin Jobs to Start With — A clinic owner's order of play for AI: bookings and recalls first, notes with review, marketing within claim limits, no AI diagnosis.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: ChiroTouch home page, Jane pricing page and AI Scribe recording guides (checked November 2026). Export formats are not stated here for any vendor: ask each one to show you.