Club Merger & Amalgamation — GoClubPro

Training Module 104 | Merging Two Clubs, Consolidating Data, and Managing the Transition

What This Guide Covers

Club mergers and amalgamations are uncommon but significant events — two clubs combining into one entity for financial sustainability, membership viability, or strategic reasons. This module covers how to manage a club merger within GoClubPro: which club's platform account becomes the primary, how to move members across, how to handle finances, and how to communicate the change.

Primary audience: Club Admin, Treasurer — clubs undergoing a merger or amalgamation See also: 36 Admin Handover Guide · 84 End-of-Year Data Archiving · 94 Transitioning Away from the Platform · 19 End-of-Season

SECTION 1: BEFORE THE MERGER — PLANNING STAGE

Define Which Platform Account Survives

Before touching any data, the committee of the merged entity must agree:

Option A — One club absorbs the other:

Club A's GoClubPro account becomes the merged club's account
Club B's account is wound down
Club B's members are migrated into Club A's account

Option B — New entity, new account:

A new GoClubPro account is created for the merged club
Both legacy accounts are wound down
All members from both clubs are migrated into the new account

Which option to choose:

Option A is almost always simpler — existing fee history, payment records, seasons, and teams remain intact
Option B is better if the merged club has a new name, new colours, and wants a clean slate
Discuss with GoClubPro support before choosing — they may have guidance or tooling to assist

The Pre-Merger Data Audit

Before migrating, both clubs should export their current data:

Each club exports:

Member register (Admin Panel → Members → Export CSV)
Accounting ledger (Treasurer → Accounting → Export) — includes Bank Transfer and wallet credit history
Outstanding fees list (Aging report → Export)
Player statistics and history (if accessible via export)

Store exports in a shared Google Drive folder accessible to both committees.

Why export before merging: Once Club B's account is wound down, its historical data is no longer accessible through the platform. The export is the permanent archive. Module 84.

Communicate with Members Before Any Platform Change

Members need to know what's happening and what it means for them. Send a clear Broadcast from both clubs:

"Important: Club Merger Update

As you may be aware, [Club A] and [Club B] are merging to form [New Club Name] from [date].

What this means for you:

Your GoClubPro account is not changing yet — you'll receive specific instructions when the migration happens

All current registrations and fee payments are still valid

Your historical data (stats, match history) will be preserved

We'll send details on next steps in the coming weeks. Questions? Contact [name] at [email]."

Do not begin the technical merger until members are informed. Unannounced platform changes cause confusion and erode trust.

SECTION 2: MIGRATING MEMBERS

Adding Club B Members to Club A's Account

There is no automated cross-account member migration tool in GoClubPro. The process is manual:

Method 1 — Re-invitation:

Export Club B's member email list
In Club A's Admin Panel: Admin Panel → Members → Invite → paste emails in bulk
Members receive an invitation to join Club A's account
Once they accept, assign them to the relevant team in the new merged season

Method 2 — Manual add: For members who may not respond to an invitation email:

Admin Panel → Members → Add Member manually
Enter their details
Send them a "welcome to the new account" message with their login instructions

Preserving historical stats: Stats from Club B cannot be automatically transferred to Club A. They remain in Club B's account (or the exported data). The clean record in Club A starts from the merged season. Note this clearly to affected players.

Assigning Merged Members to Teams

After migration, each former Club B member needs to be:

Assigned to the correct team in the merged season
Given their correct role (Player, Coach, Parent, etc.)
Checked for any notes from Club B's records (injuries, WWCC status, medical conditions) — these need to be manually re-entered in Club A's Admin Panel

Data sensitivity: Transfer only information that is relevant and appropriate to transfer. Medical conditions, hardship waivers, and disciplinary records should be handled by the relevant committee roles, not shared broadly during the merger process.

Handling Duplicate Members

If a player was registered at both clubs (e.g., played for both in different grades), they will end up with two migration invitations. The standard outcome:

Accept one invitation to the primary merged-club account
The second invitation is declined or ignored
Admin confirms their team assignment and role

SECTION 3: FINANCIAL CONSOLIDATION

Combining the Treasuries

The merged club's finances start fresh in the primary account's Accounting ledger. The financial merger requires:

Final closing entries for Club B: In Club B's Accounting, record a closing entry: "Closure — transfer of balance to [Club A/New Club] — [amount] — [date]"
Opening entry in Club A: "Amalgamation — transfer of funds received from [Club B] — [amount] — [date]"
Outstanding fees from Club B members: A list of Club B members with outstanding balances, transferred to Club A's collection responsibility

Bank accounts: The actual bank account merger is a banking/legal matter separate from the platform. GoClubPro payments (Bank Transfer declarations and wallet credit) are not tied to a payment processor, so there is no processor account to migrate — the club's own bank account is what matters.

Payment Continuity for the Merged Club

Since GoClubPro payments go through Bank Transfer declarations (verified by the Treasurer) and wallet credit — not a card processor — there's no payment account to transfer. Two things do need attention:

Wallet credit balances: Club B members' wallet balances do not automatically carry over to Club A. Treat this the same as outstanding fees (above) — the merged club's Treasurer manually credits each member's Club A wallet to match their Club B balance.
Bank Transfer instructions: update anywhere the club's bank account details are shown to members so they transfer funds to the surviving entity's account, not the wound-down club's.

If Club A simply continues as the entity (Club B dissolves into Club A), no bank account change is needed unless the merged club is opening a new account.

During transition: Ensure any Bank Transfer declarations and wallet top-ups still pending Treasurer verification for Club B are reviewed and settled before the account is closed. Module 37.

Outstanding Fees During the Transition

Members who owed fees to Club B carry those obligations to the merged club. Handle this carefully:

Export Club B's Aging report before merger
Identify members with outstanding balances
Decision: does the merged committee honour Club B's fee waiver commitments? (Yes — discuss and document)
For each member with outstanding fees: the merged club Admin manually creates a payment obligation in Club A's system matching the outstanding amount

Communication: Contact affected members before the merge to confirm their balance and payment options. Unannounced new fee items in their Payments page will cause concern.

SECTION 4: SEASON AND COMPETITION SETUP

Setting Up the First Merged Season

If the merger takes effect at the start of a new season:

Create a new season in the primary account: "[Merged Club Name] [Year]"
Create teams that reflect the merged club's structure
Re-register all members (from both legacy clubs) in the new season
Set fee configuration for the merged club
Configure League Platform Competition IDs for the new season and any new association affiliations

If the merger takes effect mid-season:

Assess whether competing mid-season transfer of registrations is permitted by the association
Association admin contact is essential — some associations have specific amalgamation registration processes
Module 81 for association portal guidance

Club Identity in the Platform

Once the merger is agreed:

Settings → Club Details: update club name, logo, colours, contact email (Module 93)
Update the public join link/page description
Update the Noticeboard header and any pinned posts that reference the old club names

Members will see the updated name and branding on next login.

SECTION 5: WINDING DOWN CLUB B'S ACCOUNT

The Club B Closure Checklist

Before deactivating Club B's GoClubPro account:

☐ All member data exported (member register CSV)
☐ All Accounting data exported (full ledger CSV)
☐ All pending Bank Transfer and wallet declarations reviewed and settled
☐ Wallet credit balances manually transferred to members' Club A wallets
☐ All active members migrated to Club A/new account
☐ Outstanding fees communicated to affected members
☐ Historical data archived in Google Drive
☐ Committee confirmed all exports are complete and stored
☐ Contact GoClubPro support to request account closure

Do not close the account until all items above are confirmed. Once closed, data recovery is not guaranteed.

Notifying the Association

The association must be notified of the amalgamation:

Association portal (your league platform or SportsTG): update team/club details
Competition entries for the merged club may need to be re-entered under the new entity name
Insurance coverage: inform the national body — policy may need updating to reflect the merged club

Association Admin contact (Module 16, 81) for specific protocols in your sport.

SECTION 6: COMMUNICATION PLAN

The Merger Communication Timeline

When	Message	Channel
8+ weeks before merger	Merger announced; member vote if required by constitution	Broadcast + Noticeboard
4 weeks before	Migration details explained; member action required	Broadcast + Email
2 weeks before	Final reminder; migration invitation sent	Broadcast
Migration week	"Your account is now active in [New Club]" welcome	Email / Broadcast from new account
Week after	FAQ post on Noticeboard; committee contact for issues	Noticeboard
4 weeks after	Confirm all members have migrated; chase non-responders	Admin Panel review

The Member FAQ Post (Noticeboard)

After the migration, post a FAQ on the Noticeboard:

Merger FAQ — [Club Name]

Q: I have stats from my time at [Club B]. Will they transfer? A: Your season stats from [Club B] are recorded in [Club B]'s archived system. We're maintaining a full export of that history. Stats in the new platform start from [Season Year]. We'll publish a historical record document.

Q: I had a fee waiver / hardship arrangement at [Club B]. Does it carry over? A: Yes — contact [Treasurer name] at [email] to confirm your arrangement is noted in our system.

Q: I'm receiving fee requests for amounts I already paid to [Club B]. A: Contact [Admin name] immediately so we can reconcile. We want to make sure no-one is double-charged.

VISUAL: Merger Workflow Overview

6–8 WEEKS BEFORE
 Committee agrees on merger and primary account
 Both clubs export all data
 Members informed via Broadcast
 │
 ▼
4 WEEKS BEFORE
 Migration invitations sent to Club B members
 Outstanding fees list prepared
 New merged season created in primary account
 │
 ▼
MERGER DATE
 Club B members accept invitations
 Assigned to merged-club teams
 Fee obligations confirmed
 Club B's pending declarations settled and wallets transferred
 │
 ▼
FIRST WEEK AFTER
 Noticeboard FAQ posted
 Admin Panel: confirm all members migrated
 Accounting: opening entry for amalgamation funds
 │
 ▼
4 WEEKS AFTER
 Chase any non-migrated members
 Club B account closure requested via support
 Historical archive confirmed in Google Drive

TOOLTIPS & HINTS

Export before anything — the moment Club B's account is closed, platform-based data access ends; export is the permanent archive
Option A (absorb) is simpler than Option B (new account) — keeps payment records, seasons, and existing data intact
No automatic member migration — all member transfers are manual (invitation or manual add)
Stats don't transfer — historical stats stay in Club B's archived data; merged-club stats start fresh
Association notification required — don't just merge the platform; notify the association and update competition registrations

FAQ

Q: Can GoClubPro support help us with the merger? A: Yes — contact GoClubPro support before beginning. They can advise on the best approach for your specific situation and may be able to assist with bulk data operations.

Q: We want to preserve the home ground, colours, and name of Club B even though Club A is the surviving entity. Is that possible? A: Branding in GoClubPro is fully configurable (Module 93). The merged club can use any name, logo, and colours. The platform account is just the technical container — the identity is entirely yours to set.

Q: A member from Club B refuses to register with the merged club. What happens? A: Their relationship is now with the merged entity. If they're not registered in the merged club, they won't appear in the system and can't be selected. Communicate with them personally; address concerns. If they've genuinely decided not to continue, archive them once you're certain.

COMMON MISTAKES

Mistake	Consequence	Prevention
Closing Club B's account before exporting	Permanent data loss	Full export checklist confirmed before closure
Not notifying members before migration	Confusion; members think they've been hacked	Communication timeline: 8 weeks, 4 weeks, 2 weeks
Not settling pending declarations or wallet balances first	Outstanding payment or wallet credit lost	Clear Reconciliation tab and transfer wallets before closure
Creating duplicate member records	Confusion; duplicate payment items	Check for existing account by email before manual add
Forgetting to notify the association	Competition entries not transferred; registration chaos	Association contact is part of the merger checklist

SHORT ONBOARDING SCRIPT

"A club merger in GoClubPro comes down to two decisions: which account survives, and how to move Club B's members into it. Almost always, Option A — Club A absorbs Club B — is simpler. Before touching anything, both clubs export their full data: member register, accounting ledger, outstanding fees. Members get 4–8 weeks notice before migration invitations are sent. Once accepted, assign them to teams in the merged season. Stats don't transfer automatically — they stay in Club B's archived data. Settle all pending Bank Transfer and wallet declarations, and transfer members' wallet balances, before closing Club B's account. Get the association's notification done in parallel. Export everything before requesting account closure."

MICRO-TRAINING QUICK TIPS

Option A (absorb) > Option B (new account) for simplicity
Both clubs: export data before any platform changes (member CSV, accounting CSV)
8 weeks' member communication minimum before migration
Member migration: re-invitation or manual add — no automatic transfer
Historical stats stay in archived Club B data; new platform stats start from merger season
Settle all pending Bank Transfer/wallet declarations and transfer wallet balances before closing Club B's account
Notify the association: competition registrations must reflect the merged entity

Training Module 104 | See also: 36 Admin Handover Guide · 84 End-of-Year Data Archiving · 94 Transitioning Away from the Platform · 20 New Season Setup · 93 Branding & Customisation