Migrate from Fivemanage

Use the migration wizard: source Fivemanage, paste your Fivemanage API token, scan, import.

After the import, the switch-over is two lines in server.cfg — the wizard shows the exact diff:

ensure fmsdk
ensure spawnbase
set FIVEMANAGE_MEDIA_API_KEY "<your Spawnbase media token>"

Swap the resource folder, change the ensure line, and paste Spawnbase token values over the old ones (the SDK still reads the FIVEMANAGE_* convar names, and the API URL defaults to https://api.spawnbase.gg). Install the fmsdk shim resource as well and even your other scripts’ exports.fmsdk:… calls keep working with zero changes.

Coming from the Fivemanage v2 API instead? The same wizard applies; the old /api/v2/image shapes are read by the importer, you still end on /api/v1. Spawnbase also mounts /api/v3 as a compatibility alias, so unmodified v3 clients keep working during the move.

What doesn’t carry over: Fivemanage’s file API doesn’t expose a file’s original upload date, folder or retention-exempt flag — folders are recovered from the file’s public URL, imported files get the import date, and none are marked exempt. Log history is importable (per dataset — the wizard asks you to name your datasets, because Fivemanage can’t list them).