Website owners changing file hosts
Move images, downloads and other supported media when an old hosting setup is being replaced.
Bring existing media into your workspace
Media migration for bulk URL and cloud file imports
Moving a few files is easy. Moving hundreds of images, videos or documents from an old host is where the job becomes repetitive.
Media2URL Migration lets you bring supported files into your workspace from external URLs and the cloud-import options available for your account. Instead of downloading each source file first, you can prepare the import, choose where the new assets should go and let the migration run from the dashboard.
The workflow
How bulk migration works
A migration works better when you decide where the files should end up before starting the transfer. That becomes especially important when the source contains assets from several websites, clients or projects.
The basic flow is source → destination → import → review.
1. Add the source files
Add the source URLs or use one of the cloud-import methods available for your account. For a URL migration, each source still needs to be reachable while Media2URL is fetching the file.
2. Decide where they should go
Choose the workspace and organisation settings for the imported files before the job starts. Where available, that can include folders, collections, tags and the default access settings for the new assets.
3. Let the import run
Media2URL fetches the supported files and processes them into the selected workspace. Where duplicate checking is part of the migration flow, the file hash can be used to recognise content that has already been imported.
4. Review the new files and mapping
Once the migration finishes, review the imported assets and the available source-to-destination mapping. A mapping export is useful when an old URL needs to be replaced inside a website, CMS or database.
Target workflows
Who media migration is useful for
Agencies managing several client libraries
Bring existing media into the correct workspace instead of mixing every client's files into one account.
Developers moving CMS assets
Import files referenced by a website or database, then use the migration mapping when old media URLs need to be updated.
Teams consolidating scattered media
Move files from older storage locations into one Media2URL library when the current setup has become difficult to manage.
Efficiency
Bulk migration removes the most repetitive part
The main advantage of bulk migration is not having to save and re-upload every file by hand. You prepare the source list once, choose the destination and then review the files that completed or need attention.
The larger the library becomes, the more useful this is. A batch of ten files is manageable manually. A catalogue with thousands of product images is a different job.
Import many file URLs in one job
A URL migration can start from a list of existing media addresses instead of requiring each file to be uploaded separately.
The migration dashboard keeps the files in the same batch so you can inspect which sources succeeded, view converted links, or see which ones need another look.
A source URL has to be reachable before it can be imported
Media2URL cannot fetch a file from a URL that the migration service cannot reach. The source therefore needs to remain available during the import.
A link that only works inside a private login or blocks server fetches may fail even if it opens in your browser. Test a small batch of URLs first before running a large migration.
Cloud imports are useful when files already live in object storage
If the media already sits inside a supported S3-compatible source, moving it file by file through your computer adds an unnecessary step. A cloud migration can use the import method exposed by your current Media2URL account to bring those files into the workspace.
Check the source permissions before starting. Being able to see a bucket in your own cloud account does not automatically mean Media2URL can read every object inside it.
Duplicate checking looks at the file content
Two files can have different names and still contain exactly the same bytes. During a migration, content-based hashing can help identify that type of duplicate instead of relying only on filenames.
Where Media2URL applies SHA-256 duplicate checking, matching hashes can recognise identical file data before creating redundant copies. A resized image produces a different hash because the binary bytes are different.
Do not migrate old clutter into a new library unchanged
Migration is a good time to decide whether the existing organisation still makes sense. Copying years of inconsistent folders into a new workspace may only move the same problem somewhere else.
Use folders for clear project or client boundaries in your Media Library, and manage distinct client boundaries with Team Workspaces.
Keep a record of where every old URL went
Moving the files is only half of many migrations. A website, database or CMS may still contain old URLs even after the new assets exist inside Media2URL.
A migration map connects the source address with the new Media2URL output. The mapping can help you update old references, but it does not automatically create redirects on a third-party host that Media2URL does not control.
Comparison
Bulk migration and bulk upload solve different problems
| Workflow Attribute | Bulk Upload | Media Migration |
|---|---|---|
| Where the files start | On your local device | Existing URLs or supported cloud source |
| Main purpose | Upload several local files together | Move an existing hosted media library |
| Old URL mapping | Usually not needed | Often important for updating references |
| Destination organisation | Choose upload settings | Plan workspace/folder/tag structure before transfer |
| Typical use | A new batch of local images | Moving away from another host or storage setup |
Use Bulk Image Upload when the files are already on your computer and simply need uploading. Use Media Migration when the files already live somewhere else and downloading them first would create unnecessary work.
Practical use
When migration is better than starting again manually
Moving away from an old image host
A website can accumulate years of product photos, screenshots and downloadable files on the same old host. Importing those existing URLs is more practical than opening every page and downloading each image one by one.
Moving CMS media
A CMS can contain hundreds of media references inside posts and database fields. Move the media first, keep the old-to-new URL mapping and then update the references using the migration plan for that site.
Consolidating client media
Agencies often inherit files spread across several older hosts. Move the supported assets into the correct client workspace so future files, links and organisation are handled from one place.
Moving cloud-stored assets
When the source already lives in supported object storage, use the available cloud-import workflow instead of pulling every file through a local computer first.
Migration boundaries
Before starting a large migration
- Keep the source available. URL-based imports still need the source file to be reachable while Media2URL is fetching it.
- Check the destination first. Make sure the correct workspace, folder and access rules are selected before applying the same setup to a large batch.
- Leave room for the imported files. Migration still uses the storage and upload allowances that apply to the current workspace.
- Do not shut down the old host immediately. Review the important files and URL mapping before treating the migration as finished.
Questions about this workflow
Frequently asked questions
Yes, where batch URL import is available for your account. Add the supported source URLs and choose the destination settings before starting the job. The source files still need to remain reachable while Media2URL fetches them.
A file can fail when the source cannot be reached, the content does not pass the current upload rules or another migration requirement is not met. Check the result shown for that source and retry it where the migration workflow provides that option.
Migration is primarily a file-transfer workflow rather than a promise to improve the media. Whether the imported file is transformed depends on the source and the specific processing rules used by that migration. Check representative files after the transfer when preserving the original output matters.
Yes, where team-workspace routing is available for the migration and your account has permission to use that workspace. Choose the destination before starting the transfer so the imported files do not land in the wrong library.
Media migration is the process of moving existing files from one hosting or storage location to another. In Media2URL, the goal is to bring supported hosted files into your workspace without manually downloading and re-uploading each one.
A normal upload starts with a file on your device. URL import starts with a file that is already reachable online. Media2URL fetches the supported source from that URL and creates the new asset in the selected workspace.
No. Media2URL can provide source-to-new-URL mapping where that migration output is available, but it cannot automatically create redirects on an external host that it does not control. Use the mapping to update your website, CMS or other references as needed.
Where SHA-256 duplicate checking is used, Media2URL compares content hashes to recognise identical file data. Files that only look similar are not necessarily duplicates. A resized or re-encoded image normally has different underlying bytes and therefore a different hash.
Next steps