Who Owns Your Veterinary Practice's Data? (And What Happens When You Try to Leave)

Your practice generates patient records, clinical histories, appointment logs, invoices, and diagnostic data every day. According to the American Veterinary Medical Association, that data belongs to you.

Most veterinary practice management software contracts tell a more complicated story.

This article explains what veterinary practice data ownership actually means, where the gaps between principle and contract exist, what happens in practice when you try to leave a closed system, and what your options look like if you want to own your data in a way you can actually act on.

It is the article no closed PIMS vendor can write about themselves. So we are writing it.

What the AVMA says about your data

In 2019, the American Veterinary Medical Association published its Principles of Veterinary Data Ownership and Stewardship. The principles are specific:

Veterinary practices own their practice data. Control is a necessary condition of data ownership. Practice data should be portable and accessible.

The AVMA also states that data vendors should collect only the minimum required data, retain practice data only for the requisite time period, and that prior consent is the foundation of any legitimate use of practice data.

The AVMA published these principles because the problem was already visible in 2019: practices generate all of the data, but software vendors control the format, the export tools, and the terms of access. The AVMA's answer was to assert, clearly, that practices own what they create in their clinical operations.

The limitation is that these are guidelines. They are not enforceable standards. A PIMS vendor who disagrees with them is not required to change anything.

What 'your data' actually means inside a closed PIMS

Here is the reality behind the standard vendor language that says 'your data belongs to you.'

Your data is stored on the vendor's servers, in a format the vendor's system reads. You can see it through the vendor's interface. You can run reports through the vendor's reporting engine. You can request a data export, usually with advance notice, often in a format the vendor determines.

What you typically cannot do: query your own database directly, connect it to software the vendor has not approved, pull a live copy of your records without going through the vendor's export process, or leave without a migration procedure that the vendor controls.

The data is technically yours. The access is theirs.

This is not a minor distinction. It shapes every decision you make about your practice software for as long as you stay on that system, and it determines how costly it is to leave.

Three tactics that make data portability difficult

Closed PIMS vendors rarely say they will make it hard for you to leave. The difficulty is structural, built into how data is stored and exported. Here are the three most common mechanisms.

Export format restrictions

Most closed PIMS systems export data in PDF format, stripped CSV files, or proprietary formats that other systems cannot cleanly ingest. A PDF of your patient records is technically an export. It is not usable data. You cannot import a PDF into a new PIMS and have five years of patient histories transfer. You cannot run a query against it. You cannot connect an AI tool to it.

Format restrictions are not always intentional obstruction. Sometimes they reflect the technical constraints of older systems. But the effect on your practice is the same: you have received your data in a form that does not give you meaningful control over it.

A full, clean database export in a standard format like SQL or JSON (the kind of export that lets you actually do something with your records) is available from very few closed PIMS vendors, and often only at a cost.

Exit and migration fees

VetSoftwareHub has documented exit fees as high as $8,500 in veterinary PIMS contracts. These are not hypothetical worst-case scenarios. They are contract provisions that apply when a practice requests a full data export or migration support package upon leaving.

The economics are straightforward. If leaving your PIMS costs $8,500, some practices will decide the cost is not worth it and stay. The fee is not a service charge covering the actual cost of export preparation. It is a switching cost, structured to retain customers who might otherwise move to a competitor.

Open-source software does not have this fee structure because it has no financial incentive to make leaving expensive.

Delayed timelines

Some contracts require 30, 60, or 90 days advance notice before the vendor begins preparing a data export. A practice that decides to switch must then pay for two systems simultaneously during the transition period: their current PIMS plus the new one they are onboarding onto.

That double-billing period is not an accident. It adds real cost to switching and creates a window where a practice might reconsider.

What happens in practice when you try to leave

The format restrictions, exit fees, and delayed timelines compound. A practice going through a real migration from a closed PIMS often encounters this sequence:

• They decide to switch and request a data export.
• The vendor acknowledges the request and confirms it will take 30 to 60 days to prepare.
• The vendor provides a cost estimate for the migration package.
• The export arrives. The format is partially incompatible with the new system.
• The new PIMS vendor quotes an additional fee for manual data cleanup and re-import.
• The practice pays for both systems during the overlap period.

By the time the migration is complete, the practice has paid an exit fee, a manual migration charge, and several weeks of double subscriptions. The AVMA says this data belongs to the practice. The contract says the practice will pay to retrieve it.

None of this is illegal. It is standard industry practice. That is the problem.

Why this is getting more urgent: AI and your practice data

As AI tools enter veterinary medicine, the data ownership question stops being theoretical.

Every AI product that operates on clinical records (appointment reminders, diagnostic summaries, SOAP dictation review, overdue patient recall) needs access to your patient data to function. On a closed PIMS, connecting a third-party AI tool typically requires the vendor to approve the integration, charge an API access fee, or build a partnership arrangement. You do not control who connects to your data, or on what terms.

On a closed system, your patient records may also be used by the vendor to train models or improve their own AI products, subject to whatever your contract says about data use. The AVMA's principles state that prior consent is the foundation of proper data use. Whether your current contract actually requires that consent is worth checking.

Open-source software removes this gate entirely. If you control the infrastructure, you decide what connects to your data. An AI tool you trust can access your records directly. One you do not trust cannot. That decision belongs to you, not to a vendor.

What open-source changes

Open-source changes the ownership question structurally, not contractually.

If the source code is public and the schema is documented, there is no secret format your records are trapped in. If you self-host, your database is literally on your own server. There is no export request. There is no migration fee. There is no format negotiation. You already have your data in its complete, queryable form.

If you use managed hosting from an open-source provider, you still have direct access to your data. The provider runs the server, but the underlying code is public and the data is portable on request. An ethical managed hosting agreement for open-source software means you get a full database export at any time, in a standard format, at no charge.

The vendor structure changes because the financial incentive structure changes. A closed PIMS vendor benefits when you stay and benefits when leaving is costly. An open-source vendor benefits only when the software is actually good enough that you choose to keep using it or paying for managed hosting. The retention mechanism is value, not lock-in.

Questions to ask your current PIMS vendor (before you need to leave)

These questions are more useful before you sign or renew than after you have decided to move. Ask them in writing.

• What format will my data export be in? Will it be importable by any standard veterinary PIMS?
• What is the fee to request a full data export or migration support package?
• How many days of advance notice are required before export preparation begins?
• Who owns my practice's data if your company is acquired?
• Does my contract restrict connecting my records to third-party software or AI tools?
• What happens to my data if I stop paying or if your company shuts down?
• Does your company use my practice data to train models or improve your products?

If any answer is vague, requires a follow-up call, or is not written into the contract, that is relevant information. Vendors who respect the AVMA's principles answer these questions directly and in writing before you sign.

What OpenVPM's data structure looks like

OpenVPM is AGPLv3-licensed, API-first veterinary practice management software. The schema is public at github.com/evangauer/openvpm. You can read exactly what fields exist, how records are structured, and how they relate to each other before you write a line of data into the system.

If you self-host, your database runs on your own server. There is no export request process. You already have your data.

If you use managed hosting, the underlying code is still public. You can request a full database export at any time. The goal is a complete, standard-format backup that you can take anywhere, because that is what 'your data belongs to you' actually means in practice.

There are no exit fees because there is no exit process.

Try it with your own eyes

The demo is live at demo.openvpm.com, preloaded with sample patient records, appointments, and invoices. You can navigate the full interface in your browser without an account.

If you want to see the schema or the API documentation rather than the interface, the repository is at github.com/evangauer/openvpm.

For managed hosting availability, join the waitlist at openvpm.com.

The AVMA published a principle: your practice owns its data. OpenVPM is built so that principle is actually true: not as a marketing claim, but as a structural fact about where your records live and who controls them.