How-to guide
Move your academy into Kelab
Use a small, reviewed first group before a wider rollout.
For Owners and operations leads
Before you start An agreed pilot or academy setup; permission to use the records being imported.
Prepare the move#
Choose a representative group and agree who will own the new records.
- List your current people, guardian links, groups, venues, fee rules and next week's sessions.
- Clean a copy of the participant CSV and keep the original safely.
- Import and review a small sample before the complete participant list.
- Set up staff scope and verify guardian relationships through the supported process.
- Run one real session, review attendance and reconcile a fee example before inviting the wider academy.
Agree the cutover#
Player import covers supported player fields from a CSV or .xlsx file. It is not an automatic migration of every invoice, payment, consent, message or attachment from another product.
Agree how historical records will be retained, the date Kelab becomes the current record and who resolves discrepancies. Train staff using their role's tutorial. Keep a short issue list through the pilot and expand only when the daily workflow is reliable.