Sitecarry Backup & Migration – Restore, Clone & Cloud Backups
by Dotance 1 (0 reviews)

Sitecarry Backup & Migration – Restore, Clone & Cloud Backups

Back up, restore and migrate your site — files and database in one package — and prove each backup restores before you need it.

Sitecarry Backup & Migration ranks #63,426 among WordPress.org plugins with 1+ active installations, is #3,411 of 4,977 in the Utilities & Tools category, a 1/5 rating from 0 reviews, and was last updated Sep 21, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1
v1.31.1 Current Version v1.31.1
Updated 1 day ago Last Update on 21 Sep, 2026
Refreshed 7 hours ago Last Refreshed on
#3,411 of 4,977 in Utilities & Tools Actively maintained
View on WordPress.org
Rank
#63,426
No change
Active Installs
1+
-1%
KW Avg Position
127
12 worse
Downloads
48
+2 today
Support Resolved
0%
No change
Rating
20%
Review 1 out of 5
1 (0 reviews)

Next Milestone 10

Total Progress 10%
0+ 10+
62,480
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

  • Exact install estimates within tiers
  • Track install growth over time
  • Milestone progress predictions
Upgrade to Pro
Need 9 more installs to reach 10+

Rank Changes

60,255 61,840 63,426 65,012 66,597 16-09-2026 17-09-2026 18-09-2026 19-09-2026 20-09-2026 21-09-2026 22-09-2026 23-09-2026
60,255 61,840 63,426 65,012 66,597 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026 17-09-2026 18-09-2026 19-09-2026 20-09-2026 21-09-2026 22-09-2026 23-09-2026
Current #63,426
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

0 10 20 30 40 16-09-2026 17-09-2026 18-09-2026 19-09-2026 20-09-2026 21-09-2026 22-09-2026 23-09-2026
0 10 20 30 40 08-09-2026 09-09-2026 10-09-2026 11-09-2026 12-09-2026 13-09-2026 14-09-2026 15-09-2026 16-09-2026 17-09-2026 18-09-2026 19-09-2026 20-09-2026 21-09-2026 22-09-2026 23-09-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

1.0
0 reviews
Overall 20%
5
0 (0%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Frequently Asked Questions

Common questions about Sitecarry Backup & Migration – Restore, Clone & Cloud Backups

In wp-content/uploads/sitecarry/, protected from direct web access.
Sitecarry removes its settings and its scheduled events from the database, and stops scheduling anything. Your packages in wp-content/uploads/sitecarry/ are left exactly where they are, on purpose — deleting a plugin should never be the thing that destroys your last copy of the site. Delete that folder yourself once you are sure you no longer need what is in it.
Background backups need the site to be able to send an HTTP request to itself. Some hosts block that. When Sitecarry detects it cannot, it falls back to running the backup from your browser instead, which works everywhere but needs the tab left open. Ask your host to allow loopback requests if you want unattended backups.
Press Get installer next to the package, and Download archive under More. Upload both files into this site's folder — the one that holds wp-admin — and open installer.php in a browser. You will need the package passphrase, shown beside the package, and this site's database password. Your stored packages are not touched. A restore replaces the very files WordPress is running from, so it cannot be done from inside WordPress, and a plugin has no business writing a program into your site folder to do it. That upload is yours to make.
While a backup is running there is a Stop backup button under the progress bar, and it will tell you if that backup has stopped making progress. Stopping clears away the half-built package. From the command line, wp sitecarry stop does the same — useful if the admin screen is not loading. Nothing is lost by stopping: a partial package cannot be restored from anyway.
Yes. wp sitecarry backup builds one and waits for it, with no execution limit and nothing to keep open. wp sitecarry verify --all checks every package and exits non-zero if any fails, so it works in a monitoring script. wp sitecarry status prints how the site is protected.
No, and nothing short of restoring it does. Verifying proves the archive is the one that was written, still opens, and holds the files a restore starts from. That catches truncated uploads, disks that filled mid-write and silent corruption. It
That last gap is exactly what rehearsing closes — see the next two questions.
Verifying reads the archive: it confirms the file is the one that was written, that it still opens, and that the two files a restore cannot start without are inside. It takes seconds and it cannot tell you the database will import. Rehearsing imports it. The whole database export is run into tables of the plugin's own, the row count is compared against what was recorded at backup time, and the tables are then dropped. Nothing on your site is written to at any point. That is the difference between "this file is intact" and "this backup works".
Yes. Turn on Rehearse weekly in Settings and Sitecarry proves the newest full backup once a week, on Sunday, three hours after your backup hour. You hear from it only when it fails — the same failures-only rule backups use, for the same reason: a weekly all-clear stops being read within a month and takes the important one with it. The hour is not a setting on purpose. It follows the backup hour so the two cannot be pointed at each other, and a rehearsal stands aside if it finds a backup running.

Sign In / Register

You need to sign in or register to use this feature.