TutelaNobody switches shelter software for fun. You switch because the old system goes down on adoption-event Saturday, because support stopped answering, or because the bill quietly doubled. And then you stay stuck for another year, because the thought of re-typing four thousand records is worse than any outage.
Here's the honest truth: a migration is a weekend project, not a rewrite of your shelter's history — if you do it in the right order.
Step 1: Export everything, even the mess
Every system has some export path, even the ones that make it hard. Look for anything labeled export, reports, or backup, and grab CSVs (or Excel files) of animals, people, adoptions, medical records, and photos if you can get them. Don't clean anything yet — mess is fine, missing is not.
- Animals — names, species, breeds, statuses, intake dates, microchips
- People — adopters, fosters, donors, volunteers, with emails and phones
- Adoptions — which person took which animal home, and when
- Medical — vaccines, procedures, due dates (grab everything; dates matter)
- Photos — even a folder of files named after animal IDs is workable
Step 2: Protect the relationships
The single most common migration disaster isn't lost rows — it's lost connections. The animals arrive, the people arrive, but nobody remembers that Biscuit went home with the Nguyens in 2023, or that Willow and Pepper are a bonded pair who must be adopted together. Spreadsheets survive; relationships die.
Before importing anywhere, check your exports for linking columns: adopter IDs on adoption rows, animal IDs on medical rows, anything that says 'bonded' or references another animal. If your new system's importer doesn't understand those links, you'll be rebuilding them by hand for months. (This is exactly why we built the free importer to preserve every relationship — adopter histories, medical timelines, and bonded pairs included — from any CSV or Excel export, no account required.)
Step 3: Do a trial import and read the flags
A good importer tells you what it couldn't understand instead of silently dropping it. Run a trial, then read the exceptions report like a vet reads bloodwork: 40 rows flagged out of 4,000 is a great result — fix the 40, not the 4,000.
Step 4: Run both systems for one week
Keep the old system read-only (stop entering new data there — one team, one source of truth) and do your real daily work in the new one. A week is enough to surface anything the trial missed while the old data is still reachable for spot checks.
Step 5: The switch-off checklist
- Final incremental export of anything added since your first export
- Confirm record counts match: animals, people, adoptions
- Spot-check five animals end-to-end: photos, medical, adopter history
- Update your website links, Petfinder feed, and QR codes
- Download one last full backup of the old system, then cancel
That's it. The shelters that get stuck are the ones who treat migration as one giant terrifying day. Treated as five small steps, it's a quiet week — and on the other side, software that doesn't fight you.