Everything you need to know about backing up, restoring, and migrating your WordPress site with BackupRidge.
Choose a backup from history, select components to restore, and confirm.
If a completed backup still lives on a configured remote destination (Amazon S3, Cloudflare R2, FTP, SFTP, or a Pro OAuth provider), you can start a restore without downloading every part to your computer first. The plugin retrieves the archives from that provider using your saved credentials, then runs the same restore pipeline as for local backups.
Upload single or multi-part archives, finalize import, then start restore from imported data.
Make sure upload_max_filesize and post_max_size support your chosen chunk size.
Before overwriting the database, you can enable an optional pre-restore database export in the restore dialog (off by default). When enabled, a SQL snapshot is written under your BackupRidge server folder (for example under wp-content/uploads/backupridge/) with a name such as pre-restore-*.sql. It does not appear in Backup History as a normal backup job; it is a safety net if you need to roll back the database step.
Receiving a site (free): Back up on the source site, upload that archive on the destination site from the Migrate admin page, then restore and validate. BackupRidge assembles and restores the incoming site here — this receiving side is free.
Pushing a site (Pro): Pushing a migration directly from one BackupRidge install to another — including staging clones — is a Pro feature and does not require manually moving an archive between sites.
Run safe serialized URL replacements when moving between domains.