Multi-location readiness is still to be proven.
OpenVPM has a per-location commercial model and a public schema, but it is not currently a production-ready multi-site platform. Group reporting, cross-location permissions, shared records, and coordinated rollout require fit review and further product work.
What must be validated for multi-location groups.
These pages describe the needs we are evaluating. They are not a claim that OpenVPM is ready for production use in this setting.
Per-user pricing punishes growth
Cloud pricing is per active location with unlimited staff, but pricing does not imply that multi-location operations are production-ready.
Reporting across locations is a nightmare
Current reports are practice-scoped. Validated group rollups and cross-location analytics are not supported today.
Acquisitions mean data lock-in
The schema is public, but acquired-practice migrations still require export review, field mapping, dry runs, and assisted handling of unsupported record types.
Relevant building blocks to inspect.
These product areas exist, but together they do not yet make this practice type production-ready.
Reports & Analytics
Revenue, appointments, services, and inventory exports.
See how it worksSmart Scheduling
Day and week views, one column per doctor.
See how it worksBilling & Invoicing
Itemized estimates, invoices, balances, and payments.
See how it worksOperational Controls
Controlled-drug ledger, audit records, and clinic roles.
See how it worksClient Communications
History, portal, email, and activated SMS workflows.
See how it worksCommon questions
Does OpenVPM scale across multiple locations?
Multi-location operations are not production-ready today. Group reporting, cross-location permissions, shared records, and coordinated multi-site rollout still require product work and validation.
How is pricing structured for groups?
Managed Cloud pricing is per active location with unlimited staff, but that commercial model is not a claim that multi-location workflows are ready for production.
What happens to acquired practices' data?
Each source export must be reviewed and mapped. The self-service dry-run path covers clients, patients, vaccination history, and visit notes; appointments, invoices, attachments, and vendor-specific history require assisted scoping. There is no general live-sync connector.
Related reading
The Best Veterinary Practice Management Software in 2026 (11 Platforms, Compared Honestly)
Eleven veterinary PIMS platforms compared honestly by a vendor that is one of them: publicly reported pricing, data ownership, API openness, and who each one actually fits.
Read moreWho Owns Your Veterinary Practice's Data? (And What Happens When You Try to Leave)
The AVMA says your practice owns its data. Most PIMS contracts don't agree. A plain-language guide to exit fees, portability traps, and what open-source changes.
Read moreWhy veterinary software should be open
Every other part of the clinic is built on standards. The software that runs it shouldn't be a locked box you rent forever.
Read moreInspect the product without assuming production fit.
The demo shows existing building blocks. This practice type is not production-ready, and live records should not be entered without a separately approved fit review.