Prepare a clean transfer package with the correct versions, dependencies, saves, resources, and database exports—without exposing credentials or relying on the only copy.
Replace sensitive values with obvious placeholders. Secure credentials can be rotated and arranged later through an approved channel.
Use these lists as a starting manifest. The final transfer path depends on archive size, sensitivity, current provider access, and downtime restrictions.
Include the exact Minecraft version and server software or mod loader. Client-only mods should not be mixed into a server pack unless the pack requires them.
Configure Minecraft hosting →Remove cache folders and never place Cfx.re keys, Tebex secrets, Discord tokens, or database passwords inside a public request.
Configure FiveM hosting →State the current map size, seed, plugin framework, and intended wipe behavior so the transfer can be staged responsibly.
Configure Rust hosting →Large save and cluster transfers may require a private transfer method arranged after review rather than an email attachment.
Configure ARK hosting →Keep the original save untouched until player ownership, guild data, and world loading have been confirmed on the destination.
Configure Palworld hosting →The matching world database and FWL files should travel together. Document crossplay and mod requirements before testing.
Configure Valheim hosting →List workshop content and plugin dependencies separately so missing or retired items can be identified before launch.
Configure CS2 hosting →Include file size, database use, framework or loader, required versions, and any downtime restrictions. Do not include credentials.
