Migrating a club from GGBook V2

The account owner can migrate a club on the Migration page.

Before you start

  1. Back up the Gizmo database and club files.
  2. Upgrade Gizmo to version 3 and check that it works.
  3. Prepare the server address, web port and operator credentials. Check the GGBook module installation.

Connection and branches

The address and web port are filled in from the saved settings. Check them against the current Gizmo settings. Leave the password field empty if the operator password has not changed. Enable HTTPS if the Gizmo server uses it.

Add other branches migrates additional branches with service disabled. All registered branches, including disabled ones, are counted when paying for the subscription.

Enable service for the migrated club enables the selected branch after migration. If you leave it unchecked, the existing paid period is preserved, but service stays disabled. You can enable it later in the club settings.

Choose the database

Original database: keep history

Choose this when upgrading the existing Gizmo database. Player history, compatible settings, the floor plan, documents, website address and paid period are preserved.

Deleting users or products in Gizmo does not by itself mean that the database was replaced. If you are unsure where the database came from, establish this before migration.

Sections that need further setup remain disabled and are marked “Setup required” in the menu. You can configure them after migration. The old V2 battle pass is not migrated to V3. Historical rewards with an unknown outcome are not issued again.

Different database: configure the club again

Choose this only if the Gizmo database was actually replaced. The club’s feature settings, player history and progress, referral relationships and bookings in GGBook will be reset. The Gizmo database itself is not changed.

The owner account, documents, website address, paid period and floor plan drawing are preserved. Computers on the floor plan need reassignment. You will need to configure the club again.

A GGBook backup is created before the reset. Recovery requires support; there is no automatic undo. Do not choose a different database to bypass a failed check.

Start migration

  1. Click Check server. This check does not change data. Select the correct branch if needed.
  2. Review the result and confirm switching the club from GGBook V2 to V3. For the original database, confirm that the existing database was preserved. For a different database, confirm the reset and type ОЧИСТИТЬ.
  3. Click Migrate club or Clear data and migrate.

After confirmation, GGBook switches the club’s processing to V3. Do not restart V2 processing for the migrated club.

The page shows the current stage and progress. Once migration has started, you can close the page and return later. If migration is paused, check again using the same connection, branch and database choice. Contact support if you cannot continue.

Unfinished payments or data shared with other clubs may require a separate review. The message on the page explains the next step.

After migration

  • Check the connection and GGBook module in the server settings, then check the floor plan and club website.
  • Open sections marked “Setup required” and finish their setup. Enable the rules you need after checking them.
  • The existing paid period is preserved. Migration does not top up the new subscription balance.
  • The club website keeps its address and switches to V3 after every club linked to it has migrated. The website is temporarily unavailable until those migrations finish. Refresh the page; close and reopen an installed app.