Description
SiteRelay copies a WordPress site (its database, its files, or both) to another WordPress site, and keeps a way back.
What makes SiteRelay different
- Everything is free: pull, push, backups, multisite subsites and WP-CLI. No paid version, no size caps, no account.
- Your two sites talk to each other directly. Nothing passes through a third-party service or the author’s servers.
- A way back from everything: a restore point before every change, and one click to undo it (even a push, undone on the site it went to).
- You see what will happen first: every pull and push shows a summary before it starts, and Find & Replace previews every change.
- Built for big sites: work moves in small steps that hosting time limits don’t stop, and a job can be paused, resumed or cancelled.
- Multisite both ways: bring a site into a network as a new or existing subsite, or take a subsite out, with users merged by email.
Pull and push
- Pull another site into this one, or push this site to another. SiteRelay runs on both sites; they talk to each other directly.
- Copy the whole site, just the database, or the parts you choose: themes, plugins, must-use plugins, uploads and the rest of wp-content.
- Addresses and file paths change to the receiving site’s automatically, including inside serialized data and JSON.
- Mirror mode moves aside what the receiving site has and the other doesn’t, so it matches exactly.
- Access keys decide who may pull from or push to a site, and the site mode (locked, pull-only, push-only or open) sets what it accepts at all. A site can lock itself after a push arrives.
Backups, export and import
- Full backups of the database and files, to keep on the server, download, or import on another site and restore there (the by-file way to put a site live).
- Choose what a backup holds: the database, themes, plugins, must-use plugins, uploads, the rest of wp-content and the files in the site’s root such as .htaccess and robots.txt (never WordPress itself or wp-config.php), compressed or not. Restoring replaces only what the backup holds.
- Export the database as .sql or .sql.gz, and import .sql, .sql.gz (from SiteRelay, mysqldump or phpMyAdmin) or a SiteRelay backup .zip.
- Find & replace across the database with a preview first; serialized and JSON data stay intact.
A way back
- Every pull, push, import, restore and find & replace saves a restore point first. Undo it from History; a push is undone on the site it went to.
- When the users came with what was copied, SiteRelay takes you to the login page and back to the job.
Multisite
- SiteRelay works on one subsite at a time: export, import, back up, find & replace, pull and push it.
- A site that comes into a network becomes one of its subsites, existing or new, and its users join the network, merged by email and shown before anything runs.
And
- Saved profiles and “Run again”, email and webhook notifications when a job ends, and a History of every job with a downloadable report.
- WP-CLI:
wp relay pull,push,export,import,find-replace,backups,keys,mode,jobsandsubsites.
Security
Every request between two sites is signed with the access key’s secret (HMAC-SHA256) and can be used only once; the answers are signed too. Secrets are stored encrypted. Nothing passes through a third party: the two sites talk to each other.
External services
SiteRelay uses no service of its own, and never sends data about your site to its author. It connects only to:
- The WordPress sites you connect it to. A pull or push carries what you chose to copy (database tables and files) between your site and the other site, which runs SiteRelay too, at the address in the connection string from that site’s Access keys screen. Every request is signed with that access key, and nothing passes through anyone else.
- The email addresses or webhook URL you enter under Settings → Notifications, and only once you switch them on. They receive a short summary of a finished or failed job (its type and status, the other site’s address and a link to the job). A webhook can be any service that accepts a JSON POST, such as Slack’s incoming webhooks; that service’s own terms and privacy policy apply (for Slack: https://slack.com/terms-of-service and https://slack.com/trust/privacy/privacy-policy).
- This site itself: after a pull, push or restore, SiteRelay loads the site’s home page once to check that it still works, and puts the site back if it doesn’t.
Source code and building
The screens are built from the TypeScript source in ui/: run cd ui && npm ci && npm run build to write build/. The PHP source is in src/.
Installation
- In WordPress, go to Plugins → Add New, search for “SiteRelay”, click Install Now, then Activate. On a multisite network, install it from Network Admin and click Network Activate.
- Open Tools → SiteRelay (on a network: Network Admin → SiteRelay).
- To pull or push, install SiteRelay on the other site too. There, create an access key under Access keys, and paste its connection string into Pull or Push here.
FAQ
Does SiteRelay have to be on both sites?
To pull or push, yes. To restore a backup on another site, only that site needs SiteRelay: download the backup here and import it there.
What does a backup hold?
By default the whole site: the database, themes, plugins, must-use plugins, uploads, the rest of wp-content, and the files in the site’s root folder, such as .htaccess, robots.txt and verification files. You can untick any of them, or leave out single files and folders in the root; other WordPress sites found there (a staging copy, say) are left out unless you tick them. WordPress’ own files and wp-config.php are never in a backup, so restoring never touches the receiving site’s WordPress or its database login. Server settings (.htaccess, .user.ini, php.ini, web.config) are put back with a site’s own backups, and from another site’s backup only when you tick them, because rules from another host can stop a site from loading.
Can I undo a migration?
Yes. SiteRelay saves a restore point before it changes anything, and History offers to undo the job. It keeps the newest restore points (2 by default; see Settings).
Why do I have to log in again after a pull or a restore?
When the users were copied too, this site now has the other site’s accounts: log in with one of those. SiteRelay takes you to the login page and brings you back to the job.
Is my data sent anywhere else?
Not your site’s data. The two sites talk to each other directly, and notifications go only to the email addresses or webhook you set. SiteRelay uses no service of its own; see External services.
Does SiteRelay download plugins, themes or other code?
Not from its author or any service. A pull or push copies the files you choose, plugins and themes included, between your own sites: only when you start it, and only with an access key the other site’s administrator created for this. SiteRelay never pulls or pushes on its own; its one scheduled task tidies up, removing old history, backups past your limit and temporary files.
Does SiteRelay add files outside its own folder?
No. Everything SiteRelay keeps is in one private folder, wp-content/uploads/siterelay, removed when you delete SiteRelay:
- exports and backups, under random names;
- restore points: the files a pull, push or restore replaced, packed into an archive shortly after the job finishes, so the job can be undone;
- while a job runs, the files on their way in and the ones they replace, in folders named after the job’s random id.
Each folder has an index.php and rules that refuse direct access, and once a job’s restore point is packed, nothing SiteRelay keeps is a file a web server could run. SiteRelay writes nothing into the mu-plugins folder or other plugins’ folders; only a pull, push or restore that you start changes the site’s own themes, plugins and uploads. On a site that ran an earlier build the folder is uploads/relay, and the wp-content folders siterelay-staging and siterelay-backups (or relay-staging and relay-backups) that earlier builds used can be deleted.
What does SiteRelay leave out when it copies files?
What a copy of the site doesn’t need: caches, logs, the backup folders of other backup and migration plugins, WordPress’ upgrade folders, an analytics plugin’s location database (that plugin downloads it again), and version-control and node_modules folders. SiteRelay’s own folders are never copied. To bring something back for one job, choose Custom and add a line starting with ! under Leave out, for example !uploads/iawp-geo-db.mmdb.
How do I translate SiteRelay?
On translate.wordpress.org, like any plugin in the directory. The template is also in the plugin: languages/siterelay.pot. Put the PHP translations in languages/siterelay-{locale}.mo and the screens’ translations in languages/siterelay-{locale}-relay-app.json.
Coming from Relay 0.9.x?
SiteRelay is Relay’s new name: the same plugin, now in the WordPress.org directory. Deactivate Relay, then install and activate SiteRelay from Plugins → Add New. Your settings, access keys, saved connections, history and backups carry over. Then delete Relay on the Plugins screen: SiteRelay keeps your data. Sites still on Relay 0.9.x can keep pulling from and pushing to SiteRelay sites in the meantime.
Screenshots






Changelog
1.0.1 (2026-11-09)
- SiteRelay’s screens make everything they show with the React that WordPress loads, instead of a copy of part of React built into SiteRelay, so they keep working when WordPress moves to React 19.
1.0.0 (2026-11-09)
- First release on WordPress.org.
- Pull and push between WordPress sites: the whole site, just the database, or the parts you choose, with addresses changed to the receiving site’s.
- Backups of the database and files, database export and import, and find & replace with a preview.
- A restore point before every change, and undo from History (a push is undone on the site it went to).
- Multisite: one subsite at a time, into a network or out of it, with users merged by email.
- WP-CLI commands for everything the screens do.
Before 1.0.0
- Earlier versions were released privately as Relay. Coming from Relay 0.9.x? See the FAQ: your data carries over.
