Sitecarry Backup & Migration – Restore, Clone & Cloud Backups
by Dotance 5 (2 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 #34,124 among WordPress.org plugins with 10+ active installations, is #2,295 of 5,310 in the Utilities & Tools category, a 5/5 rating from 2 reviews, and was last updated Oct 25, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.4
v1.41.0 Current Version v1.41.0
Updated 1 week ago Last Update on 25 Oct, 2026
Refreshed 1 week ago Last Refreshed on
#2,295 of 5,310 in Utilities & Tools Top 50% by installs Downloads -70.6% this week Actively maintained
View on WordPress.org
Rank
#34,124
— No change
Active Installs
10+
+900%
KW Avg Position
108
1.7 worse
Downloads
853
+1 today
Support Resolved
0%
— No change
Rating
100%
Review 5 out of 5
5 (2 reviews)

Next Milestone 20

Total Progress 70%
10+ 20+
10,951
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 3 more installs to reach 20+

Rank Changes

32,418 33,271 34,124 34,977 35,830 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
33,156 33,514 33,872 34,230 34,588 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
Current #34,124
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 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-2026
0 10 20 30 40 50 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026 02-11-2026 03-11-2026 04-11-2026 05-11-2026 06-11-2026 07-11-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

5.0
2 reviews
Overall 100%
5
2 (100%)
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 Restore this site next to the package and confirm. Sitecarry offers to take a backup of the site as it is first, then rebuilds the package's database in tables of its own, swaps them in, and puts the files back. Nothing is uploaded by hand and no passphrase is needed — you are already signed in as an administrator.
The tables it replaced are kept for two days, so a change of mind is quick. If the archive is no longer on this server — a host clean-up, a file deleted by hand — the same button still works: the package is downloaded back from Google Drive, S3 or FTP first, verified, and only then restored. Nothing on the site is touched until it is here and proven. Moving a site to a different server is the other case, and it still uses the
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".

Sign In / Register

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