Preview
Detect supported local GnBots profiles and their LDPlayer mappings. See the proposal before any import.
AUDITABLE GNBOTS CONFIGURATION MIGRATION
Having an importer is not the differentiator. Showing recognised mappings, unsupported fields and the proposed destination before any write is. Nothing is silently treated as compatible.

Real development-build capture. Mapping totals describe that example installation—not every GnBots version or configuration.
A REVIEWABLE MOVE
The source is read, not rewritten. Import does not uninstall GnBots, copy its program or replace emulator data.
Detect supported local GnBots profiles and their LDPlayer mappings. See the proposal before any import.
Create a local copy of allowlisted source configuration. Game and emulator data remain outside the import.
Inspect supported options, proposed routines and exclusions. Ambiguous fields require review.
Confirm the supported configuration copy, review resulting routines and validate one farm.
SUPPORTED CONFIGURATION
Profile names and recognised LDPlayer mappings
Enabled actions with supported VRA counterparts
Supported customer preferences and limits
Recognised schedule intervals where the source format is supported
NOT A CLONE OR 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 need review
Android data and emulator profiles are not duplicated or replaced
A migration preview is evidence—not a successful automation run. Imported routines still need customer review and one-farm validation. Compatibility varies by source version and configuration.
AFTER THE IMPORT
Inspect active catalogue status, assign a small routine and use VRA Evidence to confirm what the first farm actually did.