docs/content/admin/configuring-packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md

title	intro	product	permissions	versions	shortTitle	topics	redirect_from
Migrating your enterprise to the Container registry from the Docker registry	You can migrate Docker images previously stored in the Docker registry on {% data variables.location.product_location %} to the {% data variables.product.prodname_container_registry %}.	{% data reusables.gated-features.packages %}	Enterprise owners can migrate Docker images to the {% data variables.product.prodname_container_registry %}.	feature docker-ghcr-enterprise-migration	Migrate to Container registry	Containers Docker Migration	/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry

{% data reusables.package_registry.container-registry-ghes-beta %}

About the {% data variables.product.prodname_container_registry %}

{% data reusables.package_registry.container-registry-benefits %} For more information, see "AUTOTITLE."

For more information about configuring {% data variables.product.prodname_registry %} for {% data variables.location.product_location %}, see "AUTOTITLE."

About migration from the Docker registry

{% data reusables.package_registry.container-registry-replaces-docker-registry %} If the Docker registry on {% data variables.location.product_location %} contains images, you must manually migrate the images to the {% data variables.product.prodname_container_registry %}.

{% ifversion ghes %}

[!NOTE] {% data reusables.package_registry.container-registry-ghes-migration-availability %}

{% endif %}

{% data reusables.package_registry.container-registry-migration-namespaces %} For more information about the impact of migration to the {% data variables.product.prodname_container_registry %}, see "AUTOTITLE."

Migrating organizations to the {% data variables.product.prodname_container_registry %}

You can start a migration of all your organizations' Docker images to the {% data variables.product.prodname_container_registry %}. The duration of the migration operation depends on the total number of images to migrate, and the overall load on your instance. After a successful migration, {% data variables.product.product_name %} will display a summary, and all future uploads of Docker images will use the {% data variables.product.prodname_container_registry %}.

If a site administrator has configured email notifications for {% data variables.location.product_location %}, you will receive an email after the migration is complete. For more information, see "AUTOTITLE."

During the migration

During the migration, the CPU and memory usage for your instance will increase. To ensure the performance of the instance for your users, {% data variables.product.company_short %} recommends that you begin a migration during a period of reduced activity.

[!WARNING] Do not modify settings for your enterprise or run ghe-config-apply from an administrative SSH session. These actions will trigger a configuration run, which can restart services and may interrupt the migration.

After the migration

After the migration, storage pressure on your instance will increase due to the duplication of image files in the Docker registry and the {% data variables.product.prodname_container_registry %}. A future release of {% data variables.product.product_name %} will remove the duplicated files when all migrations are complete.

For more information about monitoring the performance and storage of {% data variables.location.product_location %}, see "AUTOTITLE."

Starting a migration

{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %}

1. In the left sidebar, click Packages.
2. To the right of the number of packages to migrate, click Start migration. During the migration, {% data variables.product.product_name %} will display progress on this page.

After the migration completes, the page will display the results. If a migration fails, the page will show the organizations that own the package that caused the failure.

Re-running a failed organization migration

Prior to migration, if a user has created a package in the {% data variables.product.prodname_container_registry %} that has an identical name to an existing package in the Docker registry, the migration will fail.

1. Delete the affected container in the {% data variables.product.prodname_container_registry %}. For more information, see "AUTOTITLE." {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.packages-tab %}
2. To the right of the number of packages to migrate, click Re-run migration. During the migration, {% data variables.product.product_name %} will display progress on this page.
3. If the migration fails again, start from step 1 and re-run the migration.