From spreadsheet to system: a foster coordinator's migration playbook
The two-week plan to move your rescue off Google Sheets and group chats, without losing a single dog's history or making your fosters revolt.

Your coordinator is the most important person at your rescue. They're also, statistically, the most likely to quit this year. Here's the migration playbook that gets them out of a 4,000-row spreadsheet and a group chat with 212 unread messages, without losing a single dog's history along the way.
Almost every dog rescue under 200 dogs/year runs on the same stack: one shared Google Sheet, one WhatsApp or Facebook Messenger group, and a coordinator who keeps the whole thing alive through sheer memory and caffeine. It works until it doesn't. The coordinator burns out, takes a vacation, or leaves for a paid job, and suddenly nobody knows which fosters have a senior-friendly home, which dogs are overdue for vaccines, or who promised to drive Buddy to his neuter appointment on Saturday.
Migrating off that setup feels scary because the spreadsheet is the institutional knowledge. Lose it and you lose the rescue. So most coordinators don't migrate. They just keep adding columns.
This playbook is the one we wish every coordinator had when they made the jump. It assumes you have a working spreadsheet today and want to be fully running on a real system within two weeks, without making your fosters revolt or your director nervous.
Week one: audit, don't migrate
Do not start by importing anything. Start by deciding what's actually worth bringing.
Open your spreadsheet. You almost certainly have columns that look something like this:
- Dog name, breed, age, intake date
- Current foster (often a name with no contact info)
- Medical notes (a free-text column nobody updates consistently)
- Adoption status (a color you change manually)
- Notes (where everything important actually lives)
- Three columns from 2022 that someone added once and nobody touches
Your job in week one is to separate the structured data (intake date, breed, current placement) from the narrative (the notes column, the chat history). Structured data migrates cleanly. Narrative needs a home, usually a "dog update" log attached to the dog's profile, not a column.
Block a single 90-minute working session and do three things:
- Mark every active dog with a row color. Anything not colored is archived, not migrated. Most rescues find 30–40% of their spreadsheet is stale.
- Identify your "source of truth" columns. Usually: name, intake date, current foster, medical status, adoption status. Everything else is either derivable or belongs in the notes log.
- Screenshot the spreadsheet. Seriously. Print it to PDF. You're not deleting it; you're freezing it so you have a fallback.
Week one, day three: build your foster roster first
The mistake almost everyone makes is importing dogs first. Don't. Import your foster homes first.
Here's why: every dog record needs to reference a foster home. If you import dogs first, you end up typing "Sarah M." as free text in 40 different places, and three months later you can't tell whether "Sarah M.", "Sarah Mitchell", and "S. Mitchell" are the same person. Start with the roster of 20–60 humans, get their capacity, preferences, and contact info entered cleanly once, and then every dog you import attaches to a real record.
For each foster, capture: name, email, phone, address (for proximity to adopters), max dogs, dog size/age preferences, kid/cat/dog compatibility, and any notes from past placements ("great with shy dogs", "can't do high energy"). That last column is the one that makes future matching feel like magic instead of guesswork.
Week one, day five: import dogs in tranches
Now you import dogs, but not all at once. Do it in three tranches:
- Active fosters first (today). Every dog currently in a home. These are the records your coordinator is touching daily.
- In-progress adoptions next (day six or seven). Dogs with a pending application or upcoming meet-and-greet.
- Recently adopted (week two). The last 90 days. Skip anything older. It's history, not operations.
The reason for tranches isn't technical. It's psychological. The first time your coordinator opens the new system and sees only their active caseload, the relief is immediate. They were drowning. Now they can see the bottom of the pool.
Week two: move the conversation off the group chat
This is the part that breaks most migrations. The data moves fine. The chat doesn't.
Your group chat is doing four jobs simultaneously: foster check-ins, vet coordination, social bonding, and emergency alerts. A platform can replace three of those, but you have to be deliberate about which.
Here's the split that works:
- Check-ins → structured updates. Every foster submits a quick "how is your dog today" form. It attaches to the dog's record automatically. Your coordinator stops asking; the data just shows up.
- Vet coordination → medical records on the dog. Upcoming appointments, vaccine due dates, medication schedules all live on the dog's profile where the next coordinator can find them in five seconds.
- Emergency alerts → keep the group chat. Do not try to replace this. When a foster's dog is bleeding at 11 p.m., they need a channel where humans respond in seconds. That's a chat, forever.
- Social bonding → keep the group chat. Pictures of foster puppies in costumes belong in WhatsApp, not in an operations system.
Tell your fosters explicitly: "Daily updates go in the check-in form. Anything urgent or fun stays in the group." Within ten days the group chat quiets down to the things it was always best at, and your coordinator stops scrolling 200 messages a day looking for the one about Buddy's appetite.
The thing nobody tells you about the migration
Your fosters will not revolt. They will be relieved.
Fosters hate the group chat too. They feel guilty when they miss a message, anxious when they can't remember if they reported something, and frustrated when their update gets buried under twenty other notifications. A structured form takes 45 seconds and gives them a clear "I did my job" feeling. That's the actual value proposition: not to your operations, but to the volunteers you're trying to retain.
What success looks like at day 14
Two weeks in, you should be able to answer these questions in under 30 seconds each, without opening a spreadsheet or scrolling a chat:
- How many dogs are currently in foster?
- Which fosters have open capacity for a medium-energy adult dog?
- Which dogs are overdue for a vaccine?
- When did we last hear from the Johnsons about Buddy?
- How many dogs did we adopt out last month?
If those answers come fast, you've made the jump. If they don't, the migration isn't done. That's usually because the spreadsheet still lives somewhere and one coordinator hasn't fully let go. That's normal. Give it another week.
The director's case for funding this
If you're a coordinator reading this and your director is on the fence, the argument is not "the spreadsheet is bad." The argument is: a structured system is the only way the rescue survives the coordinator leaving. Spreadsheets and group chats are illegible to the next person. A real operations layer is the institutional memory you're currently storing in one human's head.
That's the migration worth doing. Two weeks of focused work to make your rescue continuity-proof.
Ready to start your two-week migration?
PupOps is built specifically for the foster-coordination workflow described above. Start a free trial and import your first tranche today, or run our capacity calculator to see what your foster network can actually handle.