Prepare and back up
Stop activity and back up Hub configuration, SQLite, tenant home, legacy workspace, and relevant company data.
Workspace migration
Migrate a Hermes Hub workspace safely by stopping tenant activity, taking verified backups, auditing links, running a dry run, and completing an atomic cutover with the legacy source retained for rollback. Company or team data must be migrated separately into the intended shared-storage boundary.
Treat migration as a verified data operation, not a directory move.
Stop activity and back up Hub configuration, SQLite, tenant home, legacy workspace, and relevant company data.
Reject symlinks that resolve outside the workspace and quarantine disposable links instead of weakening the check.
Use staged copying, checksums, permissions, and atomic installation while retaining the legacy source for rollback.
Review the documented command, dry-run behavior, verification, and rollback source.
Learn moreKeep private workspace and company storage as separate tenant-visible boundaries.
Learn moreConnect migration to runtime, storage, secrets, release, and recovery ownership.
Learn moreDiscuss a backup-first migration and the tenant and company storage boundaries it must preserve.
Architecture conversation
Share your deployment boundary, number of agents, work surfaces, and governance requirements. We will reply by email to arrange a focused technical discussion.
Email the Bewize teamThis opens your email application. Read our Privacy Policy.