Migrating from Advanced Media Offloader
Advanced Media Offloader is a WordPress media offload plugin primarily focused on Cloudflare R2. If you are switching to WP Media Cloud, your files stay in your R2 bucket exactly where they are. WP Media Cloud can read Advanced Media Offloader’s credentials directly and configure itself automatically, then import all offload tracking records. No files are moved, copied, or re-uploaded.
Supported providers#
Advanced Media Offloader’s primary supported provider is Cloudflare R2. The migration assistant is designed around R2 and includes auto-configuration from AMO’s saved credentials. If you are on a different provider, you will need to configure WP Media Cloud manually before running the import.
How Advanced Media Offloader stores offload data#
Advanced Media Offloader stores offload status in WordPress postmeta on each attachment:
advmo_offloaded = "1"— marks the attachment as offloadedadvmo_path— the subdirectory path within the bucket (e.g.2024/01/)
Storage credentials are in WordPress options under advmo_credentials. WP Media Cloud reads both during migration.
Before you start#
- Take a full database backup. The migration writes new records to the WP Media Cloud database table.
- Install and licence WP Media Cloud. See Installation and Activating your licence.
- Do not disable Advanced Media Offloader yet. Keep both plugins active during the migration.
Auto-configuration from AMO credentials#
If you are using Cloudflare R2, WP Media Cloud can read Advanced Media Offloader’s saved credentials and configure itself automatically. Go to Media Cloud > Migration. If WP Media Cloud detects Advanced Media Offloader with R2 credentials, an auto-configure option will be available. Click it to populate WP Media Cloud’s R2 settings from AMO’s saved values — Account ID, Access Key ID, Secret Access Key, bucket name, and CDN domain are all read directly from AMO’s options.
After auto-configuration, run the connection test in WP Media Cloud > Settings > Storage to confirm the credentials are correct before proceeding with the import.
Auto-configuration is only available for Cloudflare R2. If AMO is configured for a different provider, configure WP Media Cloud manually using the setup wizard before running the import.
Running the migration#
Go to Media Cloud > Migration. WP Media Cloud will display a summary showing the total number of attachments marked as offloaded by Advanced Media Offloader, how many have already been imported, and how many remain.
Click Start Migration. WP Media Cloud reads AMO’s postmeta records in batches and creates corresponding WP Media Cloud tracking records pointing at the same files. It constructs the full bucket path for each file by combining the advmo_path subdirectory with the filename from the attachment’s file record. Thumbnail paths are built from the attachment’s registered sizes metadata. Progress is shown as the import runs. The migration can be paused and resumed at any time.
No files are moved or re-uploaded.
After the migration completes#
- Verify — go to Media > Library and click on several images. Confirm the file URL shows your R2 CDN domain or bucket hostname rather than your site URL.
- Enable URL rewriting in WP Media Cloud — go to WP Media Cloud > Settings and confirm Rewrite URLs is enabled.
- Deactivate Advanced Media Offloader — once you have confirmed WP Media Cloud is serving correct URLs, deactivate Advanced Media Offloader from the Plugins page.
- Test the site — browse several pages and confirm images load correctly.
Troubleshooting#
Migration tab shows zero offloaded items
WP Media Cloud detects AMO’s offloaded attachments via the advmo_offloaded postmeta key. If no items are found, Advanced Media Offloader may not have completed any offloads, or the postmeta may have been removed. Confirm AMO had offloaded files before migrating.
Some attachments show errors during import
If an attachment’s file record cannot be resolved to a filename, WP Media Cloud skips it with an error count. This can happen if the attachment’s postmeta is incomplete. Check those attachments individually in the media library and re-offload them using WP Media Cloud’s bulk migration tool if needed.
Auto-configuration is not available
Auto-configuration requires Advanced Media Offloader to be active and configured for Cloudflare R2. If AMO is using a different provider, configure WP Media Cloud manually using the setup wizard and run the import from the Migration tab.
Images return 404 after deactivating Advanced Media Offloader
Confirm URL rewriting is enabled in WP Media Cloud > Settings and that the R2 bucket name, Account ID, and credentials match what AMO was using. Run the connection test to confirm.