New launcher. Same GoNuts history.

Before you start

A different launcher usually opens a different game folder. Copying only the GoNuts JAR can therefore look like a fresh installation.

Your original data may still be in the old launcher’s folder. Do not delete that instance, uninstall the old launcher or reset either database while checking.

Cloud diagnostics help investigate bug reports. They are not a backup or restore service for your complete local trading ledger.

1. Find both game folders

1. In the original launcher, select the exact installation you used and open its game folder. For the official launcher, check that installation’s Game Directory. The usual Windows default is %APPDATA%\.minecraft, but a custom directory takes precedence.
2. In Modrinth, MultiMC or your new launcher, open the destination profile’s folder. Use the game folder containing mods and config, not the launcher program folder.
3. Check the original folder for config/doughbay/doughbay.db. If it is missing, check other original instances and backups. A database in the new profile may be newly created and empty.

Hive or custom database? If the game folder contains gonuts-hive.json, or the configuration uses a custom databasePath, read the Hive section before copying. The active ledger may be elsewhere.

2. Stop safely and back up

1. Use GoNuts’ normal Stop control and let active work reach a supported safe checkpoint. Do not clear a recovery hold or uncertain trade.
2. Exit Minecraft normally in both launchers. Close every client sharing this ledger, including headless clients and Hive peers.
3. Make separate dated backup copies of the original and destination game folders before changing either. Keep the originals until verification is complete.

Never copy an open SQLite database. Copy the whole closed GoNuts data folder together. If doughbay.db-wal or doughbay.db-shm remains, preserve it with its matching database. Do not delete sidecars or mix files from different backups.

3. Transfer the standalone installation

These steps replace one installation for the same Minecraft account. Hive/custom-path users should use the next section.

1. If the destination already has config/doughbay, preserve it separately under a dated backup name while both games are closed. Do not merge the folders.
2. Copy the entire original config/doughbay folder into the destination’s config folder. The result should be NEW-GAME-FOLDER/config/doughbay/doughbay.db, not another nested doughbay/doughbay.
3. If present, copy gonuts-capital-history from the original game-folder root to preserve its local capital timeline.
4. For a replacement of this exact installation, preserve the root gonuts-dashboard and gonuts-community folders if present. They contain private installation credentials and retry state. Transfer them privately to your replacement only. Never upload them publicly, distribute them in a modpack or give them to another user.
5. Preserve config/gonuts-report-grouping.bin if present. This private report-grouping identifier is not a replacement for your database.
6. Use a compatible Minecraft/Fabric profile with GoNuts and its required dependencies. Keep one intended GoNuts JAR in mods.

This is a move, not a second running clone. Keep the original instance closed. To add another account or bot, use the supported Hive and account-linking setup instead of copying another installation’s credentials.

Hive and custom database paths

A Hive may store the active ledger and account configuration in a shared folder outside this game folder. gonuts-hive.json points to that location. A custom databasePath can also point outside config/doughbay.

Backing up only the instance may miss the active ledger. With every linked client closed, back up the actual shared/custom location too. Keep the original shared location available and use the supported Hive setup flow to connect the replacement profile. Do not create a new Hive over an empty ledger, combine histories by dragging files or edit database records.

If the shared folder must also move, get help before launching the replacement: every linked client needs a consistent location. A missing shared-folder error means restore access to that folder, not delete the Hive pointer and start with an empty database.

4. Verify before trading

1. Launch only the replacement profile, signed into the same Minecraft account.
2. Open GoNuts and compare purchases, owned positions, history and settings with your original backup. Check the intended account and Hive are shown.
3. Check spending limits and recovery state. Let native reconciliation verify current inventory, listings and order ownership. Old ledger entries alone do not prove current server state. Never reset exposure or manually mark uncertain trades complete.
4. Check dashboard and Swarm linking. If you did not transfer credentials, use the normal linking flow. Signing into the same Discord account does not restore the local ledger.
5. Resume deliberately only when the expected data and native readiness checks agree. Keep the backup.

Comparing database file sizes and hashes before launching can confirm an ordinary copy matched. The files change when the replacement opens them, so later differences do not by themselves mean the transfer failed.

Already opened the new launcher and history is empty?

1. Stop GoNuts, close the new game normally and back up that profile too.
2. Find and preserve the original launcher’s game folder and its actual database location, including Hive/custom paths. Opening a new profile does not by itself delete the old one.
3. If the new profile has not traded, follow the closed-folder transfer steps above while preserving its new files separately.
4. If both profiles made trades, do not overwrite or merge either database. Ask for help reconciling their different histories and owned-position records before running either bot again.

If the original files were deleted, check backups and operating-system restore/recycle options. Recovery is not guaranteed. Cloud diagnostics, a settings code and an empty replacement database cannot reconstruct all lost trading history.

For support, describe the original/new launchers, whether the original folder exists, whether Hive is enabled and whether either profile traded after the move. Do not post databases, credentials or raw configuration publicly.