Using auto-upload to lazily migrate assets from one product environment to another

To migrate all assets from one product environment to another using auto-upload, you should create a mapping for each asset type and delivery type.

For example, you would need to create three mappings to migrate all assets of delivery type "upload":

1. To migrate asset type image e.g.

image-assets -> https://res.cloudinary.com/<product_environment_name>/image/upload

2. To migrate asset type video e.g.

video-assets -> https://res.cloudinary.com/<product_environment_name>/video/upload

3. To migrate asset type raw e.g.

raw-assets -> https://res.cloudinary.com/<product_environment_name>/raw/upload

The folder name can be anything and follow similar logic for other delivery types. Please also see the below screenshot as an example.  

Note: As mentioned in Configuring auto-upload URL mapping, you can map assets to go directly to your root folder by using a forward slash in the folder name. However, this approach only works for one asset and delivery type at a time. You would need to update the delivery URL and the URL prefix of the mapping for each different asset and delivery type. Therefore, this method is not recommended when lazily migrating from one Cloudinary product environment to another. If you need to migrate your assets to the root folder, it's better to use our APIs as mentioned in this article.