Moving Hosts and Using Staging Sites
Moving to a new host
Media Cloud Sync keeps its settings and records in your WordPress database, so a normal site move brings them along.
- Copy your files and your whole database, including the
wpmcs_itemstable. - If your keys are in
wp-config.php, copy theWPMCS_CONFIGconstant too. See Storing Credentials in wp-config.php. - On the new host, open Settings and click Recheck on the Storage and Delivery cards.
- Make sure WP-Cron works there, or add a server cron job. Tools → Site Health reports this: see Site Health.
With Remove files from server on, there’s less to copy, since media stays in the bucket. If you’d rather have local copies on the new host, use Restore Media to Server PRO first.
Changing your domain
Cloud URLs don’t contain your site’s domain, and your posts store local URLs that are rewritten on display. After a normal domain change, run your usual search-and-replace on the database. Then, if you use it:
- Bucket CORS
PRO: click Update to add the new address. - A Pro license is tied to the site’s address. Deactivate it on the old domain first, and activate it on the new one.
Staging copies
Warning: A staging copy of your database still points to your live bucket. Deleting media on staging deletes its cloud files, which breaks them on your live site. New uploads on staging also land in the live bucket.
Safer options:
- Give staging its own bucket. Migrate a copy there with Migrate Bucket to Bucket
PROon the staging site, leaving Delete source files after they are copied off. - If staging must share the bucket, don’t delete media there, and give it its own prefix in Storage settings so new uploads stay apart.
Don’t run Clean Up Unused Files PRO to delete on a site that shares a bucket and base path with another site: the other site’s files look unused.
Copying only the settings
To set up another site the same way, use Import / Export. Secrets aren’t included, and it doesn’t copy any media or records.