Move to Java without wiping your players’ progress.
Keep inventories, XP, ender chests, and logout or respawn locations intact. Give your community a Java home without asking them to start over—or breaking the trust they placed in you.
No card required. Migration Check is a compatibility preview, not a free conversion.
Migration preview
reef-town.mcworld
18
players
0
failed
ZIP
ready
Plugin handoff
Restore inventories, XP, ender chests, and locations on first Java login.
Check
Preview what can move before you pay. A check is not a free conversion.
Preserve
Inventories, XP, ender chests, and player locations are extracted safely.
Migrate
Paid migration plans translate world geometry and validate the Java output.
Welcome back
Goldie restores each player’s progress when they arrive on Java.
Preserve progress with evidence, not hope
Built for admins who need to know what will move before they ask a community to leave Bedrock behind.
Observable, not opaque
Every run shows a live phase timeline, worker logs, and a per-entity skip summary. You see exactly what converted and what didn’t.
Safe-failure by design
An unmappable item or entity is dropped and logged — never a failed conversion. The migration report tells you precisely what was lost.
Java load-tested
Output is round-tripped through Mojang’s own DataFixerUpper plus structural assertions, calibrated against real Paper server loads.
Protect community trust
Players arrive on Java with the progress they earned instead of an empty inventory and a broken promise from their server admin.
Inventories follow your players home
The conversion extracts every player’s inventory, ender chest, XP and logout location into a
portable player_data.db.
A separate, open-source plugin restores it at runtime — so a Bedrock player who joins your
Java server lands with their gear intact.
World geometry is converted here. Player inventories and locations are restored at runtime by the separate, open-source plugin reading player_data.db.
- 1
Install the Goldie plugin
Drop Goldie.jar into your Paper/Spigot server plugins/ folder. Floodgate is an optional soft-dependency for automatic Geyser-mode restores.
- 2
Place player_data.db
Copy the player_data.db from this conversion into plugins/Goldie/. The plugin verifies its checksum on load.
- 3
Optional: place mappings.json
If you filled in Java player mappings on the conversion page, copy the downloaded mappings.json next to player_data.db. You can skip this and map later in-game.
- 4
Restore on join (Geyser mode)
Bedrock players joining via Geyser are matched by XUID and their inventory, ender chest, XP, and logout location are restored automatically — once per player.
- 5
Or map manually (Admin mode)
For Java accounts, run /goldie import <bedrock_gamertag> <java_player_name>. Works whether the player is online or offline.
Start with a free check
Preview compatibility, then choose the smallest paid rescue that fits.
Preview first
Migration Check · Free
Check a world up to 250 MiB before you pay, without creating a downloadable Java world or player-data package.
Small Realm Rescue
Bring a small realm to Java with inventories, XP, ender chests, and player locations ready to restore.
≤250 MB, ≤10 players
- Bedrock → Java world conversion
- Up to 250 MB upload
- Up to 10 player records
- Java world ZIP + player_data.db
Community Migration
The default rescue for a live SMP: preserve player progress and the trust your community placed in you.
≤5 GB, ≤50 players
- Everything in Small Realm
- Up to 5 GB upload
- Up to 50 player records
- Migration report + Tier-3 Java load validation
Large Server Migration
Move a large community with player progress intact and priority, dedicated migration capacity.
≤25 GB, ≤200 players; priority/dedicated queue
- Everything in Community Migration
- Up to 25 GB upload
- Up to 200 player records
- Priority dedicated queue
Ready to protect the progress your players earned?
Check the world first. Pay only when you choose a migration or player-data rescue path.