Migrate supported configuration from GnBots

What the migrator is for#

The migrator provides a head start by reading allowlisted configuration and proposing VRA farms, LDPlayer mappings, routine choices and supported settings. You review the proposal before import.

Compatibility varies by GnBots version and source configuration. A recognised setting is still translated into VRA’s own routine model; the product does not run another bot’s implementation.

What never transfers#

• GnBots binaries, APKs, proprietary scripts or executable automation.
• Licences, subscription status, account-wide secrets or third-party credentials.
• Game passwords, recovery information or unsupported custom rules.
• Android data or entire emulator profiles.
• A guarantee that an imported routine works without review and validation.

Safe migration process#

1. 1

   Preview

   Inspect detected profiles, mappings, supported values and exclusions.

2. 2

   Back up

   Allow the tool to create its documented configuration backup; keep your own emulator backup separately.

3. 3

   Dry run

   Review the proposed farms and routines without writing the destination configuration.

4. 4

   Import deliberately

   Confirm only after names, mappings, limits and exclusions make sense.

5. 5

   Validate one farm

   Run a minimal routine before assigning imported routines across the fleet.