Migrating to and within Grafana

Migrations into Grafana and between Grafana setups: legacy alerting and Angular plugins, imported alert rules, collectors, databases, platforms and consolidated instances.

Migrate legacy Grafana alerts to Grafana Alerting

Moving dashboard alerts and notification channels to Grafana Alerting on 10.4 before going to 11: preview versus simple upgrade, channels that do not convert, the clean_upgrade option and what rollback restores.

Replacing Angular panels and data sources in Grafana

Finding dashboards that still depend on AngularJS plugins, using the automatic migrations for Graph and Table-old, updating or replacing third-party plugins, and testing dashboards before Angular support disappears.

Migrate from Grafana Agent to Grafana Alloy

Replacing Grafana Agent Static with Alloy: alloy convert and its report, settings that do not convert, running a Static configuration directly as a stopgap, and the cutover order for fleets of hosts.

Migrate Grafana API keys to service accounts

Replacing legacy API keys used by scripts and CI with service accounts and tokens: per-organization scope, token expiry limits, the None role for least privilege and rotating tokens without downtime.

Migrate Grafana from a virtual machine to Kubernetes

Moving an existing Grafana from a VM to Kubernetes: externalizing the database first, persistent volumes and provisioning directories, plugins, ingress and root_url, and cutting over without breaking OAuth callbacks.

Consolidating multiple Grafana instances into one

Merging team-owned Grafana servers into one managed instance: organizations versus folders, moving dashboards and data sources with provisioning or the API, mapping users and teams, and retiring the old servers.

Talk to our team.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.

  • 30-minute call: free, with no obligation.
  • NDA on request: we can sign before you share details.
  • Clear next steps: a scope and plan after the call.