Migrating from WP Offload Media
WP Media Cloud can take over media that WP Offload Media (by Delicious Brains) already put in your bucket. Nothing is uploaded again and nothing in the bucket is moved, renamed or deleted.
How the migration works#
WP Offload Media keeps a record of every offloaded file in its own database table, wp_as3cf_items. The migration reads that table and creates a WP Media Cloud record for each attachment: the bucket, the region and the exact path of the original file and every image size. WP Media Cloud then serves those files from the bucket like any file it offloaded itself.
The migration finds WP Offload Media by its data, not by whether the plugin is active. You can run it while WP Offload Media is active or after you deactivated it, as long as its table is still in the database.
There are two ways to run it:
- Setup wizard (new sites): the wizard copies WP Offload Media’s storage settings, saves them and imports the records in one go.
- Migration tab (sites already set up): imports the records only.
Supported providers#
| WP Offload Media provider | WP Media Cloud provider | Notes |
|---|---|---|
| Amazon S3 | Amazon S3 | Keys and bucket are copied. |
| DigitalOcean Spaces | DigitalOcean Spaces | Keys and bucket are copied. |
| Google Cloud Storage | Google Cloud | Bucket is copied. WP Offload Media uses a service account key; WP Media Cloud needs HMAC keys, which you create in Google Cloud under Cloud Storage, Settings, Interoperability. |
What is imported#
- Settings (setup wizard only): provider, bucket, region, access key and secret, the delivery domain or CloudFront domain as the CDN URL, and the object prefix.
- Where settings come from: the WP Offload Media settings page, or the
AS3CF_SETTINGSconstant inwp-config.php, which wins when both exist. Keys can also come fromAS3CF_AWS_ACCESS_KEY_IDandAS3CF_AWS_SECRET_ACCESS_KEY(or theDBI_AWS_andAWS_versions), orAS3CF_DO_ACCESS_KEY_IDandAS3CF_DO_SECRET_ACCESS_KEYfor Spaces. - Records: one per attachment in the Media Library, with the paths of the original file and every size. Records for attachments WP Media Cloud already tracks are skipped.
Keys stay on the server. The wizard shows Copied from WP Offload Media in the key fields; the real values are never sent to your browser.
If WP Offload Media used the server’s IAM role instead of keys, there are no keys to copy. The wizard tells you, and you enter an access key and secret for the bucket.
Before you start#
- Back up your database.
- Install and activate WP Media Cloud. You don’t need to deactivate WP Offload Media first.
- On a multisite network, run the migration on each subsite. Keys set as constants in
wp-config.phpare shared by every subsite, so only a super admin can copy them; a subsite admin enters the keys by hand.
Run the migration#
New site: setup wizard#

- Open Media Cloud. The setup wizard starts.
- Under Moving from another offload plugin? you see WP Offload Media with the number of files, the bucket and the provider. Click Use these settings.
- On Configure, check the fields. A box at the top lists what was copied and anything still needed. Fill in anything missing.
- Click Continue, then Save & import N files. A progress bar shows the import.
- Follow the Next steps on the last screen, then click Go to Dashboard.
Site already set up: Migration tab#

- Set up WP Media Cloud with the same bucket WP Offload Media used.
- Open Media Cloud > Migration. The WP Offload Media card shows Active or Deactivated, data found, the providers detected and the number of records.
- Click Import AS3CF Records. The import runs in batches with a progress bar until all records are imported.
After the import#
- Deactivate WP Offload Media in Plugins, so only WP Media Cloud rewrites media URLs.
- Open a few pages and posts with images and check that they load.
- Open Media > Library in list view. Imported files show In cloud.
- Run Offload All Media on the Dashboard if WP Offload Media had not offloaded everything. Imported files are skipped.
Don’t delete WP Offload Media’s table until you are sure you won’t need to migrate again. WP Media Cloud never changes or deletes it.
What happens to your URLs#
- WP Media Cloud builds each file’s URL from your CDN URL (or the bucket address) and the file’s exact path as WP Offload Media stored it, so existing images keep working.
- With the setup wizard, new uploads use WP Offload Media’s object prefix, such as
wp-content/uploads/. If no prefix was set, WP Offload Media’s default,wp-content/uploads, is used. If the prefix was turned off, none is used. You can change it later under Path prefix on the Settings tab. - Image URLs in post content and in
srcsetare rewritten as pages load. Nothing in the database is changed. - If WP Offload Media served files from a CloudFront or custom domain, keep that domain pointing at the bucket and use it as the CDN URL.
Restoring files#
To bring every offloaded file back to your server, for example before removing WP Media Cloud, click Download All to Server on the Dashboard or run wp wpmc restore. This works for imported files too.
Troubleshooting#
| Problem | Fix |
|---|---|
| The wizard does not list WP Offload Media | Its table wp_as3cf_items is missing or has no Media Library rows. If the site was offloaded with a very old version, update WP Offload Media first so it creates the table. |
| Keys are listed as still needed | The keys were not in the settings or in wp-config.php (for example with an IAM role), or you are a subsite admin on a network. Enter the keys. |
| Images are broken after the import | Check that the bucket and CDN URL match what WP Offload Media used, then click Run All Checks on the Health tab. |
| Some attachments are not offloaded | WP Offload Media had not offloaded them. Run Offload All Media. |
| The import stops with an error | Run it again. It continues where it stopped and skips imported records. |