Observação
Enterprise Live Migrations is in beta and subject to change.
If your migration encounters a problem, check the migration status with elm migration status --migration-id MIGRATION-ID and review the error information.
Statuses and recommended actions
| Status | Meaning | Recommended action |
|---|---|---|
| Created | The migration has been created but not yet started | Run elm migration start |
| Queued | The migration is waiting to start | Wait |
| Exporting | Data is being exported from the source | Monitor with elm migration status |
| Processing | Exported data is being imported to the destination | Monitor with elm migration status |
| Ready for cutover | The initial migration is complete and the migration is ready for cutover | When ready, run elm migration cutover-to-destination |
| Cutting over | The source repository is locked and remaining changes are being applied to the destination | Monitor; the status will transition to Completed |
| Completed | The migration has finished successfully | Verify the destination repository and reclaim mannequins |
| Failed | The migration encountered an unrecoverable failure | Investigate the error (see below) |
| Paused | The migration is paused | Resume the migration |
| Terminated | The migration was cancelled | N/A |
| Degraded | The destination is unreachable | Check network connectivity between the GitHub Enterprise Server appliance and GHE.com (see below) |
Migration status is "Failed"
A migration enters the Failed status when an unrecoverable error prevents it from continuing. This is distinct from individual resources failing to import—a failed migration means the migration itself cannot proceed.
To investigate, run elm migration status --migration-id MIGRATION-ID and review the error details in the response. Each failure includes a correlation ID in the format (Correlation ID for Support: UUID). If you contact Suporte do GitHub, provide this ID so the support team can investigate.
After resolving the underlying issue, abort the failed migration with elm migration cancel --migration-id MIGRATION-ID and start a new migration.
Migration status is "Degraded"
A Degraded status means the migration service on the GitHub Enterprise Server appliance cannot reach the destination enterprise. The migration continues on the source side, but the destination status is unknown.
Check network connectivity between the GitHub Enterprise Server appliance and your subdomain of GHE.com, then run elm migration status --migration-id MIGRATION-ID again. The status response includes a timestamp for the last successful contact with the destination, which can help you assess how long the connectivity issue has been occurring.
Some resources failed to import
Individual resources can fail to import without causing the overall migration to fail. You can see a count of failed resources in the output of elm migration status --migration-id MIGRATION-ID.
Failed resources are only shown after all automatic retries have been exhausted, so any failures you see are confirmed as unresolvable without intervention. Review the error details in the status response: each failed resource in backfill or live updates will display "state": "failed".
If the number and types of failed resources are acceptable, you can proceed with cutover. If not, abort the migration, resolve the underlying issue, then start a new migration.
Cutover failed and the source repository is locked
If a cutover fails partway through, the source repository may remain locked or archived. This prevents developers from pushing to the source while the destination may still be incomplete.
To unlock the source repository, a site administrator must unlock it from the GitHub Enterprise Server Console de Gerenciamento.
After the source is unlocked, you can either retry cutover using elm migration cutover-to-destination --migration-id MIGRATION-ID, or abort the migration with elm migration cancel --migration-id MIGRATION-ID and start a new migration when you're ready.
Migration must be restarted due to a force push
If someone force-pushes to the default branch of the source repository while a migration is in progress, the Git synchronization between the source and destination breaks. Force pushes rewrite commit history in a way that cannot be reconciled incrementally.
If this happens, abort the migration with elm migration cancel --migration-id MIGRATION-ID and start a new migration. Before restarting, communicate to your team that force pushes to the default branch are not permitted while a migration is active.
Access token was rejected
If your migration fails with an authentication error, check that:
- Both the source and destination tokens are personal access tokens (classic). Fine-grained tokens are not supported.
- The tokens have the scopes specified in Migrating your repository with Enterprise Live Migrations.
- If the destination organization enforces SAML single sign-on, the token must be authorized for SSO.
The source GHES URL was rejected
Enterprise Live Migrations requires the GitHub Enterprise Server URL to use HTTPS. If the URL is configured with HTTP, the migration will fail preflight validation.