Moving dashboards and users onto Superset from other open-source BI tools, and moving existing Superset deployments between platforms, databases and instances.
Moving a Helm-based Superset to the Superset custom resource: external PostgreSQL and Redis or Valkey, long-lived secrets, config overrides, lifecycle tasks on first reconcile, routing changes and removing the Helm release last.
Moving from Metabase to Superset: what transfers and what is rebuilt, mapping questions and models to datasets and charts, permissions and groups to roles and RLS, embedding changes and a parallel-run plan.
Replacing Redash with Superset: moving saved queries into SQL Lab and virtual datasets, rebuilding visualizations and dashboards, data source connections, alerts and user access.
Leaving SQLite or a Docker Compose PostgreSQL container for a managed PostgreSQL metadata database: export and import versus database copy, encryption with SECRET_KEY, downtime and verification.
Moving a Compose-based Superset to Kubernetes with the operator: building your own image, externalizing the metadata database and cache, Celery workers and beat, ingress and a cutover with no lost dashboards.
Promoting dashboards, charts and datasets from development to production Superset with ZIP export and import: UUIDs, overwrite behavior, database connection passwords and dataset file naming since 6.0.
Merging departmental Superset instances after reorganizations or acquisitions: inventorying assets, UUID conflicts, role and RLS redesign, database connection consolidation and user migration.
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.