Migrating to Hubs Community Edition: what survives the move, and what you rebuild by hand
Description and use
Migrating to Hubs Community Edition preserves binary assets but requires manual recreation of rooms, accounts, and permissions. Effort scales with room count, not storage size.
Problem
When moving from the hosted Hubs service to a self‑hosted Hubs Community Edition deployment, binary assets such as scene GLBs, avatar GLBs and uploaded media transfer automatically, but all database‑backed state—rooms, links, accounts, permissions, moderation settings—does not. This forces a manual rebuild of every room and related configuration, which can be time‑consuming and disrupts existing URLs and user settings.
Outcome
The migration preserves all binary assets but requires manual recreation of rooms, accounts, permissions, and links. The effort scales with the number of rooms rather than storage size. Successful migration restores full functionality, but all old URLs become invalid and must be redistributed.
Workflow
- 1. Identify all binary assets (scene GLBs, avatar GLBs, uploaded media) and copy them to the new instance’s storage directory (e.g., using rsync).
- 2. Dump the current database (pg_dump) and restore it into the new instance’s Postgres, or start with a fresh database and plan to rebuild all relational data.
- 3. For each room: create a new room entry in the database, assign a short ID (optionally seed the ID to match the old one), set the scene binding, occupancy limit, permissions, and pinned objects.
- 4. Re‑create all user accounts, roles, and assign avatars. Upload any derived avatars after uploading their parent avatars.
- 5. Update any third‑party integrations (e.g., Dialog SFU, TURN servers) with new keys and endpoints.
- 6. Communicate new URLs to all stakeholders and update any embedded iframes or shared links.
- 7. Verify functionality by visiting each room, checking media, and ensuring permissions work as expected.
- 8. Monitor logs for any missing files or broken links and address them.
- 9. Archive the old database and storage for reference if needed.
- 10. Decommission the old hosted service once migration is confirmed.
- 11. Document the migration process for future reference.
Evidence
Binary assets survive because they are just files on disk: a published Spoke scene is a glTF 2.0 binary, a custom avatar is a .glb with a small set of texture overrides, and an uploaded image, PDF or video is the original file plus a generated thumbnail.
The database rows that turn those assets into a working room, the short room IDs, the permalinks, the accounts, the per room permissions and the moderation settings are all Reticulum state that a fresh deployment generates from scratch.
- Record date: 2026-09-07T09:31:51.395Z