Most practices stay on software they've outgrown for one reason: fear of the migration. Losing records, a week of chaos at the front desk, reminders going to the wrong people, staff who refuse to learn something new. Those risks are real, but almost all of them come from skipping the planning, not from the switch itself. This guide walks through a veterinary PIMS migration from start to finish: deciding what to move, getting it out of your old system, cleaning and mapping it, testing, training, going live, and the first two weeks after.
Quick answer
A veterinary PIMS migration has three parts: getting your data out of the old system, cleaning and importing it into the new one, and training the team. How long: a small clinic doing its own CSV import can go live in about 3–4 weeks; vendor-run migrations are slower, and vendors that publish a figure quote roughly 8–12 weeks. How much: the vendor's migration fee ranges from $0 (self-service import) to a published $2,475 at one vendor, and many do not publish it. Add one or two months of paying for both systems and the staff hours spent cleaning data and training, which is usually the largest cost. The switch itself takes one day.
In this guide
- Signs it's time to switch
- Step 1: Decide what needs to move
- Step 2: Get your data out of the old system
- Step 3: Clean the data before you import it
- Step 4: Map your fields
- Step 5: Import in the right order, then verify
- Step 6: Train everyone, then go live
- How long does it take to switch to a new PIMS?
- How much does it cost to migrate from one PIMS to another?
- Will patient history migrate correctly?
- Go-live checklist
- Common migration mistakes (and how to avoid them)
- Migrating from AVImark, Cornerstone or another installed system
- How migration works with VetSyCare
- Frequently asked questions
The short version
- Decide what data must move on day one, what can follow, and what stays archived.
- Export everything from your old system, and keep a full copy somewhere safe.
- Clean it: merge duplicates, mark deceased patients, fix contact details.
- Map your old fields to the new system's import format, and do a test import.
- Spot-check real records, train every staff member, then switch on a quiet day.
- Keep read-only access to the old system until you're sure nothing is missing.
Signs it's time to switch
Nobody migrates for fun. These are the reasons practices tell us they finally made the move:
The server is a liability
An ageing machine in a back room holds every record you have. Backups are "someone's job", and an IT call costs more every year.
You pay per seat
Adding a part-time tech or relief vet means another license, so people share logins, which is a security and records problem.
Clients expect more
Online booking or appointment requests, a client portal and automatic reminders are standard now. Bolting them on separately adds cost and double entry.
Notes eat evenings
Slow SOAP entry means vets finishing records at home. Modern systems with templates and dictation give those hours back.
You can't work remotely
If you can't check a record from home, a satellite location or a house call, the software is holding the practice back.
Updates mean downtime
Installed systems need upgrades scheduled around clinic hours. Cloud systems update themselves.
Step 1: Decide what needs to move
Not everything has to migrate in full detail on day one. Sort your data into three groups:
| Priority | Data | Why |
|---|---|---|
| Day one | Active clients and patients, vaccination history, allergies and alerts, current medications and prescriptions, upcoming appointments, outstanding balances | You need these to see patients safely, send reminders and get paid from the first morning. |
| Soon after | Medical record history, SOAP notes, lab results, services and price list, inventory, staff accounts | Important for continuity of care and billing, but can follow in the days after go-live. |
| Archive | Old invoices and payments, very old records, inactive clients, deceased patients | Keep a complete export and read-only access for legal and records-retention purposes. |
Check your state, province or country's medical-records retention rules before deciding what to archive. Archived never means deleted. Keep the full export, and keep it backed up.
Step 2: Get your data out of the old system
There are three common routes, and many practices use more than one:
Built-in reports & exports
Most systems can export client and patient lists, vaccine history and appointments to CSV or Excel. Run them one data type at a time.
Vendor data export
Ask your current vendor for a full export. Some charge for it, and some are slow, so ask on day one. Read your contract: you should own your data.
Database backup
Older server-based systems keep data in a local database. An IT professional, or your new vendor, can sometimes extract from a backup.
Don't cancel your old subscription or license until the export is complete and checked. Losing access halfway through a migration is the most common way practices lose records. Plan for at least one overlap month.
Step 3: Clean the data before you import it
Moving messy data just moves the mess to a new address. An hour of cleaning here saves weeks of confusion later:
- Merge duplicate clients. The same person entered twice with different phone numbers is common after years of use.
- Mark deceased patients. A vaccine reminder for a pet that died last month is one of the most upsetting mistakes a practice can make, and it's entirely preventable.
- Fix email addresses and mobile numbers. Reminders, the client portal and receipts all depend on them.
- Standardise species, breed and sex. "Canine", "Dog" and "K9" should become one value. Same for "MN", "Male neutered" and "Neutered male".
- Review your services and price list. A migration is the perfect moment to retire codes nobody uses and fix prices that drifted.
- Decide on inactive clients. Clients with no visit in several years can usually be archived rather than imported as active.
Step 4: Map your fields
Every system names things differently. Mapping means deciding which column in your export goes into which field in the new system. Do it once, write it down, and reuse it for the final import.
| Old system might call it… | New system field | Watch out for |
|---|---|---|
| Client ID / Account # | Client code | Keep the old number so staff can still look people up by it. |
| Owner email | Client email | Often used to link patients to clients during import, so it must be correct. |
| Animal / Pet name | Patient name | Multiple pets with the same name in one household. |
| Birth date / Age | Date of birth | Ages stored as text ("3 yrs") need converting to an estimated date. |
| Rabies tag / Vaccine | Vaccination record | Keep administration date, due date, lot number and manufacturer together. |
| Balance | Outstanding invoice | Bring over open balances as single opening items, not years of history. |
Step 5: Import in the right order, then verify
Later data depends on earlier data, so the order matters:
- Clients. Everything else hangs off them.
- Patients, linked to their clients.
- Vaccinations, allergies and medical history, linked to patients.
- Prescriptions and lab results.
- Upcoming appointments.
- Opening balances and open invoices.
Then verify, and don't skip this:
- Compare counts. Number of active clients and patients, old vs. new.
- Spot-check 20–30 patients you know well. Vaccines, allergies, current meds and last visit.
- Check upcoming appointments landed on the right day and time. Time zones and daylight saving catch people out.
- Check balances to the cent on a handful of accounts.
- Send yourself a test reminder to confirm the wording and that it goes to the right person.
Step 6: Train everyone, then go live
Pick a quieter day to switch, such as a mid-week afternoon. Not a Monday morning, and not peak vaccine season or the week before a holiday. A typical plan for a small practice:
| When | What happens |
|---|---|
| 3–4 weeks before | Request the vendor export. Choose the go-live date. Tell the team why you're switching and what will be better for them. |
| 2–3 weeks before | Export and clean data. Set up clinic details, staff accounts, services, templates and reminder wording in the new system. |
| 1–2 weeks before | Test import. Every staff member practises their real tasks: check-in, SOAP note, prescription, invoice, payment, reminder. |
| Go-live day | Final export of anything that changed since the test, final import, quick spot-check, switch. Old system goes read-only. |
| First 2 weeks | A 10-minute daily huddle on what's confusing. Fix templates and settings as you go. Keep a shared list of questions. |
| After 30–90 days | Confirm nothing is missing, then cancel the old system, keeping the final full export archived. |
Training that actually sticks
- Train by task, not by menu. "How I check in a new client" beats a tour of every screen.
- Everyone practises, not just one "super user". The person who checks in patients at 7:45 am needs to have done it before.
- Write a one-page cheat sheet for the five things each role does most.
- Name a go-to person for questions during the first two weeks.
How long does it take to switch to a new PIMS?
The honest answer is a range, because the timeline depends far more on who does the conversion and how clean your data is than on the size of the clinic. These are the figures vendors publish themselves, read on their own pages on 14 November 2026:
| Source | What it says about timing |
|---|---|
| Provet Cloud (provet.com/pricing) | "Most practices are fully up and running within 8 to 12 weeks"; its in-house team always runs a test migration first. |
| Shepherd (shepherd.vet/pricing) | Existing single-location practices start paying 12 weeks after onboarding begins, even if they go live sooner, which tells you the onboarding window it plans around. |
| Digitail (help.digitail.io, migration article) | Four stages: first migration into a test environment, data validation that must be finished "at least 4 weeks before go-live", final migration from a fresh backup, then go-live. |
| VetSyCare (ours) | No conversion service to wait for: you run the CSV import yourself, so the pace is set by how quickly you can export and clean your data. A small clinic can do it in 3–4 weeks. |
Use those to place yourself in one of three bands:
3–4 weeks
One location, one to three vets, data that exports to CSV, self-service import. Most of the time goes on cleaning and training, as in the plan in Step 6.
8–12 weeks
The vendor converts a database backup for you. You wait for a slot, review a test migration, give feedback, and the final conversion runs just before go-live.
3–6 months
Several locations, several source systems, heavy lab or payment integrations, or years of duplicate records to untangle first. Plan one site at a time.
Whatever the band, the cut-over is short: the old system goes read-only at close of business, the final import runs, and you open on the new system the next working day. The weeks before are preparation; the two weeks after are when the team needs the most support.
How much does it cost to migrate from one PIMS to another?
There is no single market price, and we will not invent an average. What you can do is list every line that will appear and get each one in writing. Vendor figures below are from each vendor's own page on 14 November 2026.
| Cost line | What is published | What to ask |
|---|---|---|
| New vendor's migration fee | Shepherd: $2,475 one-time, or $230/month for 12 months ($2,760); +$500 per additional server for groups. Provet Cloud: in-house migration listed on every plan, no separate price shown. VetSyCare: $0, self-service CSV import. Most other vendors do not publish a fee. | Exactly which records are converted (history, attachments, balances, reminders), how many test runs are included, and what a re-run costs. |
| Onboarding or setup fee | Shepherd: none. Provet and VetSyCare: none listed. Others: ask. | Whether training hours are capped and what extra sessions cost. |
| Old vendor's export fee | Rarely published. | Read your contract for data-export terms, then ask for the fee and the format in writing before you give notice. |
| Overlap subscription | Your current monthly bill. | Budget one to three months of paying for both systems, and check your notice period. |
| Staff time | Your own payroll. | Hours for cleaning data, building templates and price lists, and training, multiplied by loaded hourly cost. |
| IT help | Your IT provider's rate. | Needed mostly when the old system is a server database that has to be backed up or extracted. |
| Re-connecting other tools | Varies. | Labs, payment terminals, texting, online booking and accounting links may need new setup or a new contract. |
| Go-live slowdown | Your own schedule. | Many clinics book lighter for the first few days. Decide in advance how much. |
Migration cost worksheet (copy and fill in)
ONE-TIME COSTS
New vendor migration / conversion fee $ ______
New vendor onboarding or training fee $ ______
Old vendor export fee $ ______
IT provider: ____ hours x $ ____ $ ______
Hardware (tablets, label printer, card reader) $ ______
Staff time, cleaning data: ____ h x $ ____ $ ______
Staff time, setup (fees, templates): ____ h x $ ____ $ ______
Staff time, training: ____ people x ____ h x $ ____ $ ______
Lighter schedule at go-live: ____ slots x $ ____ $ ______
ONE-TIME TOTAL $ ______
OVERLAP
Old system: $ ____ / month x ____ months $ ______
ONGOING DIFFERENCE
New system monthly cost (all seats and add-ons) $ ______
Old system monthly cost (software + server + IT) $ ______
Monthly saving or extra cost $ ______
Months to recover the one-time total = one-time total / monthly saving
If the last line comes out at more than about three years, or the new system costs more each month, the case for switching has to rest on something other than money: the server, remote access, missing features. That is a legitimate reason; it just should be a deliberate one. Our staying vs switching worksheet covers the "old system" side in more detail, and the veterinary software cost calculator works out the new monthly cost for per-vet and flat pricing.
Hidden costs in switching vet software
- The second conversion. A test migration finds mapping problems; fixing them and running it again may be billed separately. Ask how many runs are included.
- Data that does not convert. Attachments, scanned documents, images, open estimates and client balances are the usual gaps. Whatever stays behind means keeping read-only access to the old system, sometimes for a fee.
- Auto-renewal on the old contract. A missed notice date can add a full year of fees. Our guide to veterinary software contracts shows where to find it.
- Per-seat pricing on the new system. Training everyone properly means giving everyone a login, which costs more where each login is billed.
- Add-ons you had bundled before. Texting, online booking, AI notes and payment processing are separate lines with some vendors.
- Client messages sent twice. If reminders run from both systems during overlap, you pay for both and annoy clients. Keep reminders off in the new system until cut-over.
Will patient history migrate correctly?
It will if you check it, and it may not if you only compare record counts. Structured data such as clients, patients, vaccine dates and appointments usually converts cleanly. Free-text history, attachments and money are where errors hide. Before go-live, open the same 20–30 patients in both systems and compare these fields side by side:
SPOT-CHECK SHEET (one row per patient; choose long-history and multi-pet clients) [ ] Client name, phone, email match; pets attached to the right owner [ ] Species, breed, sex, date of birth, microchip [ ] Deceased / inactive status carried over [ ] Allergies and alerts visible where staff will see them [ ] Last 3 visits: dates, notes readable, in the right order [ ] Every vaccine: date given, due date, lot number [ ] Current medications and open refills [ ] Latest weight [ ] Lab results or attachments present (or location in archive noted) [ ] Future appointments: right day, time, provider [ ] Open balance matches to the cent [ ] Reminder due dates present, and reminders still switched OFF Checked by: ______ Date: ______ Problems logged: ______
Go-live checklist
THE WEEK BEFORE [ ] Full export or backup of the old system saved in two places [ ] Test import done and spot-check sheet signed off [ ] Every staff member has a login and the right permissions [ ] Services, prices, tax rate and invoice layout checked [ ] SOAP templates, consent forms and reminder wording set up [ ] Printers and label printer tested from the new system [ ] Each role has practised its five most common tasks [ ] Clients told if reminders or invoices will look different [ ] Backup internet (hotspot) tested GO-LIVE DAY [ ] Old system set to read-only at close of business [ ] Final export of everything changed since the test import [ ] Final import; counts compared; 10 patients spot-checked [ ] Tomorrow's appointments visible on the new calendar [ ] Test invoice and payment recorded, then voided [ ] One test reminder sent to a staff email address [ ] Reminders switched on in the new system, off in the old one FIRST TWO WEEKS [ ] 10-minute daily huddle; one shared list of problems [ ] One named person fixes templates and settings each day [ ] Lookups in the old system logged (what was missing?) [ ] Day 14: open balances and reminders reconciled AFTER 30-90 DAYS [ ] Nothing still needed from the old system day to day [ ] Final archive export stored and backed up [ ] Old subscription cancelled in writing; old server wiped or stored securely
Common migration mistakes (and how to avoid them)
Cancelling too early
Keep read-only access to the old system until you're certain nothing is missing.
Skipping the spot-check
Record counts can match while vaccine dates are wrong. Check real patients.
Importing the mess
Duplicates and deceased patients cause embarrassing reminders. Clean first.
Bad timing
Busy season, holidays and staff vacations make a migration much harder than it needs to be.
Running two systems for weeks
Double entry causes errors. Switch on a set day and keep the old one read-only.
Not telling clients
If reminders or receipts will look different or come from a new address, let clients know.
Migrating from AVImark, Cornerstone or another installed system
Older installed (server-based) systems are the most common starting point for a migration. They usually hold years of history in a local database, and exports can be less straightforward than with cloud tools. A practical approach:
- Run every built-in report you can (clients, patients, vaccines, appointments) and save them as CSV.
- Ask the vendor or your IT provider about a full database export, and how long it takes.
- Move the "day one" data first, archive the rest, and keep the old system available read-only for history lookups.
If you're still deciding whether to move to the cloud at all, read our comparison of server-based vs. cloud PIMS and our AVImark alternatives guide. If you have already decided to leave Cornerstone, Cornerstone alternatives compares eight cloud systems with the prices that are published.
How migration works with VetSyCare
VetSyCare includes a built-in CSV data migration tool with a ready-made template for each data type: clients, patients, medical records, SOAP notes, vaccinations, lab results, prescriptions, appointments, invoices, payments, inventory, services and staff. Download a template, paste in your exported data, upload it, and review the import results. Errors are listed so you can fix them and re-import.
What that means in practice: the import is self-service and works from CSV files, so it suits a clinic whose current system can export lists and history to CSV or Excel. We do not convert a raw database backup for you, attachments and scanned files do not come across through the CSV templates, and there are no lab, imaging or payment-terminal integrations to reconnect. If your history lives in a server database that only the old vendor can open, get their export in CSV first, or choose a vendor that runs the conversion for you.
Because VetSyCare's plan includes 3 veterinarian and 7 staff logins (extra seats are $49/month per vet and $15/month per staff user), most small practices can set up every team member on day one at no extra cost, which makes proper training much easier. See pricing, or read how to choose veterinary practice management software and what veterinary software costs.
Frequently asked questions
How long does a veterinary software migration take?
For a small practice with reasonably clean data doing its own import, plan on three to four weeks from requesting the export to go-live, most of it preparation and training. Where the new vendor converts your database for you, expect longer: Provet, for example, says most practices are up and running within 8 to 12 weeks (provet.com/pricing, 14 November 2026). The switch itself takes a day. Multi-location practices and very messy data take longer.
Will I lose my medical records when I switch?
Not if you keep a complete export and read-only access to the old system. Import what you need day to day, and archive the rest so it's still available for records requests.
Can I migrate from AVImark or Cornerstone?
Yes. Export client, patient and history data from the old system (or ask the vendor for a full export), map it to the new system's import format, and import it in order. Older installed systems sometimes need help from IT or the vendor to get a complete export.
Should I run both systems at the same time?
Only briefly. Running two live systems for weeks means double entry and mistakes. Switch on a set day and keep the old one read-only for lookups.
What does a migration cost?
It depends on the vendors on both sides. Published examples on 14 November 2026: Shepherd charges $2,475 one-time for data migration, Provet Cloud lists in-house migration on every plan without a separate price, and VetSyCare's CSV import is self-service at no charge. Many vendors do not publish a fee, and some old vendors charge for the export. Ask both your old and new vendor up front, and budget for the overlap months and for staff time spent on cleaning and training, which is usually the biggest cost.
What's the best time of year to switch?
Your quietest few weeks. For many small-animal practices that's outside peak vaccine season and away from major holidays. Ask your team when they'd least mind learning something new.
Planning a switch?
Tell us which system you use today and we'll tell you plainly what the CSV import can bring across and what it cannot. Or try the import yourself with a few records during the 7-day free trial.
Start a 7-day free trialNo credit card needed. Questions first? Talk to us about migrating.