Migrate a Minecraft Server to Paper: From Vanilla, Fabric, Forge or Spigot
Moving a server to Paper is mostly a jar swap, but only from some starting points. Paper's own migration documentation separates the cases clearly: vanilla to Paper is supported, Spigot or CraftBukkit to Paper goes through vanilla first, and a modded server cannot be migrated in place because Paper does not load mod content.
This guide follows that documentation, checked on 2026-11-17. The world folder layout changed in Minecraft 26.1, and older guides describe the previous layout, which Paper now calls outdated and unsupported. If a step here disagrees with what you see on your server, trust the version you are actually running and ask support before moving files. For background on the server types, read Paper vs Spigot vs Purpur vs Vanilla.
- Back up first, using the Whole server option on the Backups tab so the plugin and config folders are included.
- Vanilla to Paper: swap the server software. Paper converts the world storage automatically.
- Fabric or Forge to Paper: not possible in place. Paper cannot load mod content, and Paper describes hybrid servers as fundamentally flawed and not recommended.
- Spigot or CraftBukkit to Paper: Paper says this is fundamentally impossible directly from 26.1. Migrate to vanilla first.
- Paper to vanilla needs a few world data files moved before you swap the jar. Paper to Spigot or CraftBukkit is unsupported and risks data loss.
On this page
Pick your starting point
| Coming from | Going to Paper | What Paper's documentation says |
|---|---|---|
| Vanilla | Supported | Swap the server software. World storage is converted automatically. Going back later needs the vanilla migration steps below. |
| Fabric or Forge | Not in place | Paper cannot load mod content. Hybrid servers are described as fundamentally flawed and not recommended. |
| Spigot or CraftBukkit | Via vanilla | Described as fundamentally impossible directly as of 26.1. Migrate to vanilla first, then to Paper. |
| Paper | Going back to vanilla | Possible with a few data files moved first (steps below). |
| Paper | Going to Spigot or CraftBukkit | Unsupported, with a risk of data loss. |
The modded case is worth reading twice. A Fabric or Forge world contains blocks, items and entities that only exist because of those mods, and Paper has no way to load them. If your players want mods, stay on a mod loader. If they want plugins and better performance, Paper fits, and the two are separate paths. See installing Forge and Fabric mods and installing plugins on Paper.
Before you change anything
- Take a full backup
On the Backups tab choose Back up now and pick Whole server. Paper's documentation says to back up before migrating. Click the star to keep it so automatic cleanup never removes it.
- Download a copy as well
If the world matters to you, download the world folder from the Files tab as a second copy. The method is in the SFTP guide.
- Note your current version
Write down the Minecraft version the world was last played on. Paper cannot open a world saved by a newer Minecraft version than it supports, and downgrading is not supported.
- Tell your players
The first start after a migration can take longer while the world is converted, so choose a quiet time.
A general walk-through of backups is in the Minecraft backup and restore guide.
Vanilla to Paper
This is the simple case. The world stays where it is, and Paper converts the world storage on its first start.
- Stop the server
Use Stop on the Console tab and wait until it is fully offline. Never swap server software while it runs.
- Switch the server software to Paper
On ChicagoServers the server software is managed by the panel. Check the Startup tab for a server type or version field, and if you cannot find one, contact support and ask for Paper on your Minecraft version. The launch line itself is staff-only.
- Start and watch the Console
Start the server and read the Console tab for conversion messages and errors. Join and check your builds, chests and spawn.
- Keep the backup
Keep the starred pre-migration backup for a few days so you can compare or roll back.
Fabric or Forge to Paper
There is no in-place route. Paper's documentation says it cannot load mod content, and recommends against hybrid servers, meaning projects that try to run mods and plugins together. A hybrid is a separate decision from a migration, and Paper's position is that it is not recommended.
If you still want Paper, the honest options are to start a new Paper world, or to take your world to vanilla only if it contains no modded content. Worlds that used modded blocks or items will not load cleanly without those mods, so do not assume the world survives. Make the decision on a copy and keep the backup.
Spigot or CraftBukkit to Paper
Paper's documentation says a direct migration from Spigot or CraftBukkit to Paper is fundamentally impossible as of 26.1, and tells you to migrate to vanilla first. Plan it as two steps: Spigot or CraftBukkit to vanilla, then vanilla to Paper, taking a backup before each step. Plugins are separate files, so keep your plugins folder out of the way during the vanilla step and check each plugin for compatibility afterwards.
Paper back to vanilla
The documented process for current versions, assuming level-name is world in server.properties, is to move five data files before you swap the jar. Paper stores them in the overworld dimension folder, and vanilla expects them in the top-level data folder.
From: world/dimensions/minecraft/overworld/data/minecraft/
To: world/data/minecraft/
Files to move:
game_rules.dat
scheduled_events.dat
wandering_trader.dat
weather.dat
world_gen_settings.dat- Stop the server and take a Whole server backup first.
- Do the move on the Files tab, then switch the server software back to vanilla.
- If your world folder has a different name, use that name in place of
world. - Check the layout on your own server before moving anything. If the folders above do not exist, you are on a different layout and these steps do not apply.
After the migration
- Open the Console tab and read the first start from top to bottom. Warnings about plugins are separate from the world conversion.
- Check
server.propertiesafter the swap. See the server.properties guide. - Paper creates its own configuration files. Paper's migration page does not cover them, so see the global config guide and the world config guide before changing values.
- If the server will not start, work through the won't-start fixes and restore the backup rather than forcing the world open.
Frequently asked questions
Can I move a Fabric or Forge server to Paper?
Not in place. Paper's documentation says it cannot load mod content, and it describes hybrid servers as fundamentally flawed and not recommended. Worlds that contain modded blocks or items will not load correctly without the mods.
Will my vanilla world work on Paper?
Yes. Paper's documentation says to swap the server software and that world storage is converted automatically. Back up first, because going back to vanilla afterwards needs extra steps.
Can I go from Spigot straight to Paper?
Paper says this is fundamentally impossible directly as of 26.1 and recommends migrating to vanilla first, then to Paper. Take a backup before each step.
Can I switch from Paper back to vanilla?
Yes. Paper documents moving game_rules.dat, scheduled_events.dat, wandering_trader.dat, weather.dat and world_gen_settings.dat from the overworld dimension data folder into world/data/minecraft/ before swapping the jar, assuming the world is named world. Going from Paper to Spigot or CraftBukkit is unsupported and risks data loss.
Do I lose my plugins when I migrate?
Plugins are separate jar files and configuration folders, so they are not part of the world. Whether each one works on your new server type depends on that plugin, so check them one at a time after the move.