Change Minecraft versions with a backup and rollback plan

Your Minecraft server version affects world data, plugins, mods and which players can connect. Decide whether you need a newer server, a different server type or just client compatibility before changing files. Keep the working installation intact until a separate test succeeds.

Record the working setup

In the game panel, check Console and Startup. Record the exact Minecraft version, server software, Java runtime and JAR filename. Include proxy, Geyser, plugin and mod versions if you use them. A label such as “latest” is not a reproducible rollback target.

Check the new release's requirements on the server project's official site. Review plugin and mod authors' supported versions too. A plugin working on one Paper release does not prove it works on another, and a modded server may require a matching client pack.

Make a recoverable copy before the change

Announce downtime, stop the server and wait for the save to finish.
Take a complete file backup, including all world and dimension folders, server settings, plugins or mods and their data.
Export any external plugin databases while writes remain stopped. Keep the database export paired with the file backup.
Save a copy outside the server and verify that you can open the archive. Note its timestamp and original versions.
Test on a separate server or isolated copy when possible. Do not let both copies write to the same production database.

Use the backup guide before proceeding. A backup entry that still says pending is not a confirmed recovery point.

Choose the kind of change

For a newer Paper or Purpur version, follow the safe-update guide. Stop before replacing the running server JAR. Select a supported Java runtime using the Java guide, and check the startup filename against the uploaded file.

Switching from Paper to a mod loader changes more than a version number. Review the loader's requirements and world compatibility before using the existing world. Do not run a reinstall or replace folders as an experiment on your only copy.

If players use a different client release, first test with the exact matching release. Protocol-compatibility plugins can help specific supported combinations, but they do not add newer blocks or gameplay to an older server. Check the plugin's compatibility table rather than assuming it supports every client.

Do not force a world downgrade

Loading an existing world in a newer server can upgrade its data before anyone joins. Starting an older JAR afterward does not reverse that conversion. Paper does not support world downgrades. Do not bypass world-version checks to force an older release to load newer data.

To return to an earlier release, restore the complete backup from before the upgrade alongside its matching server software, configuration and database state. Changes made since that backup will need separate consideration. Stop and ask support if you have no compatible recovery copy.

Verify before reopening

Read startup logs, then test login, inventories, permissions, plugins, multiple dimensions and known builds. Check a stop/start cycle during the window. Send the relevant logs and exact old/new versions if a test fails; keep players out while investigating.

Further reading: Paper updates; Paper world-version errors; Paper runtime requirements.