Back up and stop activity
Back up Hub configuration, databases, tenant homes, legacy workspaces, and relevant company data before copying.
Workspace migration
How do I migrate company data into a private Hermes Hub workspace?
Migrate company data into a private Hermes Hub workspace with a backup-first process: stop tenant activity, audit links and destinations, stage the copy inside the tenant home, verify files and permissions, then atomically install the private workspace while retaining the legacy source for rollback. Company or team storage is migrated separately from tenant workspace data.
Migration checkpoints
The documented flow emphasizes verification and separation.
Validate the workspace
Audit symlinks, reject links outside the workspace, verify the destination, and quarantine unsafe developer-machine links.
Verify and cut over
Check file hashes, entry kinds, permissions, and symlink targets before atomic installation and rollback retention.
Workspace migration FAQ
Does installing Hermes Hub migrate legacy data automatically?
No. Workspace migration is an explicit operation for selected tenants or a documented scan of legacy workspace directories.
How is company data different from tenant workspace data?
Company and team content is migrated separately into dedicated company storage, with team-relative paths and intended share-group access controls.
What happens to the legacy source?
The documented migrator retains the legacy source for rollback after verifying and atomically installing the staged private workspace.
Plan workspace migration
Discuss backups, tenant selection, symlink checks, company storage, permissions, verification, and rollback.
Architecture conversation
Tell us what your team needs to control
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.