Switching from Shelterluv · PetPoint · spreadsheets

Bring the animals. Bring the history. Leave the lock-in.

The scariest part of switching shelter software is losing records and Shelter Animals Count continuity. Migration is treated as a product workflow, previewed before anything commits.

Plan my migration

How it works

Four passes, one guided migration.

Export from the current system. goodDingo maps the incoming formats, previews every pass, and keeps batches reversible while the records are being verified.

Animals

Names, species, breeds, identifiers, locations, and statuses—with existing animal codes preserved.

People

Adopters, fosters, donors, and volunteers, including the relationships that connect them to animals.

Medical history

Vaccinations and treatments matched to each animal by stable identifiers and reviewed exceptions.

Historical outcomes

Past adoptions, transfers, and returns mapped to Shelter Animals Count categories.

Shelter staff planning a careful records migration together
Illustrative records-migration planning scene.
The other direction

And if you ever leave?

One click in Settings downloads the records you own—animals, people, adoptions, medical, outcomes, and donations—as plain CSV files in a ZIP. No export fee, support ticket, or exit interview.

Export everything (.zip) → plain-CSV files → openable by standard tools, without a proprietary reader.
Before you commit

Ask the awkward migration questions.

Source inventory

We start with the systems, exports, record counts, and identifiers that need to move.

Dry-run preview

Review mapped samples and count totals before any migration batch is accepted.

Exception report

Unsupported, missing, or ambiguous fields are named for review instead of silently dropped.

Acceptance checklist

Your team agrees on samples, totals, access, and sign-off criteria before the move is complete.

Data access, retention, and deletion expectations are reviewed during onboarding. See the published security and data practices.

Tell us what you run today.

Share the current system and rough record counts. We’ll outline the migration before you commit to anything.

Plan my migration