Migrating from Media Cloud by ILAB
WP Media Cloud can take over media that Media Cloud by ILAB (Media Cloud) already put in your bucket. Nothing is uploaded again and nothing in the bucket is moved, renamed or deleted.
How the migration works#
Media Cloud stores where each file lives in the attachment’s metadata (ilab_s3_info). The migration reads it and creates a WP Media Cloud record for each attachment: the bucket 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 Media Cloud by its data, not by whether the plugin is active. You can run it while Media Cloud is active or after you deactivated it.
There are two ways to run it:
- Setup wizard (new sites): the wizard copies Media Cloud’s storage settings, saves them and imports the records in one go.
- Migration tab (sites already set up): imports the records only.
Supported providers#
| Media Cloud provider | WP Media Cloud provider | Notes |
|---|---|---|
| Amazon S3 | Amazon S3 | |
| DigitalOcean Spaces | DigitalOcean Spaces | |
| Wasabi | Wasabi | |
| Cloudflare R2 | Cloudflare R2 | The account ID comes from the endpoint and the public URL from Media Cloud’s R2 public URL setting. |
| Backblaze B2 (S3 API) | Backblaze B2 | The region comes from the endpoint. |
| Backblaze B2 (native API) | Backblaze B2 | WP Media Cloud uses B2’s S3-compatible API: create an application key and choose the bucket’s region. |
| MinIO, DreamHost, other S3-compatible | Custom S3 | Endpoint and URL style are copied. |
| Google Cloud Storage | Google Cloud | Bucket is copied. Create HMAC keys in Google Cloud under Cloud Storage, Settings, Interoperability. |
| Bunny.net | Bunny.net | Storage zone, password, region and pull zone are copied. Add your Bunny.net account API key for usage stats and CDN purge. |
What is imported#
- Settings (setup wizard only): provider, bucket, region, endpoint, access key and secret, and the CDN base URL.
- Where settings come from: Media Cloud’s settings, its constants or environment variables in
wp-config.php(such asMCLOUD_STORAGE_S3_SECRET), the olderILAB_AWS_S3_andILAB_CLOUD_constants, and on a network in network mode, the network settings. If Media Cloud’s region was set to custom, its custom region is used. - Records: one per attachment, 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 Media Cloud in the key fields; the real values are never sent to your browser.
Before you start#
- Back up your database.
- Install and activate WP Media Cloud. You don’t need to deactivate Media Cloud first.
- On a multisite network, run the migration on each subsite. Keys set as constants or environment variables are 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 in the WP Media Cloud menu. The setup wizard starts.
- Under Moving from another offload plugin? you see Media Cloud 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 Media Cloud used.
- Open Migration. The Media Cloud by ILAB card shows Active or Deactivated, data found, the active provider and the number of records.
- Click Import ilab Records. The import runs in batches with a progress bar until all records are imported.
After the import#
- Deactivate Media Cloud in Plugins, so only WP Media Cloud rewrites media URLs. Both plugins add a menu called Media Cloud; after you deactivate the old one, only WP Media Cloud’s is left.
- 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 Media Cloud had not offloaded everything. Imported files are skipped.
WP Media Cloud never changes or deletes Media Cloud’s metadata.
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 Media Cloud stored it, so existing images keep working.
- Image URLs in post content and in
srcsetare rewritten as pages load. Nothing in the database is changed. - If Media Cloud served files from a CDN domain, keep that domain pointing at the bucket and use it as the CDN URL.
- Media Cloud features WP Media Cloud does not have, such as Imgix image processing, stop when Media Cloud is deactivated.
Restoring files#
To bring every offloaded file back to your server, 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 Media Cloud | No attachment has Media Cloud metadata. Check that the media was offloaded by Media Cloud and not only served through its CDN. |
| The provider is not recognised | The wizard asks you to choose the provider. Choose it and enter its details. |
| Keys are listed as still needed | The keys were not found in Media Cloud’s settings or constants, the provider uses other keys (Google Cloud, Backblaze native API), 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 Media Cloud used, then click Run All Checks on the Health tab. |
| The import stops with an error | Run it again. It continues where it stopped and skips imported records. |