Why migrate?
Who should consider moving their server to Vital.sandbox and why
Overview
These guides are for developers running an active multiplayer server on an existing platform — primarily MTA, SA-MP, FiveM, or Roblox — who want to move their gamemode to Vital.sandbox.
Who should migrate
| Signal | What it means |
|---|---|
| Scripting limits | Your platform's language or threading model is blocking features you want to build |
| Plugin dependency | Core features like HTTP, database, and audio require third-party plugins to function |
| Renderer limitations | You want modern lighting, post-processing, or custom shaders beyond what the current engine supports |
| Asset pipeline | You want full control over asset formats and the import pipeline |
| Self-hosting | You want to own your infrastructure without a platform intermediary |
Who should not migrate
| Signal | What it means |
|---|---|
| Depends on base game assets | If your server relies on GTA SA/V's map, vehicles, peds, or interiors — those assets are not part of Vital.sandbox |
| Needs the platform audience | Roblox servers depend on the Roblox discovery engine, social graph, and storefront — these have no equivalent outside the platform |
| Wants a drop-in replacement | Vital.sandbox is a blank slate — there is no pre-loaded world, no built-in gamemode, and no compatibility layer |