--- title: Transfer your Valheim Server to Nodecraft description: Bring your existing Valheim world to Nodecraft without starting over. This guide explains how to find your .db and .fwl world files, upload them to the correct worlds_local folder, set the matching World Name, and troubleshoot common transfer issues. source: "https://nodecraft.com/support/games/valheim/transfer-your-valheim-server-to-nodecraft" image: "https://dynamic-assets.nodecraft.com/signedurl/w7vokBAexMnVlnMZ1Q/image.jpg?modifications=W3sibmFtZSI6ImdhbWVfYmciLCJpbWFnZV91cmwiOiJodHRwczovL2Ntcy1hLm5vZGVjcmFmdC5jb20vZi8xMzM5MzIvMjAwMHg1NTAvZjY2ZTY0Y2JjNS92YWxoZWltLTEtMi0wLnBuZy9tLyJ9LHsibmFtZSI6ImdhbWVfbG9nbyIsImltYWdlX3VybCI6Imh0dHBzOi8vY21zLWEubm9kZWNyYWZ0LmNvbS9mLzEzMzkzMi8zNzV4MTUwL2MwZGEwNmUzMzAvdmFsaGVpbS5wbmcvbS8ifSx7Im5hbWUiOiJjdGFfdGV4dCIsInRleHQiOiJDcmVhdGUgeW91ciBvd24gc2VydmVyISJ9LHsibmFtZSI6InRleHQiLCJ0ZXh0IjoiVHJhbnNmZXIgeW91ciBWYWxoZWltIFNlcnZlciB0byBOb2RlY3JhZnQifV0&s=1c8154ffd4006fbf71c1a4f48c8fb98338e4015b8f7646c10a0f7fb28550d847" published: "2026-09-01T03:07:42.752Z" updated: "2026-09-01T03:07:42.752Z" --- # Transfer your Valheim Server to Nodecraft Bring your existing Valheim world to Nodecraft without starting over. This guide explains how to find your .db and .fwl world files, upload them to the correct worlds_local folder, set the matching World Name, and troubleshoot common transfer issues. Already have an existing Valheim server and want to bring it over to Nodecraft? You don't have to start over. If you have a copy of your previous Valheim server files saved on your computer, you can transfer your existing world to your new Nodecraft server and continue playing with your builds, exploration, and world progress intact. This guide walks through the entire process, from identifying the files you need to uploading them to Nodecraft and getting your existing world running. ## Before You Begin Before making any changes to your new Nodecraft server, make sure you have a complete copy of your existing Valheim server files saved somewhere safe on your computer. If your files came from another hosting provider, you may have downloaded them as a ZIP file or as an entire server directory. Either is fine. Keep the original copy of your server files as a backup until you've confirmed that everything is working correctly on Nodecraft. You won't necessarily need to upload every file from your old server, so having an untouched backup gives you something to return to if you need another file later. ## Find Your Valheim World Files The most important part of your transfer is your world save. Valheim worlds use two primary files with matching names: - YourWorld.db - YourWorld.fwl For example, if your world is named MyValheimWorld, you should have both MyValheimWorld.db and MyValheimWorld.fwl. The .db file contains most of the world data, while the .fwl file contains information Valheim uses to identify the world. You will need both files for the transfer. Depending on your previous setup, you may also see files such as MyValheimWorld.db.old and MyValheimWorld.fwl.old. These are backup copies of the world and are worth keeping, but the active .db and .fwl files are the ones you'll normally use first. Important: Make sure the .db and .fwl files have the exact same world name. Don't mix files from different saves. If you downloaded an entire server backup and aren't sure where the world is located, look for a folder named worlds\_local. You can also search your backup for .fwl or .db files to help find the correct save. ## Prepare Your World Files Once you've found the correct .db and .fwl files, place them together in a folder on your computer. You can also include their matching .old backup files if you'd like to keep those with the server. Compress the files into a .zip file before uploading them. For example, you might create a file named MyValheimWorld.zip. Using a ZIP keeps the files together and makes the transfer easier. Avoid placing the files several folders deep before creating the ZIP. Once the ZIP is extracted on Nodecraft, the .db and .fwl files need to be directly inside Valheim's worlds\_local folder. ## Open Your Nodecraft Valheim Server 1. Navigate to your Nodecraft dashboard. 2. Locate your Valheim server and click **Manage**. 3. Stop the server. 4. Click **Server Files** in the menu on the left. ![Dark admin sidebar; Server Files highlighted with Files, SFTP, Installer; includes Backups, Automated Tasks, Manage Instance with Manage and Users.](https://cms-a.nodecraft.com/f/133932/269x585/16c831aff6/valheim-server-files-menu.png/m/) Keeping the server stopped while uploading or replacing save files prevents Valheim from writing to the world directory while you're making changes. ## Navigate to the Valheim World Folder In Server Files, navigate to: /.config/unity3d/IronGate/Valheim/worlds\_local ![Dark file manager UI with a left folder tree and right file list; includes Upload (green), New Folder and New File (blue); shows files like world.db](https://cms-a.nodecraft.com/f/133932/997x735/5b0ab87f6a/valheim-upload-world-files.png/m/) You may already see world files in this folder from a world created by the new server. That's okay. You don't need to use that world if you're transferring an existing one. ## Upload Your Existing World While inside /.config/unity3d/IronGate/Valheim/worlds\_local, upload the ZIP file containing your world. Once the upload finishes, select the ZIP file and click **Unzip**. ![Dark file manager interface with left folder tree and right file list; UnZip button highlighted; world.zip selected.](https://cms-a.nodecraft.com/f/133932/1003x734/402215611d/valheim-unzip-world-files.png/m/1000x0/smart) After extracting the ZIP, confirm that your .db and .fwl files are directly inside the worlds\_local folder. For example: /.config/unity3d/IronGate/Valheim/worlds\_local/MyValheimWorld.db /.config/unity3d/IronGate/Valheim/worlds\_local/MyValheimWorld.fwl Make sure the ZIP didn't create an extra folder during extraction. For example, you don't want your files stored at worlds\_local/MyValheimWorld/MyValheimWorld.db. If an extra folder was created, move the .db and .fwl files directly into worlds\_local. ## Set the World Name Uploading the files gets the world onto your server, but you still need to tell Valheim which world it should load. 1. Click **Game Settings** in the menu on the left. 2. Locate **World Name**. 3. Enter the exact name of your uploaded world without the file extension. For example, if your files are MyValheimWorld.db and MyValheimWorld.fwl, enter MyValheimWorld as the World Name. ![Dark settings panel showing World Name with a text field displaying 'world' under the subtitle World file used for storage.](https://cms-a.nodecraft.com/f/133932/673x122/e73b195f70/valheim-world-name-setting.png/m/) Save your changes when finished. ## Review Your Server Settings Your world files contain your existing Valheim world, but they don't necessarily include all of the settings from your previous hosting provider. Before starting the server, review your **Game Settings** and configure options such as your server name, password, crossplay settings, and any other Valheim settings you were previously using. Don't assume that settings from your previous host will automatically transfer with the world save. ## What About the Rest of My Server Files? If you downloaded a complete backup of your previous Valheim server, you'll probably have far more files than just the .db and .fwl world files. In most cases, you shouldn't upload the entire old installation over your Nodecraft server. Nodecraft handles the Valheim server installation for you, so start by transferring the data you actually need. For a standard unmodded server, this is primarily your world save and your server settings. If your previous server used mods, however, there may be additional files you'll need to transfer or reinstall. ## Transferring a Modded Valheim Server If your old server used BepInEx plugins or other Valheim mods, transferring the world will not automatically reinstall those mods. You'll need to set up the required mod framework on your Nodecraft server and install the same server-side mods your previous server used. BepInEx plugins are commonly stored in: /BepInEx/plugins If your old server backup contains plugin .dll files, use those files to help identify which mods were installed. However, avoid replacing your entire new BepInEx installation with an old copy without checking it first. Valheim, BepInEx, and individual mods can change between versions, so reinstalling the framework and then adding the required plugins can help prevent outdated files from causing issues. Some mods may also use configuration files or additional dependencies. Check the installation instructions for each mod before transferring those files. If players needed client-side mods to join the previous server, they'll generally still need the appropriate versions installed on their own computers. ## Start Your Valheim Server Once you've uploaded the .db and .fwl files, confirmed they're directly inside worlds\_local, set the correct World Name, reviewed your server settings, and installed any required mods, start the server. Give Valheim a moment to finish loading before trying to connect. Once the server is online, join it and visit an area you're familiar with. Check for existing buildings, explored areas, terraforming, boss progression, and other changes you recognize from the old server. If everything looks familiar, your world transfer was successful! ## The Server Generated a New World Instead If you connect and find yourself in a completely new world, stop the server before making additional changes. Your uploaded world files are usually still there, but Valheim may not be loading them correctly. First, check Game Settings and make sure World Name exactly matches your uploaded files. If the files are named VikingAdventure.db and VikingAdventure.fwl, the World Name should be VikingAdventure. Next, confirm that both the .db and .fwl files are present and directly inside /.config/unity3d/IronGate/Valheim/worlds\_local. Also check that extracting the ZIP didn't place them inside an additional folder. If everything appears correct and the server still loads the wrong world, compare the uploaded files with your original backup to make sure you transferred the intended save. ## The Server Won't Start After the Transfer If the server won't start after uploading your files, check the server console for errors. If you're transferring a modded server, an outdated plugin, missing dependency, or incompatible mod version may be preventing the server from starting. If needed, try starting the server with the transferred world but without the old mods. Once you've confirmed that the world itself works, you can add your mods and configuration files back one at a time. ## Keep Your Original Backup Don't delete your original server files as soon as the new server starts. Keep the backup until you've played on your Nodecraft server and confirmed that your world, settings, and any required mods are working correctly. Having the original files available gives you something to fall back on if you uploaded the wrong save, need one of the .old backups, or discover that you're missing a configuration or mod file. ## Final Thoughts Moving an existing Valheim server to Nodecraft can look intimidating when you have an entire folder of server files sitting on your computer, but you usually don't need to replace the entire installation. Start with the most important pieces: your matching .db and .fwl world files. Once those files are uploaded to the correct folder and your **World Name** matches the save, you can start the server and confirm that your world made the trip safely. From there, review your server settings and reinstall any mods or additional configuration you need, and you'll be ready to continue exploring the Tenth World without starting over.