Data Export Questions to Ask Before You Sign With Any Clinic Software

Every clinic software demo covers the import: how easily your data comes in. Almost none covers the export: how it comes out again when you leave. Yet the export is the clause that decides whether you are a customer or a hostage, and reviews are full of clinics who found out at the end of a contract that getting their own notes back meant a support ticket, a wait and sometimes a fight. The comparison pages on this site put data export in the table for that reason, and this post gives you the seven questions to ask any vendor before you sign, with the answers a good one should give.

Why the export matters more than the import

An import happens once, with the vendor motivated to help. An export happens when you have decided to leave, with the vendor motivated to slow you down, and with years of clinical records at stake that you are required to keep. A practice cannot abandon those records; it has to get them out, complete and readable, or stay.

That asymmetry is why the export deserves more scrutiny than any feature on the demo. A platform with a mediocre diary and a clean export is a platform you can leave in a month. A platform with a brilliant diary and a locked export is a platform you will be arguing with in three years.

The seven questions

1. What exactly do we get back?

Ask for the list. It should include patients and contact details, appointments past and future, clinical notes with dates and authors, documents, images and attachments, signed consent forms, intake answers, messages with their timestamps, invoices and payments, and the audit trail where the vendor can provide one.

Then compare the list with what you put in. The common gaps are attachments ("notes, but not the files"), messages ("we don't export conversations") and the audit trail ("that's internal"). Each gap is a decision you are making now about what you will lose later.

2. In which formats?

Structured data should come as CSV or JSON, with a documented column layout, so the next system can import it. Documents and images should come in their original formats. Notes should come as both structured records and as PDFs per patient, because the next system may not import the structure and you still need something readable.

A single PDF of everything is an archive, not an export. It satisfies record-keeping and nothing else.

3. Self-serve, or a support request?

The question that reviews answer most loudly. Established platforms are described as needing a support request for a full export, with a wait of days or weeks and, in one case, months. A self-serve export, run from your own admin screen at any time, removes the wait, the ticket and the leverage.

If the honest answer is "by request", ask for the service level in writing: how many working days, and what happens if it is missed.

4. How long does it take?

For a self-serve export, minutes. For a request, the vendor should commit to a number of working days. A vendor who will not commit is telling you the answer.

5. What happens to our data after we leave?

Three sub-questions. How long does the account stay readable after cancellation, so you can check the export against it? How long is the data retained before deletion, and can you get a copy during that window? And how is it deleted, so you can tell patients the truth about where their records went?

Reviews describe accounts frozen with the data inside, sometimes over a billing dispute. The contract should say that access to your own data cannot be withheld.

6. Can we test it during the trial?

Load five test patients into the trial, add a note, a document and a message to each, run the export, and open the files. Check that the note has its date and author, the document is the original file, and the message thread is there. If the trial does not include the export, ask the vendor to run one on a demo account while you watch.

Ten minutes of testing here saves a quarter of arguing later.

7. What does the contract say?

Find the clauses on data ownership, export rights, retention and deletion. "The customer owns their data" is a good start and not enough; the clause should say you can export it at any time, in the formats above, and that access cannot be suspended for any reason other than a court order. If the clause is missing, ask for it to be added. A vendor who refuses is answering the whole question.

What reviews show when nobody asked

Reading practitioner reviews across the UK, US and Australia, the export complaints cluster into three:

1. "We had to ask, and wait." The export was a support request with no committed turnaround, and leaving took longer than the notice period.
2. "We got a dump, not an export." PDFs of everything, or CSVs with no attachments, so the new vendor's import was half a migration and half re-typing.
3. "They locked us out." Account access suspended during a dispute, with years of notes inside.

Each of the three has a question above that would have surfaced it before signing.

A clause to ask for

Short enough to paste into an email:

The customer may export all customer data at any time, without charge, in structured and document formats, through a self-serve function or within five working days of a request. Access to customer data shall not be suspended for any reason other than a lawful order. Customer data shall remain accessible for ninety days after termination and be deleted on written request thereafter.

A vendor who signs that is one you can leave. A vendor who will not is one you should not join.

Questions that sound similar and are not

Vendors answer the export question with four different things, and only one of them is an export.

A backup is the vendor's copy of your data for the vendor's disaster recovery. You cannot download it, and it is not yours to restore elsewhere.

An API is an interface a developer can use to pull your data out. If you have a developer, it is better than nothing; if you do not, it is a promise with no one to keep it.

A transfer to the new vendor is the old vendor sending your data straight to the new one. Convenient, and it leaves you without your own copy, which matters if the new vendor's import fails or the two vendors disagree about what was sent.

An export is a complete set of files you can download yourself, in formats another system can read, with the documents included. It is the only one of the four that puts the records in your hands.

When a vendor says "yes, you can get your data", ask which of the four they mean.

How Capra answers the seven

Capra's answers are on the comparison pages beside each competitor's, and they are the same on every page: your data is exportable at any time, in structured and document formats, including notes, documents, messages and invoices; the export is yours to run, not a ticket; your onboarding lead will walk through it with you during the trial if you ask; and the terms say what the clause above says. The practice management software page covers the platform the data lives in, the security page covers how it is protected while it does, and a demo is where you can ask the seven questions and watch the export run.