Perses Grafana Migration

Convert Grafana dashboards to Perses format with validation and deployment.

Overview

This skill orchestrates a four-phase migration pipeline: EXPORT Grafana dashboards as JSON, CONVERT to Perses format, VALIDATE converted output and fix incompatibilities, then DEPLOY to a Perses instance.

Key constraints embedded in workflow:

• Always validate after conversion because percli migrate succeeds even when panels become StaticListVariable placeholders — zero errors does not mean zero data loss
• Preserve originals (never delete Grafana source files) because migration is one-way; originals are the rollback path
• Extract .dashboard key when exporting from Grafana API because the raw API response wraps the dashboard in metadata that percli migrate cannot parse
• Verify Grafana version is 9.0.0+ before migration because older versions use dashboard JSON schemas that percli does not support
• Use online mode when a Perses server is available because offline mode bundles outdated plugin migration logic; online uses the latest logic from the server

Instructions