GCR to Google Artifact registry migration using gcloud artifacts docker upgrade migrate command

[himalhewagamage]

I need to migrate Google Container Registry (GCR) images to Google Artifact Registry. Currently, we have GCR images hosted in a central project (central-shared-services), which contains multiple service image repositories organized by different project names. To perform the migration, I attempted to use the gcloud artifacts docker upgrade migrate command, as shown below.

Google provides the following command syntax:
gcloud artifacts docker upgrade migrate --from-gcr=gcr-host/project-id --to-pkg-dev=project-id/repository-id

Here is the specific command I used:
gcloud artifacts docker upgrade migrate --from-gcr=asia.gcr.io/central-shared-services --to-pkg-dev=central-shared-services/application-repo-id

When I run this command, the images are successfully copied to the destination location. However, the destination paths are different from what I expected. Since the central-shared-services project contains multiple repositories, all repositories are being migrated into the single application-repo-id repository. This results in image paths such as:

central-shared-services/application-repo-id/project-1-repo
central-shared-services/application-repo-id/project-2-repo

The central-shared-services project contains more than 300 repositories, so managing them in this structure becomes challenging.

Is this behavior a bug in the gcloud migration tool? Alternatively, is there a way to map the source repositories to identical destination repositories during the migration to maintain a one-to-one mapping?