[GH-ISSUE #5322] Migration guide from separate services to combined netbird-server #10321

Open
opened 2026-08-05 01:25:27 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @SuperKali on GitHub (Feb 14, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5322

Problem

I currently have a NetBird deployment with separate services:

  • netbird-management
  • netbird-signal
  • netbird-relay
  • netbird-coturn

I want to migrate to the combined netbird-server container for simpler management, but there's no migration guide available.

Why migrate to combined server

  • Simpler deployment and maintenance
  • Fewer containers to manage
  • Better alignment with official documentation
  • Easier upgrades

What's needed

A migration guide covering:

  1. Data backup: What data needs to be preserved (users, peers, configurations, keys)
  2. Configuration migration: How to convert separate management.json, signal.json, etc. into combined server config
  3. Database migration: How to migrate existing data to the new setup
  4. External IdP: How to maintain Zitadel/Keycloak/Auth0 integration
  5. Downtime strategy: Zero-downtime migration steps if possible
  6. Rollback procedure: How to revert if something goes wrong

Current environment

  • Deployment: Docker Compose with separate containers
  • External IdP: Zitadel
  • Reverse proxy: Traefik
  • Data: Active users and peers that must be preserved

Expected outcome

Successfully migrate to netbird-server without losing:

  • User accounts and permissions
  • Peer connections and configurations
  • Network policies and routes
  • Authentication integration

This would help users who started with separate services and want to simplify their deployment.

Originally created by @SuperKali on GitHub (Feb 14, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5322 ### Problem I currently have a NetBird deployment with **separate services**: - `netbird-management` - `netbird-signal` - `netbird-relay` - `netbird-coturn` I want to **migrate to the combined `netbird-server`** container for simpler management, but there's no migration guide available. ### Why migrate to combined server - Simpler deployment and maintenance - Fewer containers to manage - Better alignment with official documentation - Easier upgrades ### What's needed A migration guide covering: 1. **Data backup**: What data needs to be preserved (users, peers, configurations, keys) 2. **Configuration migration**: How to convert separate `management.json`, `signal.json`, etc. into combined server config 3. **Database migration**: How to migrate existing data to the new setup 4. **External IdP**: How to maintain Zitadel/Keycloak/Auth0 integration 5. **Downtime strategy**: Zero-downtime migration steps if possible 6. **Rollback procedure**: How to revert if something goes wrong ### Current environment - Deployment: Docker Compose with separate containers - External IdP: Zitadel - Reverse proxy: Traefik - Data: Active users and peers that must be preserved ### Expected outcome Successfully migrate to `netbird-server` without losing: - User accounts and permissions - Peer connections and configurations - Network policies and routes - Authentication integration This would help users who started with separate services and want to simplify their deployment.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#10321