This article provides general preparation guidance. Final service recommendations depend on the actual software, data, licensing, integrations, and operating requirements involved.
Never upload the only copy
Create a separate transfer copy and retain an untouched local backup. A migration package should never become the sole remaining copy of a world, database, resource stack, or website.
Remove secrets and temporary data
Delete caches, crash dumps, temporary files, and unrelated old backups. Replace passwords, private keys, tokens, license keys, and database credentials with placeholders before sharing files for review.
Document versions and dependencies
Include the exact game version, framework, loader, plugin or mod dependencies, startup requirements, database engine, and external services. A clean manifest often prevents more migration problems than a larger archive.
Use the transfer method approved for the project
Public quote and contact forms are not file-upload systems. After a request is approved, OutlawCoreStudios will identify an appropriate private transfer method based on size, sensitivity, and service requirements.
Never place passwords, private tokens, recovery codes, API keys, database credentials, or license keys into a public form or unverified message.