Preview
Detect supported local GnBots profiles and their LDPlayer mappings. See the proposed configuration before any import.
THE GNBOTS CONFIGURATION MIGRATOR
Moving to a new bot shouldn’t mean starting from a blank page. VRA includes a configuration migrator for supported GnBots profiles and settings—with a preview before you commit.

Real development-build capture. Mapping totals describe that example installation—not a guarantee for every GnBots version or configuration.
A REVIEWABLE MOVE
The source is read, not rewritten. Importing settings does not uninstall GnBots, copy its program or replace your emulator data.
Detect supported local GnBots profiles and their LDPlayer mappings. See the proposed configuration before any import.
Create a local copy of allowlisted source configuration. Existing game and emulator data are outside the import.
Inspect supported options, proposed routines and exclusions. Unmapped settings are not silently treated as compatible.
Confirm the supported configuration copy. Review the resulting routines, then validate your environment before running farms.
SUPPORTED CONFIGURATION
Profile names and recognised LDPlayer instance mappings
Enabled action choices that have supported VRA counterparts
Supported task preferences and limits
Recognised schedule intervals, where the source format is supported
NOT A CLONE OR A COMPLETE TRANSFER
GnBots software, proprietary scripts, binaries and APKs are not copied
Licences, account globals, passwords and game logins are not imported
Custom rules, ambiguous fields and unsupported tasks require manual review
Android data and emulator profiles are not duplicated or replaced
A migration preview is not a successful automation run. The migrator and imported routines still need release validation. Compatibility varies by source version and configuration. You can review the workflow now and join the list for future testing.
CONSIDERING A SWITCH?
Make the comparison around the tasks you actually run—not an unverified performance claim.