A poker club migration from one platform to another is not a weekend project. It is a coordinated operational event spanning player data export, full chip settlement, agent briefings, notification cascades, overlap periods where two clubs run simultaneously, and the eventual shutdown of the old infrastructure. Done correctly, you retain 85-95% of your active roster. Done incorrectly, you lose half your regulars to coordination failures, disputed balances, and dead tables during the transition window.
This guide covers the operational mechanics of moving a club from one platform to another — whether that is PPPoker to PokerBros, PokerBros to ClubGG, or any other combination. The process structure is the same. The details vary by platform.
Why Clubs Migrate: The Four Forcing Functions
Platform switches are not impulsive. They are forced by one of four concrete operational pressures.
Union economics collapse. A club joins a union for liquidity. The union raises its rake cut from 15% to 25%, or changes payout terms from weekly to monthly, or imposes new player acquisition quotas the club cannot hit. At that point, staying costs more than leaving. Many Brazilian clubs migrated from PPPoker to Suprema in 2025 when PPPoker’s largest union restructured commission tiers, making mid-volume clubs unprofitable.
Platform policy changes. ClubGG introduced mandatory KYC for clubs above 200 members in late 2025. Clubs targeting privacy-focused markets could not comply without losing their rosters. Those clubs moved to PPPoker or X-Poker, where anonymous membership remains the standard model. Policy changes do not give operators time to adapt — you migrate or you close.
Traffic density shifts. The club runs NLH and PLO at mixed stakes. Traffic on the current platform is heavy at low stakes but dies above 5/10. PokerBros has deeper mid-stakes PLO pools than the club’s current app. The owner migrates to access that liquidity, knowing regulars who play 5/10+ will follow the action.
Platform ban risk. The club receives a warning from platform compliance about activity patterns, third-party tool use, or unclear sourcing of chip flow. Whether the warning is justified or not, the owner evaluates the risk of a full club ban — which would vaporize the roster overnight — against the cost of a controlled migration. Many clubs choose migration as the clean exit before forced closure.
The decision to migrate is rational. The execution is where most clubs fail.
Pre-Migration Preparation: Settlement and Data Export
A migration begins weeks before the announcement. The first phase is invisible to players.
Full Chip Balance Settlement
Every player’s chip balance in the old club must reach zero before migration. This is not optional. Attempting to carry balances across platforms without full settlement creates accounting gaps that take months to reconcile.
Across the clubs we manage, settlement starts 5-7 days before the migration announcement. The owner and agent team contact every player with a positive balance and process withdrawals. Players with negative balances are notified of settlement deadlines. Any player who does not settle by the cutoff forfeits their balance — this must be stated clearly in the migration notice to avoid post-migration disputes.
The settlement target is not “most players at zero” — it is 100% of active players at zero. A club with 180 members and 12 unsettled balances at migration time is operationally stuck: those 12 players will file disputes in the new club, demand retroactive transfers, and create agent workload spikes for weeks.
Player and Agent Data Export
Most mobile poker apps do not offer a “export your club roster” button. The owner builds the roster list manually or through agent reporting.
The essential data points for each player: in-app nickname, agent of record, approximate chip balance at settlement, contact method (Telegram username, WhatsApp number, WeChat ID). The agent of record is critical — when the migration is announced, each agent is responsible for notifying their own player network. A player list without agent attribution creates a coordination failure where nobody knows who is responsible for onboarding which players.
For clubs operating in PPPoker or PokerBros unions, the union administrator may have access to full club rosters. Request the export 10 days before the planned migration. If the union refuses or delays, build the list manually from agent reports and the in-app member directory. Some owners screenshot the member list in 50-player increments and transcribe it — tedious, but it works.
Agent Briefing 48 Hours Before Announcement
Agents learn about the migration before players do. This is mandatory. The owner schedules a group call or sends a detailed written brief covering: the new platform, the migration timeline, the new club code, the new chip settlement process, and any changes to agent commission structure.
Agents who learn about the migration at the same time as players often interpret it as a signal the owner does not trust them. In Brazilian and Southeast Asian markets where agent loyalty is territorial, this perception alone causes agent defections. Brief agents first, answer their questions, confirm they are onboard, then proceed to the player announcement.
Technical Migration: Setting Up the New Club
While settlement proceeds and agents are briefed, the technical setup of the new club begins. This happens in parallel, not sequentially.
New Club Creation and Configuration
The owner creates the new club on the destination platform following the same setup steps covered in platform-specific guides like how to create a PokerBros club or how to create a PPPoker club. The club name, logo, and branding typically carry over for continuity — regulars need to recognize the club instantly when they receive the migration notice.
Chip values are set to match the old club’s chip-to-currency ratio. If the old club used 1 chip = 1 USD, the new club uses the same ratio. Changing chip denominations during migration adds conversion friction that players interpret as hidden fees. One club we managed attempted a 10:1 chip conversion during a PPPoker-to-X-Poker migration; player complaints about “why did my 10,000 chips become 1,000” created three weeks of dispute resolution that could have been avoided by keeping the denomination constant.
Format and Stake Replication
The new club replicates the old club’s table formats and stake levels exactly. If the old club ran 6-max NLH at 1/2, 2/5, 5/10 and PLO at 1/2, 2/5, the new club launches with the same structure. This is not the time to experiment with Short Deck or add a 10/20 stake tier — migration is about continuity, not expansion.
A 100-player club on PPPoker runs $45/month for the Level 2 license; the same capacity on PokerBros costs $20–26 but with chip costs 30% higher, which affects the owner’s cost structure but does not change what the players see. The formats stay identical.
Launching Table Activity Before Players Arrive
One of the most common migration failures is announcing the new club, watching players install the app and log in, and discovering the club lobby is empty. Regulars who see zero active tables interpret it as a failed migration and stop logging in.
Managed AI infrastructure solves this. PokerNet AI spins up table activity in the new club on the same day the migration is announced — often before the first players complete onboarding. When regulars log in 24-48 hours after the announcement, they see tables running at their usual stakes. This is the operational signal that the migration is real and the club is not dying during the transition.
How to keep your poker club active 24/7 covers the always-on model in detail. During migration, the always-on model is not optional — it is the difference between retaining 90% of your roster and losing half to perceived abandonment.
The Notification Cascade: Agents First, Players Second
The migration announcement is not a single message. It is a cascade: agents notify their players, the owner posts a general announcement in the club notice, and follow-up reminders go out at T-3 days, T-1 day, and T-day (migration cutoff).
Agent-Led Notification
Each agent contacts their player network individually — Telegram DM, WhatsApp message, WeChat group message. The message includes: the new platform name, the new club code, the agent’s contact info on the new platform, and the timeline. Agents who manage 20-50 players spend 2-3 hours on this notification round. Agents who skip it and assume the general announcement is sufficient lose 30-40% of their players to inaction.
In one club migration we tracked from PokerBros to PPPoker, agents who sent individual messages retained 92% of their players. Agents who relied solely on the group announcement retained 61%. The difference is follow-through: individual messages are read; group announcements are scrolled past.
General Club Announcement
The owner posts the migration notice in the old club’s in-app notice field and pins it in any club-wide Telegram or WhatsApp group. The notice includes: why the club is migrating (platform economics, union change, better traffic — keep it brief), the new platform and club code, the migration timeline, the settlement deadline, and a reassurance that chip balances will transfer after settlement.
The tone is factual, not apologetic. Migrations are normal. Clubs switch platforms every 12-18 months on average. Treating the migration as a crisis signals instability. Treating it as a planned operational upgrade signals control.
Straggler Reminders
At T-3 days, T-1 day, and on migration day, the owner and agents send follow-up reminders to players who have not yet joined the new club. The straggler list is visible from the new club’s member count compared to the old club’s roster. If the old club had 180 active members and the new club has 140 members three days before cutoff, 40 players are stragglers. Agents contact their stragglers individually.
Overlap Period: Running Two Clubs Simultaneously
The old club does not close the day the new club opens. Both clubs run simultaneously for 7-14 days. This overlap period is the operational buffer that prevents catastrophic player loss.
During overlap, tables run in both clubs. Multi-table poker club economics become temporarily more expensive because the owner is funding table activity on two platforms, but the cost is unavoidable. Regulars who have not migrated yet still play in the old club. Regulars who migrated early play in the new club. The owner cannot force the transition faster without losing players who need more time to install the app, complete agent onboarding, or resolve settlement questions.
Action density during overlap is critical. If the new club’s tables are dead while the old club’s tables are active, regulars conclude the migration failed and stop checking the new club. If the old club goes dark immediately, stragglers who were planning to migrate “next week” have nowhere to play and drift to other clubs. Both clubs must stay active until the cutoff date.
Managed infrastructure handles this operationally. PokerNet AI runs in both clubs during overlap, maintaining table activity at the configured stake levels and formats in each. The owner sets a higher concurrency cap in the new club and a lower cap in the old club, gradually shifting density toward the destination platform. By the end of the overlap period, the new club is the primary action hub and the old club is a low-traffic fallback for stragglers.
Closing the Old Club and Handling Stragglers
On the announced cutoff date, the old club closes. In most apps, “closing” means the owner removes all agents, zeros out all chip balances, and either deletes the club or leaves it as an inactive shell.
Final Settlement Sweep
Before closure, the owner and agents conduct a final settlement sweep. Any player with a remaining chip balance is contacted one last time. Players who do not respond forfeit their balance — this was stated in the migration notice, so it is not a surprise. In practice, stragglers with significant balances respond. Players with 100-500 chips often do not, and those small balances are written off.
The settlement sweep takes 24-48 hours. Rushing it creates post-closure disputes. One club we tracked closed the old PPPoker club 12 hours after the cutoff announcement, and five players with unprocessed withdrawal requests filed complaints that took the owner three weeks to resolve. The correct sequence is: announce cutoff → wait 48 hours → process final settlements → close.
Stragglers Who Miss the Migration
In every migration, 5-15% of the old roster never completes onboarding in the new club. These are not lost players — they are inactive players who were not playing regularly in the old club either. The owner tracks them via agent reports. If a straggler becomes active again weeks or months later, the agent contacts them with the new club code. If the straggler does not respond, they are marked inactive.
Some stragglers migrate to competing clubs. This is expected. Migrations are natural moments for players to reevaluate where they play. A 10% roster loss during migration is operationally normal. A 30% loss signals a coordination failure — unclear messaging, poor agent follow-through, or dead tables in the new club during the overlap period.
Platform Migration Comparison: Setup Complexity by App
Not all platforms are equally easy to migrate to. The destination platform affects timeline, technical complexity, and agent onboarding difficulty.
| Platform | Club Setup Time | Player Onboarding Complexity | Chip Purchase Friction | Agent System | Migration-Friendly? | |—|—|—|—|—| | PPPoker | 30 min | Low — app is mature, club codes simple | Mid — diamond bundles, conversion step | Flexible agent hierarchy | Yes | | PokerBros | 20 min | Low — mobile-first UI, fast install | Higher chip cost but streamlined | Agent system well-documented | Yes | | ClubGG | 45 min | Medium — subscription model confuses some players | Low for cash, higher for tournaments | Integrated but less flexible | Medium | | X-Poker | 25 min | Medium — regional app store issues in some markets | Low | Agent model similar to PPPoker | Yes |
PPPoker and PokerBros are the most migration-friendly platforms because their club and agent systems are mature and widely understood by both owners and players. Migrating to ClubGG from a fully anonymous platform introduces subscription friction — players accustomed to zero up-front cost resist the membership fee, even when it is $5-10/month. Migrating to X-Poker works smoothly in Asian and Eastern European markets but faces app availability issues in Western markets where the app is not listed in major app stores.
Table Activity Continuity During Migration
The single most damaging migration failure is allowing tables to go dark during the transition. Regulars interpret dead tables as a signal the club is collapsing. Even if the owner eventually rebuilds activity, those regulars have already moved to competing clubs.
Table activity continuity is not about manually propping tables with house players for two weeks — that approach does not scale and burns out the owner’s team. It is about deploying managed infrastructure that maintains configured activity levels automatically.
PokerNet AI operates at the NLH, PLO, and Short Deck formats. The owner configures the new club’s activity schedule — which stakes, which formats, which time windows, how many concurrent tables — and the infrastructure executes within those bounds. During migration, the configuration spans both the old and new clubs. As the overlap period progresses, the owner reduces concurrency in the old club and increases it in the new club, shifting density gradually without creating a single moment where both clubs are dead.
This is not autonomous AI deciding to run your club. This is AI table activity infrastructure executing the schedule you set. The owner decides where and when. The infrastructure decides how to play. During migration, the “where” is two clubs at once. The infrastructure handles that operationally.
Regulars who log into the new club 48 hours after the announcement and see active tables at their usual stakes stay. Regulars who log in and see an empty lobby leave. The operational difference is whether managed infrastructure was deployed before the migration announcement or after players started asking “why is nobody playing?”
Edge Cases and Failure Modes
Three edge cases appear in most migrations and must be planned for.
Agents who refuse to migrate. One or two agents decide they will not switch platforms — either because they dislike the new app, they have competing commitments in another club on the old platform, or they interpret the migration as a loss of status. These agents effectively resign when the old club closes. The owner consolidates their player load across the remaining agent team or recruits new agents from the player base. In agent-heavy markets like Brazil, losing one agent during migration is operationally normal.
Disputed chip balances. A player claims they had 8,000 chips in the old club; the agent’s records show 5,500. The dispute surfaces when the player requests their opening balance in the new club. The resolution process depends on whether the old club kept transaction logs. If logs exist, the dispute resolves in 24 hours. If the club relied on agent memory and screenshots, resolution takes days and damages the player’s trust. This is why full settlement before migration is mandatory — it eliminates the disputed-balance failure mode entirely.
Platform downtime during migration window. The new platform experiences an outage or maintenance window during the overlap period. Tables go dark for 6-12 hours. Regulars who chose that window to try the new club for the first time see downtime and assume the club is broken. The owner cannot control platform uptime, but can control messaging: immediate notification in the club group that the downtime is platform-wide, not club-specific, with an ETA for restoration. Players who understand the downtime is external wait it out. Players who receive no explanation assume the club failed and stop logging in.