Cornerstone Alternatives: A Practical Guide for Hospitals Ready to Move (or Not)

Disclosure up front: we build OpenVPM, one of the options below. It appears last and clearly labeled. Product and API claims use vendor-owned sources; numeric prices appear only when a vendor currently publishes them.

Cornerstone is not a bad system. It is one of the most established products in veterinary software, with clinical depth built over decades and deep integration with IDEXX labs and imaging. Hospitals that run it tend to have staff whose muscle memory in Cornerstone is itself a real asset. Nobody leaves Cornerstone lightly.

But there are moments that force the question, and if you found this page you are probably in one of them:

• The server is due. Cornerstone has traditionally lived on your own hardware, and the refresh quote arrived at the same time as the cloud pitch.
• The cost is not independently checkable before sales. IDEXX does not publish a current Cornerstone rate card, so the complete software, hosting, implementation, support, integration, upgrade, and export terms need to be requested in writing.
• Training new staff on a system this deep takes real time, and turnover has made that expensive.
• IDEXX itself is steering the ecosystem toward cloud, and you would rather choose your next platform than default into it.

First decision: stay in the IDEXX family or leave it

This is the fork most Cornerstone hospitals face first, and it is worth making consciously. ezyVet and IDEXX Neo are both IDEXX-owned, so moving to either keeps your diagnostics integration seamless and keeps your software and your lab vendor under one roof. That is genuinely convenient, and it is also the same concentration of dependence you have today. Leaving the family gets you negotiating leverage and independence, at the cost of a lab integration that is merely good instead of native.

ezyVet: the in-family upgrade

For larger and specialty hospitals, ezyVet is the natural IDEXX-family landing spot: cloud-native, capable, and supported by documented REST API paths. ezyVet does not publish a current rate card, so model the written quote against your actual locations, roles, modules, implementation, integrations, and export requirements.

IDEXX Neo: the in-family simplification

If your Cornerstone deployment always used a fraction of what the system could do, Neo is IDEXX's simpler cloud option for smaller practices. IDEXX does not publish a current Neo rate card in the reviewed material. A large hospital may find the scope too narrow; a modest practice that inherited Cornerstone may find it a better fit.

Provet Cloud: the multi-site independent

Outside the family, Provet Cloud is a strong fit for multi-site and referral operations: mature, European-built, with a documented API and webhooks. Its official US pricing page publishes current platform and per-veterinarian rates for Core and Pro plans, while Enterprise and optional AI agents require a quote.

Shepherd: the fresh start

If the appetite is for a SOAP-centered cloud workflow rather than enterprise depth, Shepherd belongs on the list for small and mid-size general practices. Its current feature material markets unlimited users, training, and veterinary-experienced support, but not a numeric rate card; confirm the complete quote in writing.

OpenVPM: keep the control, modernize the stack (that is us)

Here is the part of the Cornerstone story the cloud pitches skip: some hospitals like running their own systems. Your data in the building, your uptime in your hands, no monthly meter. If that is you, the modern version of that model is not another aging on-premise product. It is open source.

OpenVPM is AGPLv3-licensed and has no software license fee when self-hosted on your own hardware or private cloud. It provides a modern web interface, a targeted REST API for selected workflows, signed webhooks, an optional configured AI agent, and a public database schema. Managed OpenVPM Cloud is $79 per month per location with unlimited staff. OpenVPM does not currently replace Cornerstone's external diagnostics ecosystem or specialty depth, and specialty or multi-site hospitals should not plan a production cutover. The present rollout scope is controlled, connected single-location companion-animal or house-call pilots.

Side by side

The migration questions that matter for a Cornerstone-sized record set

• What exactly converts? Decades of Cornerstone history includes attachments, imaging links, and reminders. Get the conversion scope in writing, item by item.
• What does the export cost, and who runs it? Third-party conversions of proprietary databases are a known cost center. Ask for the number before you sign anything.
• How long do the two systems overlap, and what do you pay during the overlap?
• What happens to the old server and its data after cutover? Retention rules for medical records still apply to the system you left.

Whichever way you go, decide on your own clock rather than the server refresh clock. The worst PIMS decisions are the ones made in the week the old hardware died.