I wrote the standard for making websites AI-operable. Learn More
Migration · Cornerstone to ezyVet
Cornerstone practices tend to have deep, well-kept medical records and a decade of in-house lab history attached to them. That is exactly what makes the move valuable and exactly what makes it frightening — the record is genuinely good, so losing part of it is a genuine loss.
The reminder schedule is the sleeper risk, the same as any veterinary migration. Financial errors get noticed because someone checks. A broken vaccine reminder schedule fails quietly for months, and by then you've missed a season of recalls.
Cornerstone is an on-premise system, which means the data is physically yours and sitting on your server — nobody can switch it off partway through. Extraction runs against that store directly, supplemented by report exports for anything the tables don't express cleanly. ezyVet is cloud-hosted with a documented API, so the load side is well defined. The concentration of work is in the middle: deciding what each Cornerstone field actually meant after years of practice-specific use, and preserving the linkage between lab results and the visits they belong to.
Each of these gets its own record count in the assessment and its own line in the reconciliation report. Depth of history is a scope decision made with real numbers in front of you, not an assumption baked into a quote.
Clients and patients
Client records with contact details and linked patients — species, breed, sex, date of birth, microchip — plus the multi-pet relationships that determine how reminders and invoices group.
Medical history and exam records
Visit history, exam notes, diagnoses, and treatment records carried against the right patient, date, and attending veterinarian.
Vaccination history and reminders
Administered vaccines with dates, products, and lot numbers where recorded, plus the forward reminder schedule — validated as its own step, because this is what silently breaks.
Lab results
In-house and reference lab results carried as records and relinked to the visits they belong to. On this pair that linkage is the crux, not an afterthought.
Prescriptions and medication history
Dispensed medications, dosages, and refill history, with controlled-substance records handled to their own standard.
Client ledgers and balances
Invoices, payments, credits, and open balances reconciled against a Cornerstone-side control report before load.
Invoice items, services, and inventory
Item and service codes mapped to ezyVet's product structure, with a usage report in hand so retiring the codes nobody has touched in years is a decision rather than an accident.
Documents and imaging attachments
Consent forms, referral letters, scanned documents, and imaging attachments remapped to the correct patient.
Written down before you spend anything, because the alternative is finding out in week six. This list is specific to Cornerstone to ezyVet; the assessment turns it into your list, with record counts attached.
— The live connection to your in-house lab analysers. Historical results migrate; the integration itself is re-established on the ezyVet side. That has its own lead time and it belongs in the plan up front, because a practice that discovers it on cutover weekend runs manual for a fortnight.
— Cornerstone's screen layouts, travel sheets, and practice-specific entry templates. Content moves; the interface is rebuilt, and that is separately scoped.
— Free-text notes recover as text, not as ezyVet's structured clinical fields. Where Cornerstone held something as a note that ezyVet expects as data, it lands as a note. The assessment tells you how much of your history is in that category.
— Whiteboard and in-hospital treatment-sheet state. It is operational rather than record data, it changes hourly, and it is not portable. Cutover is scheduled so the hospital is as close to empty as it gets.
— Cornerstone internal record IDs. ezyVet issues its own, and anything keyed externally needs the mapping table I produce and hand to you.
None of this is in either vendor's documentation. It is the category of thing that looks fine in a test load and produces a wrong number in month two, which is why the process puts a full sandbox load and a reconciliation you sign in front of any production cutover.
01
The results themselves migrate readily. What breaks is the association between a result and the consultation it was ordered during. A migration that preserves every lab value but loses which visit each belonged to has technically kept your data and functionally ruined your medical record. Linkage is validated as a named step with its own sign-off.
02
Some due dates are stored values; some are derived from last administration plus a protocol interval. Long-running practices routinely have both in the same database. Migrating one as the other yields a reminder schedule that looks right and is wrong, so the reminder set gets its own date-range spot check that you run yourself.
03
Flagging conventions vary by practice. Get it wrong and you either send reminders for deceased patients — the worst email your practice can send — or lose access to history you are obliged to retain. Flag mapping is signed off before the load.
04
These carry retention obligations independent of the migration and are handled and documented explicitly, rather than swept along with general prescription history.
01 — 02
A read-only audit of your Cornerstone instance produces record counts, a risk register, and a fixed quote. Then a field-by-field mapping document you sign before any code runs.
03 — 04
The complete migration runs into a ezyVet sandbox — not a sample. You spot-check records you choose, and sign a written reconciliation. If the counts don't tie, we don't cut over.
05 — 06
Scheduled around your calendar with the rollback plan written in advance, followed by 30 days of included corrections for the things that only surface in real use.
A single-location practice usually lands in Standard Migration. Multi-location groups, practices running several Cornerstone installations, or anything with a large in-house lab archive to relink generally land in Complex. The assessment is what makes a fixed migration price possible, and its fee is credited toward the migration if you proceed.
Tier
Scope
Price
Migration Assessment
A read-only audit of your source system.
$1,500 – $2,500
Standard Migration
One source system to one destination.
$6,500 – $15,000
Complex / Multi-Entity Migration
Multiple locations, systems, or long history.
$18,000 – $40,000
Historical results migrate as part of the medical record. The live analyser connection is re-established on the ezyVet side as a new integration, with its own lead time, and it is sequenced into the plan before cutover rather than after. Practices that leave it to the last minute run results manually for a couple of weeks.
It is usually an advantage. On-premise means the data is physically in your possession and cannot be switched off mid-migration. The first step of the assessment is taking a full copy of that server's data so all subsequent work happens against a snapshot, never against your live system.
All of the medical history — it is the clinical record and there are retention obligations attached. Financial transaction depth is a real cost tradeoff, and most practices carry two to three years plus current balances. The assessment gives you record counts so it's a decision made against numbers.
Around your closed hours, and with the hospital as close to empty as it gets — in-patient treatment state is the one thing that genuinely cannot migrate. Nothing touches production until the sandbox load is validated and you have signed the reconciliation report.
The assessment is the read-only audit — what data exists, what is extractable, what will be lost, and a fixed-price quote for the migration itself. It is priced at $1,500 – $2,500 depending on scope, fixed before anything starts, and the report is yours whether or not you go further.
Tell me what you're moving. I read every one of these personally and reply within one business day, usually with a couple of specific questions about your source system — the answers change the price, so it's worth asking early.
Nothing is committed by this form. No payment, no contract, no scheduling sequence. It starts a conversation.
If your destination vendor can handle it, I'll say so. Some conversions genuinely don't need an independent migration.
Standard – Complex
Vaccine reminders fail silently.
Every pair
Twenty-odd pairs are written up across seven industries — and the written ones are not the limit of the work. Search the full list, or just ask.
Cornerstone and ezyVet are trademarks of their respective owners. This page describes independent data migration work involving those systems and does not imply any affiliation with, partnership with, or endorsement by either vendor.
Before you give notice on Cornerstone
The most expensive mistake in this category is losing source-system access before the extraction is done. The assessment is read-only, fixed-price, and yours to keep either way.
I respond personally within 1 business day. No pitch — just a real conversation.