org-wide-secret-migration

Migrate secrets across a GitHub organization by generating a plan with gh secret-kit migrate plan, reviewing the script, starting a central org-level runner, and executing the script to complete the full migration.

Yes, you can migrate GitHub environments and deploy keys along with secrets and variables. The migration process handles differences across hosts and environments, moving deploy keys and environments where applicable.

The best way to verify secrets after an org migration is to use the gh secret-kit migrate check command, which ensures all secrets and variables are present at the destination organization.

Cross-host secret migration works for enterprise GitHub deployments by handling differences across hosts and environments, supporting multi-repo migrations across source and destination organizations.

Yes, you need to run a central org-level runner to coordinate jobs across repositories. Start the runner after generating the migration plan, then execute the script to complete the automated migration.

Manual secret migration across organizations leads to errors due to manual, error-prone reconfiguration when changing orgs or consolidating security boundaries across multiple repositories and environments.