Data portability and migration: what actually moves when you switch camp software

The fear behind switching camp software is rarely the new system. It’s the old one — and the years of camper history sitting inside it. Every registration, every medical form, every payment, every returning family you’ve built up over five or eight or twelve seasons lives in a system you’re about to leave. The honest worry is that some of it won’t come with you, and you won’t find out which part until it’s gone.

That worry is reasonable. Not every record moves the same way, and a vendor who tells you it all transfers cleanly is either not looking closely or hoping you won’t. Migration is part of camp management software, and the part that decides whether a switch goes well is whether you know — before you commit — what ports cleanly and what gets stranded. This walks through that, record type by record type, by the shape of the data rather than the amount.

What a clean export contains, and what gets left behind

Start with the distinction that predicts everything else: structured data versus loose data.

Structured data is anything your current system stored as a real field — a camper’s birthdate in a birthdate column, a session enrollment as a record that points at a session, a fee as a number tied to a plan. Structured data ports well because it maps. The new system has a place to put each field, and the values land where they belong.

Loose data is everything the old system held informally. Free-text notes typed into a comment box. Custom fields a previous director added to track something specific. Records the export hands you as a PDF instead of a row of values. Loose data is where migrations lose the most, not because it can’t move at all, but because it arrives without structure — a wall of text where there used to be sortable, filterable records.

The practical read: the more a record was stored as named fields, the more cleanly it crosses. The more it lived as notes and attachments, the more careful — and the more lossy — its migration is.

Camper records, contacts, and history

This is the backbone, and the good news is it’s also the most portable part.

A camper record is structured almost by definition — first name, last name, date of birth, grade, school. Contacts hang off it as their own records: each parent or guardian with a name, email, phone, and a relationship to the camper. These map straight across, because both the system you’re leaving and the system you’re joining understand a camper as a set of named fields.

The history attached to the camper is what makes the record worth keeping. Which seasons they attended. Which sessions. What their status was each year. That history is what lets a new system recognize a returning camper instead of treating every familiar face as a stranger. When the export carries it as structured records, it ports. When it’s been collapsed into a summary or a note, you keep the camper but lose the story.

Registrations and payment history

Registrations and the money behind them are where “it mostly migrated” quietly becomes a problem.

A registration is structured: a camper, a session, a status. Those move. The risk lives in what’s attached — the fee each family was charged, the tier or plan they were on, the discounts and adjustments applied. That financial history is what makes year-over-year reporting possible and what tells you, next season, what a returning family already paid and on what terms.

When fee and payment history exports as structured records, it lands complete and your financial past survives the move. When it exports as a flattened total — a single number per family with the breakdown gone — every historical figure becomes an asterisk. You can see what was paid, but not how it was arrived at, and reconciliation against your prior years stops being possible. The payments move; the accounting context is what gets stranded.

Medical forms and documents

Medical data is the clearest case of a record that moves but may not stay usable.

A health record stored as structured fields — allergies, medications, dietary restrictions, doctor name and phone, insurance details — can land in the new system as those same fields. Kept that way, it stays queryable: you can pull every camper with a given allergy, surface the records still missing, sort and filter the way you do during the season.

The same record exported as a PDF arrives as a document. You can open it. You cannot filter on it, sort by it, or have the system flag a camper whose form is incomplete. The information is technically present and operationally gone. This is the migration trap that hurts most, because medical data is the data you most need to act on quickly, and a stack of PDFs is the format that makes acting on it slowest.

Uploaded documents — signed waivers, forms, files a family attached — are their own category. They move as files, which is fine, as long as each file stays linked to the right camper record instead of arriving as an unlabeled folder. The file transferring isn’t the same as the file being findable.

Returning-family and sibling links

This is the most fragile data in any migration, and the easiest to lose without noticing.

A returning-family link is the connection between this season’s camper and next season’s expectation that they’ll be back. A sibling link is the connection between two campers who share a parent. Neither lives in a single column. They live in how records reference each other — relationships, not labels — and that is exactly the kind of data a careless export flattens.

When those links survive, next year’s registration prefills instead of re-collecting, sibling discounts apply because the system knows who’s a sibling, and re-enrollment starts from what you already have. When they’re dropped, the records all arrive but the connections between them don’t. You keep every camper and every parent, and lose the head start that made returning families easy. It’s a silent loss: nothing looks missing, because nothing is — until next registration opens and the prefill that should have been there isn’t.

Time the migration to the off-season

Most of what determines a clean migration is decided before the export — by when you run it.

The camp calendar gives you a natural window. Close out the season in late summer. Migrate in the quiet stretch that follows — roughly December through January — after the season is settled and before next registration opens. That timing matters because the off-season is when your data is at its cleanest: every payment reconciled, every roster final, every medical record current, no live registration writing new records while you’re trying to move the old ones.

Migrating mid-cycle is the opposite. Half the records are in flight, the export is a moving target, and the thing you copy on Tuesday is stale by Thursday. Move on the calendar’s terms, when the data has stopped changing, and you’ve removed an entire class of migration error before you start.

The export-audit move

Here’s the step that turns all of this from a worry into a known quantity, and it costs you nothing.

Before you sign with a new vendor, send them your real export and have them tell you what ports cleanly. Not a demo of their system. Not a sales call. Your actual data — the export from your current system — read against what the new system can receive. A vendor willing to do this will tell you, in writing, which records map straight across and which go lossy on your specific camp. A vendor who won’t is asking you to find out after the contract is signed.

That’s the whole offer at Camp Runner. Send us your current export and we’ll give you an honest read: what lands clean, what’s lossy, where to be careful — before you commit anything. You can read how the export audit works, and it’s the same move the director’s guide to switching camp software lays out as the single best way to de-risk a switch.

You’ve spent years building the records that make each season easier than the last — the camper histories, the medical forms, the returning families who come back because the system remembers them. A switch shouldn’t put any of that at risk you can’t see. You run the camp. The right move is to know exactly what travels with you before you go, so the data that makes next season easier is still there when you arrive.