Worlds · 12 min
Move a Bedrock world to a new device safely
Export, copy, import, and verify a Minecraft Bedrock world while preserving the original device copy and add-on requirements.
What you will accomplish
Export, copy, import, and verify a Minecraft Bedrock world while preserving the original device copy and add-on requirements. The goal is a repeatable result you can verify, not a pile of unexplained files.
- Original world preserved
- Export created
- New device import tested
- Add-ons checked
Bedrock transfer methods vary by device
The safest move keeps the original world untouched until the imported copy works. Some platforms allow direct world export, while others depend on cloud saves, Realms, file managers, or platform-specific backup tools.
This guide focuses on preserving the world and verifying add-ons rather than forcing one device-specific path.
Add-ons and resource packs matter
A Bedrock world may rely on behavior packs, resource packs, experiments, marketplace content, or device permissions. Confirm those requirements before deleting anything from the old device.
How to know you are finished
For move a bedrock world to a new device safely, the work is not finished when a file is merely downloaded. Treat it as finished when you can point to the setup you changed, explain why it matches the intended Minecraft version or platform, and repeat the result in a clean test or copied world.
Use the checklist as the exit test: old device copy still exists, transfer method chosen deliberately, world imported as a copy. If one of those checks is still uncertain, stop and verify that detail before moving to a main world, public server, or shared pack.
If the first failure you hit is "The world imports but add-ons are missing", start with this fix: Install or enable the required behavior and resource packs on the new device before opening the main copy again. This keeps recovery tied to the guide instead of turning into unrelated guesswork.
Step-by-step process
Back up original
Open the old device and make sure the world still loads before starting the transfer.
Choose transfer path
Create a backup or duplicate on the old device if the platform supports it.
Export if possible
Choose the safest transfer method available: export file, Realms upload/download, cloud sync, or platform file backup.
Copy safely
Move the exported world or backup without renaming random internal files.
Import new copy
Import or restore the world on the new device as a copy first.
Check packs
Check that behavior packs, resource packs, experiments, and marketplace dependencies are still enabled.
Verify gameplay
Enter the world and verify builds, inventory, spawn, dimensions, and add-on behavior before deleting the original.
Verification checklist
Old device copy still exists
Transfer method chosen deliberately
World imported as a copy
Behavior packs checked
Resource packs checked
Important world data verified
Troubleshooting
Install or enable the required behavior and resource packs on the new device before opening the main copy again.
Check whether the platform supports direct imports or needs Realms/cloud transfer instead.
Sign into the owning account and confirm the content is installed on the new device.
Practical notes
- Do not delete the old world until the new copy has been played and backed up.
- Realms can be useful as a temporary bridge between devices.
- Device storage permissions can block imports even when the file is valid.
Official-source standard
FreeMinecraftMods does not mirror project files. When this guide involves a download, verify the creator, version, loader, file availability, license, and final official source before installing anything.
Read how project listings are reviewed or report a correction.