Migrating to GoClubPro from Another System

Training Module 55 | Moving from Spreadsheets, SportsTG, or Another Platform

What This Guide Covers

Most clubs don't start from scratch — they're moving from something: a spreadsheet, SportsTG, a custom system, or even just a WhatsApp group and a tin of cash. This guide covers how to bring your existing data and workflows into GoClubPro with minimal disruption.

Primary audience: Club Admins migrating an established club Also useful for: Treasurers reconciling historical data; Committees choosing whether to migrate mid-season or at season start

SECTION 1: BEFORE YOU START

What Can Be Migrated (and What Can't)

Data Type	Can Migrate	How
Member list (names, emails, phones)	Yes	Bulk invite via email + manual profile setup
Historical payment records	Partially	Manual ledger entries in Accounting
Fixture schedule	Yes	CSV upload or schedule sync
Team rosters	Yes	Manual assignment in Admin Panel
Historical match results	No	Record-only context; not in platform
Fines history	No	Fresh start on GoClubPro
Financial reports from prior system	No	Keep in your own records; export before leaving
Club documents (constitution, etc.)	No	Store externally (Google Drive, Dropbox); link in Noticeboard

Key principle: GoClubPro is a forward-looking system. Historical data has limited value in the new platform — what matters is getting the current season's data correct.

Choosing When to Migrate

Timing	Pros	Cons
Before season starts	Clean slate; no mid-season disruption	Pressure to be ready in time
End of season	Transition during a low-activity window	Need to keep old system for the season
Mid-season	Rare; only if old system is critically broken	Members confused; dual-system period

Recommended: Migrate in the off-season. Use the First 30 Days guide (Module 52) as your setup sequence. Announce the platform change at end-of-season presentation night.

SECTION 2: MIGRATING FROM SPREADSHEETS

What "Spreadsheets" Usually Means

Most spreadsheet-managed clubs have:

A "member list" tab (names, emails, phone numbers, team assignments)
A "payments" tab (who's paid what, when, how much)
A "schedule" tab (round-by-round fixtures copied from the association's website)
A group chat (WhatsApp/Facebook) for communication

None of these require a complex migration — they map directly to GoClubPro's structure.

Step-by-Step: Spreadsheet Migration

Step 1: Clean your member list

Open your existing member spreadsheet
Create columns: First Name, Last Name, Email, Phone, Team
Remove duplicates (people in multiple teams → keep one row; assign to teams after import)
Verify email addresses are current (send a test email to the list first if unsure)
Save as clean CSV

Step 2: Invite members via email GoClubPro doesn't have a bulk-import for members (they must create their own accounts for security). Options:

Option A: Send individual invite links (Admin Panel → Members & Roles → Invite → copy the club join link)
Option B: Broadcast the club join link in your existing WhatsApp/Facebook group
Option C: Email the join link to your cleaned member list from your own email client

Step 3: As members join, assign to teams

Admin Panel → Members → pending approvals
Approve and immediately assign to their team from your reference spreadsheet

Step 4: Record outstanding historical payments as manual ledger entries For members who have already paid this season in the old system:

Treasurer → Accounting → find member → Add Manual Entry
Mark "Paid" with payment date and note: "Carried forward from [Old System] — paid [Date]"
This prevents those members being chased for fees they've already paid

Step 5: Import or enter fixtures

Schedule tab → convert to CSV and upload, OR
Add fixtures manually (Admin Panel → Schedule → Add Fixture)

Step 6: Decommission the spreadsheet Once all members are in GoClubPro and the season is running:

Lock the spreadsheet (read-only)
Announce to committee: "GoClubPro is now the source of truth for all club data"
Archive the spreadsheet in Google Drive for historical reference only

SECTION 3: MIGRATING FROM SPORTSTG / SPORTS CONNECT

Understanding What SportsTG Does

SportsTG (now called Sports Connect) handles:

Member registration and payment
Fixture draw (published by the association)
Rego forms and grading
Results entry (for some associations)

GoClubPro handles many of the same functions but is club-managed rather than association-managed. The migration context depends on whether your association is moving away from SportsTG or just your club is.

Scenario A: Association Still Uses SportsTG; Club Adding GoClubPro

In this case, GoClubPro runs alongside SportsTG:

SportsTG: member registration (required by association), fixture draw, official results
GoClubPro: internal payments, communication, squad selection, team management

Data flow:

Fixtures: export from SportsTG (CSV) → import into GoClubPro Schedule
Members: registered in SportsTG + join GoClubPro separately (two systems, one source of truth per data type)

Critical: Do NOT set up GoClubPro fees as a replacement for SportsTG association levies if your association requires SportsTG registration. Use GoClubPro for club-only fees; association fees stay in SportsTG.

Scenario B: Club Fully Leaving SportsTG

If your association no longer requires SportsTG and your club is moving completely:

Checklist:

Export all member records from SportsTG (full name, email, DOB for juniors, emergency contacts)
Export your fixture history for records
Export financial history (payments, refunds)
Save exported data externally before your SportsTG access expires
Invite all members to GoClubPro
Set up fee configuration (GoClubPro now handles all fees)
Import fixtures via CSV or your league platform
Notify members of the switch with clear instructions

SportsTG data that GoClubPro can receive:

Fixtures: via CSV export
Member list: reference only; members re-register on GoClubPro themselves

SportsTG data that needs external archiving:

Historical payment records
Past season rosters and results
Association compliance documents (store in Google Drive, not GoClubPro)

SECTION 4: MIGRATING FROM ANOTHER CLUB MANAGEMENT PLATFORM

Generic Migration Checklist

Regardless of which platform you're leaving:

Before leaving the old platform:

Export full member list (CSV) — last export date noted
Export payment history (CSV) — this becomes your archive; GoClubPro won't store it
Export fixture history for the current season
Export any documents you've stored there (constitution, meeting minutes)
Take screenshots of key configuration settings (fee structures, etc.) as reference
Note your cancellation date for the old platform (don't cancel before GoClubPro is live)

Transition window (both systems live):

Run both systems for a minimum of 2 weeks if possible
Only decommission the old system after GoClubPro is fully operational and all members are in

Communication to members: Send a broadcast in the OLD system (while you still have it) announcing the switch:

Club Management Platform Switch — Action Required

[Club Name] is moving to GoClubPro, our new club management platform, from [Date].

What you need to do:

Sign up at [join link] before [Date]

Complete your profile (name, photo, emergency contact)

Your team assignment and fees will be set up there

After [Date]: [Old Platform] will no longer be active. GoClubPro is the new home for all club info.

Questions? Contact [Admin Name] at [email].

SECTION 5: HANDLING MID-SEASON MIGRATION

Mid-season migration is risky and should only be done if the old system has critically failed. If you must proceed:

The Mid-Season Migration Protocol

Day 1: Freeze the old system

Lock any new fee entries or schedule changes in the old system
Export a snapshot: member list, payment status, fixture list, financial summary

Day 2-3: Set up GoClubPro in parallel

Create the season (with an already-past start date)
Add competitions and teams
Configure fees: match the exact fee amounts from the old system
Import remaining fixtures (only future fixtures; past fixtures are historical)

Day 4: Invite members

Send the migration announcement via the old system's communication tool
Invite all members to GoClubPro
As they join, manually assign to teams

Day 5-7: Carry forward payment history

For each member: check their payment status in the old system
In GoClubPro → Treasurer → Accounting: add manual "carry forward" entries for any fees already paid

Week 2: Decommission old system

Once 80%+ of members are in GoClubPro and payment history is carried forward
Announce "GoClubPro is now live; old system is read-only"

VISUAL: Migration Decision Tree

ARE YOU MID-SEASON?
 │
 YES │ NO
 ▼ ▼
Is old system Plan migration for
critically broken? start of next season
 │ │
 YES │ ▼
 ▼ Follow First 30 Days
Follow Mid-Season Guide (Module 52)
Migration Protocol

 ↓
WHAT ARE YOU MIGRATING FROM?

Spreadsheets → Clean CSV → Bulk invite email → Manual team assign
SportsTG (still in use by assoc) → Parallel systems; CSV fixtures
SportsTG (leaving entirely) → Full export first; then GoClubPro setup
Other platform → Generic checklist above

TOOLTIPS & HINTS

Export before you leave — once you cancel the old platform, data access often disappears immediately
Members must create their own accounts — GoClubPro doesn't bulk-import accounts for security; invite via email or join link
Carry forward payment status — manually mark already-paid fees so Aging doesn't chase people who've already paid
Keep old data for 7 years — financial records have legal retention requirements regardless of platform
Parallel systems for 2 weeks minimum — don't cancel the old platform until GoClubPro is fully operational

FAQ

Q: Can GoClubPro platform support help us migrate our data? A: Contact platform support to discuss data migration options. For large clubs (100+ members) with complex historical data, support may be able to assist with bulk operations.

Q: Our association requires us to use SportsTG for official registration. Can we still use GoClubPro? A: Yes — run both in parallel. SportsTG for official association registration; GoClubPro for internal club management, payments, and communication.

Q: We have 5 seasons of financial history in our old system. Can we bring it all across? A: In theory, manual ledger entries could represent historical data. In practice, historical financial records are best kept in the old system (archived) or in an external spreadsheet. GoClubPro is optimised for current-season operations.

Q: What if we cancel the old platform and realise we need data from it? A: This is why exporting before cancelling is critical. Once access is gone, data recovery from a third-party platform is typically not possible.

COMMON MISTAKES

Mistake	Consequence	Prevention
Cancelling old platform before GoClubPro is live	No club management system during the gap	Overlap the two systems by at least 2 weeks
Not exporting historical data before leaving	Permanent data loss	Export everything before cancelling
Not carrying forward payment history	Members chased for fees they've already paid	Manual "carry forward" entries in Accounting for all pre-migration payments
Migrating mid-season without a plan	Confusion, double-payment, lost data	Use Mid-Season Migration Protocol or wait for end of season
Not announcing the switch to members	Members can't find the new platform	Broadcast in old system AND new system

SHORT ONBOARDING SCRIPT

"Migrating to GoClubPro means three things: export everything from your old system before you leave, invite members to create their own GoClubPro accounts, and manually carry forward the current payment status so nobody gets chased for fees they've already paid. Don't cancel your old platform until GoClubPro is fully live. For most clubs migrating from spreadsheets, the whole process takes 1–2 weeks at season start. Use the First 30 Days guide (Module 52) as your setup sequence."

MICRO-TRAINING QUICK TIPS

Export member list, payment history, and fixtures from old system FIRST
Don't cancel old platform until GoClubPro has 80%+ of members
Invite members via join link — they must create their own accounts
Carry forward payment status manually for any pre-migration payments
Keep old financial records for 7 years (legal retention requirement)
Parallel systems for 2 weeks minimum during transition

Training Module 55 | See also: 52 First 30 Days · 06 Admin Panel · 07 Treasurer