Workspace migration

How do I migrate a Hermes Hub workspace safely?

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.

Backup-first migration sequence

Treat migration as a verified data operation, not a directory move.

Prepare and back up

Stop activity and back up Hub configuration, SQLite, tenant home, legacy workspace, and relevant company data.

Audit boundaries

Reject symlinks that resolve outside the workspace and quarantine disposable links instead of weakening the check.

Verify cutover

Use staged copying, checksums, permissions, and atomic installation while retaining the legacy source for rollback.

Migration references

Hermes Hub workspace migration FAQ

Should company data be copied with the tenant workspace?
No. Migrate shared company or team content separately into the dedicated company storage tree and preserve its intended access controls.
What happens if the destination already conflicts?
A conflicting real destination should be refused rather than overwritten. A matching prior migration can be recognized as already migrated.
Why retain the legacy source?
Retaining the legacy source provides a rollback reference while the new private workspace and permissions are verified.

Plan a workspace migration

Discuss a backup-first migration and the tenant and company storage boundaries it must preserve.

+1 332 2081410
[email protected]

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 team

This opens your email application. Read our Privacy Policy.