How to Transfer a Minecraft Server to a New Host – Complete Guide 2026

Introduction

Transferring a Minecraft server to a new host is a critical task for server owners who want better performance, lower costs, or more control over their environment. A poorly handled migration can result in corrupted worlds, lost player data, or extended downtime. This guide explains how to transfer a Minecraft server to a new host safely in 2026, covering backups, file transfers, configuration, and testing. By following a structured process, you can move your server without losing worlds, plugins, mods, or player progress, while keeping downtime to a minimum.

Quick Summary Box

Always stop your server and create a full backup before migration
Transfer all server files using FTP or SFTP
Match the Minecraft version and server software on the new host
Reconfigure server.properties and accept the EULA
Test thoroughly before sharing the new IP or switching DNS

Understanding Minecraft Server Migration

Minecraft server migration is the process of moving your entire server environment from one hosting provider to another. This includes:

World data and dimensions
Player inventories, stats, and advancements
Plugins or mods and their configuration files
Server settings and permission lists

Java Edition servers store world data as region files, while Bedrock Edition uses a LevelDB database. Both formats can be transferred safely when the server is fully stopped and files are copied correctly.

Before migrating, review your server’s file structure so no critical folders are missed during transfer.

Preparing for Migration

Create a Complete Backup

Before touching any files, stop your server completely. A running server writes data continuously, which can corrupt files if copied mid-process.

Use the in-game console:

/save-all
/stop

Your backup should include everything in the server root directory, not just the world folder.

Essential files and folders include:

world, world_nether, world_the_end
plugins or mods folders
config folder (modded servers)
server.properties and eula.txt
ops.json, whitelist.json, banned-players.json, banned-ips.json

Download the backup to your local machine and store an extra copy in cloud storage for safety.

Verify Server Type and Requirements

Different server setups require different files:

Vanilla servers: world folders and server.properties
Plugin servers (Paper, Spigot): entire plugins directory
Modded servers (Forge, Fabric): mods, config, and matching server .jar

Check your world size. Worlds over 1 GB usually require SFTP instead of browser-based file managers due to upload limits.

Choose a Transfer Method

You can migrate your server using one of three approaches:

Host-assisted migration: Your new provider transfers files for you
Manual FTP/SFTP transfer: Download and upload files yourself
Compressed archive method: Zip all files, then upload and extract

Manual FTP or SFTP gives you full control and is the most reliable for large servers.

Step-by-Step Migration Process

Step 1: Stop Your Current Server

Ensure the server status shows “Stopped” or “Offline” before continuing. Forced shutdowns increase the risk of corrupted chunks and player data loss.

Step 2: Access Your Server Files

Connect to your current host using FTP or SFTP. You’ll need:

Server address or IP
FTP/SFTP username
Password
Port (21 for FTP, 22 for SFTP)

A client like FileZilla provides a split view of your local files and remote server files, making transfers easier.

Step 3: Download All Server Files

Select all files and folders in the server root directory.

You have two options:

Compression Method

Compress all files into a single .zip archive
Download the archive to your computer
Faster and more stable for large servers

Direct Download Method

Drag and drop folders to your local machine
Suitable for small servers
Slower for large worlds

Large servers may take 30 minutes to several hours depending on file size and internet speed.

Step 4: Set Up the New Host

Important checks:

Select the same Minecraft version as the old server
Choose the correct server software (Vanilla, Paper, Forge, etc.)
Allocate enough RAM and CPU resources

Once created, stop the new server immediately to prevent auto-generated files from overwriting your data.

Step 5: Upload Files to the New Host

Connect to the new host via FTP or SFTP.

Upload your compressed archive and extract it in the root directory
Or delete default files and upload your backup directly

Verify that folder names, file sizes, and structure match your original server exactly.

Step 6: Configure Server Settings

After uploading files, update these key settings:

Accept the EULA

Open eula.txt and change:

eula=false to eula=true

Verify server.properties

Check the following:

server-port (25565 for Java, 19132 for Bedrock)
level-name matches your world folder
online-mode=true (recommended)
max-players set correctly

Most hosts handle port forwarding automatically, but confirm your server listens on the correct port.

Step 7: Transfer Player Permissions and Lists

If all files were copied correctly, permissions and lists transfer automatically.

These files preserve access control:

ops.json
whitelist.json
banned-players.json
banned-ips.json

Open them in a text editor to ensure proper formatting. Corrupted JSON files can prevent server startup.

Step 8: Start and Test the Server

Start the server from your new host’s control panel and monitor the console.

A successful startup ends with:

“Done!”
A server load time message

Test by joining the server with the new IP:

Confirm inventory, XP, and location
Test commands and plugin features
Visit the Overworld, Nether, and End

Have a few trusted players test before announcing the migration publicly.

Step 9: Update DNS and Announce Migration

If you use a custom domain, update its DNS A record to the new IP. DNS propagation can take 1–48 hours.

During this time:

Keep the old server online as a fallback
Inform players about the new IP
Suggest clearing cached server entries if connection issues occur

Special Migration Scenarios

Migrating Large Servers (10GB+ Worlds)

For very large servers:

Use SFTP instead of FTP
Split archives into smaller parts if needed
Trim unused chunks before migration to reduce file size
Schedule migration during off-peak hours

Plugin and Mod Migration

For plugin servers:

Copy the entire /plugins folder, not just .jar files
Ensure each plugin’s configuration folder is present

For modded servers:

Match mod versions exactly on both client and server
Include mods and config directories

Java and Bedrock Considerations

Java and Bedrock servers use different formats and cannot be directly swapped. World conversion tools exist but may cause data loss. Plugins do not transfer between editions.

Tips, Common Mistakes, and Optimization

Common Mistakes to Avoid

Migrating without a verified backup
Forgetting plugin configuration folders
Running mismatched Minecraft versions
Not testing before going live

Post-Migration Optimization

After migration:

Reduce view distance if lag occurs
Verify correct RAM allocation
Schedule automatic restarts
Enable automated backups on the new host

Monitor TPS and server logs regularly to catch issues early.

FAQ Section

Can I transfer my Minecraft server without downtime?

Minimal downtime is possible by preparing the new server in advance and performing a final sync before switching IPs.

Will player inventories and achievements transfer?

Yes. Player data is stored in the world folder and transfers automatically if copied completely.

Do I need to reinstall plugins after migration?

No. Copy the entire plugins folder and configurations, and they load automatically.

Can I migrate between Java and Bedrock editions?

Not directly. The two editions use different formats and require conversion tools with limitations.

How long does a server migration take?

Most servers migrate in 30–90 minutes. Very large servers may take several hours.

Conclusion

Transferring a Minecraft server to a new host is a manageable process when done correctly. By creating reliable backups, transferring all files carefully, matching server versions, and testing thoroughly, you can migrate without losing worlds or player progress. Whether you’re upgrading hardware or changing providers, a structured migration ensures your community continues playing with minimal disruption.

Published by UpbeatUptake.com