01
The dilemma
Youth camps have an awkward data shape. The person attending is not the person paying, there are usually two parents, siblings share parents, and every form submission risks creating a duplicate of somebody. The academy had outgrown a lightweight CRM that assumed one contact per deal.
What was breaking
- Family units did not fit the data model. A camper linked to two parents, with siblings sharing those parents, is not something a simple contact-and-deal structure handles cleanly.
- Duplicates were unavoidable. Each parent submitting a form risked creating another version of the same family.
- Paid and free camps were run the same way. Impact camps and paid camps have different enrollment, payment and communication needs, and neither was being served well by a single shared process.
- Payment tracking was disconnected from enrollment. Who had paid for which camper was a separate question from who was enrolled.
- Marketing could not be segmented properly. Without a reliable family structure, communications went to the wrong person or twice to the same one.
The cost of standing still
Duplicate family records are not a tidiness problem. They mean a parent receives the same email twice, a camper appears on two rosters, and a payment cannot be matched to an enrollment, and for a youth program, an administrative error in front of a parent is a trust problem.
02
The idea
The migration was straightforward. The architecture was the work. We rejected a contact-centric model, the default, and the reason the duplicates existed, in favor of making the camper the core record, with parents as linked entities. Enrollment, payment and marketing all hang off the camper, which is the only unit that is unambiguous.
The principles we worked to
- The camper is the core record. Because the camper is what the academy actually delivers to, and the only entity that cannot be duplicated by a parent filling a form.
- Parents as linked records, intelligently matched. Forms link to an existing parent where one exists and create one only where it does not.
- Separate pipelines for separate camp types. Paid and Impact camps have genuinely different processes and should not share one.
- Build for the phases not yet commissioned. Sponsorship tracking and staff onboarding were designed for, even though they were out of scope.
What we ruled out, and why
| Option considered | Why we did not take it |
|---|---|
| Staying on the lightweight CRM | Fast and cheap, and structurally incapable of representing a family unit. |
| A contact-centric model with a family field | The conventional shortcut. It puts the burden of avoiding duplicates on whoever fills in the form. |
| One shared pipeline with a camp-type field | Simpler to configure and it would have forced paid and free camps to share automation that suits neither. |
03
The build
Four architectural decisions, each with a downstream consequence.
Camper-centric architecture
The camper record drives enrollment, payment tracking and marketing segmentation, with Parent 1 and Parent 2 as linked records. Siblings share parent records rather than duplicating them.
Distinct enrollment pipelines
Separate pipelines for paid camps and Impact camps, each with the automation, communication and payment handling appropriate to its type.
Intelligent form linking
Forms capture parent data and then link to the correct existing camper and parent records, or create them, without producing duplicates, the specific failure the old structure could not prevent.
Payment tracking automation
Payment status dynamically applies service-specific tags, so enrollment, payment and communication stay aligned without manual reconciliation.
04
The impact
| Measure | Before | After |
|---|---|---|
| Platform | Zoho Bigin | Zoho CRM, camper-first model |
| Data model | Contact-centric | Camper core, parents linked |
| Duplicate records | Created on every form submission | Prevented by intelligent linking |
| Camp types | One shared process | Two distinct pipelines |
| Payment tracking | Separate from enrollment | Automated, tag-driven |
| Marketing segmentation | Unreliable | Tailored to camp type and family |
| Future phases | Not accommodated | Sponsorship and staff onboarding designed for |
Beyond the numbers
- The family data model holds. Highly organized, duplicate-free records across campers, parents and siblings.
- Communications are tailored to the camp type. Marketing and logistics messaging fits what the family actually signed up for.
- The foundation is extensible. Sponsorship tracking and staff onboarding can be added without re-architecting.
05
What comes next
The engagement continues. These are the next moves on the table.
- Sponsorship tracking linking donors to funded Impact camp places.
- Staff and volunteer onboarding on the same platform.
- Multi-season camper history and progression tracking.
Engagement delivered by the Ideentrix founding team. Technologies, scope and outcomes as recorded at project close, published with the client's consent.
