You already have a backup. It lives on a laptop, a Dropbox folder, or an old host download page. The plugin that made it is gone, expired, or locked behind a dashboard you no longer control. What you need is a way to get that archive into WordPress and put the site back.
That is a different job from scheduling nightly Drive copies, and a different job from migrating to a new domain. It is the “I have a ZIP, make it live” path.
Snapshotify supports upload and restore of an existing backup ZIP from the dashboard, with chunked uploads so PHP size limits stop mattering, and the same restore flow used for snapshots it created. Uploaded backups are never pruned by retention. Retention only cleans automatic scheduled runs.
If you still need the sermon about off-site copies, read a WordPress backup on the same server is not a backup. For the pre-update ritual, see database-only backup before a plugin update.
The problem: backups trapped outside the panel
Common traps:
- Host gave you a raw archive after a hack, but no one-click restore
- Old plugin exported a ZIP+SQL pair you can open on disk, but not reinject easily
- PHP
upload_max_filesizerejects anything over 64MB or 128MB - You are scared to run a blind search-replace on serialized data
Snapshotify’s answer is boring on purpose: upload the archive in chunks, then restore with extraction, import, and URL handling done for you. Native Snapshotify archives are standard ZIP and SQL, readable without the plugin. When you bring an external ZIP, you still want a clear files+database layout you trust.
What Snapshotify actually gives you here
Upload an existing backup ZIP from the dashboard.
Chunked upload so host PHP limits stop being a hard ceiling.
Same restore path as snapshots created inside the plugin.
Uploaded backups are never pruned automatically. Only scheduled automatic backups follow retention.
Around that: one-click backup and restore, full-site snapshots, database-only snapshots, migration with serialized-safe URL rewrite, scheduled Pro backups to Google Drive / Dropbox / OneDrive, retention per destination, batched work for large sites, smart exclusions, download archives, and email notifications when a scheduled run finishes or fails.
Free covers full manual backup, upload, restore, and migration. Pro adds schedules and cloud destinations.
Restore runbook (upload path)
- Put the site in a maintenance mindset. Warn clients. Pause editorial publishing.
- Confirm you have files + database. A media-only ZIP will not rebuild WordPress.
- Open Snapshotify → Upload & Restore. Start the chunked upload and wait for the archive to appear in the list.
- Restore. Let the plugin extract, import SQL in batches if needed, and rewrite URLs when the destination domain differs.
- Smoke test. Homepage, wp-admin login, a form submit, a shop add-to-cart if you run WooCommerce, and permalinks.
- Keep the uploaded archive. Retention will not delete it. Still download a fresh Snapshotify snapshot to your own cloud after a successful restore so you are not dependent on the old file forever.
When the destination domain changed
Restore onto a new domain and Snapshotify rewrites URLs and paths across the database, including serialized data. That is the migration path. You do not need a separate search-and-replace script for the common case. Still verify widgets, Elementor/Divi storage, and any hard-coded old hosts in theme files that live outside the database.
Pitfalls
- Uploading a partial archive. Test-open the ZIP on your machine first. Look for
wp-contentand a.sqldump. - Restoring over a site you still need. Take a fresh Snapshotify snapshot of the current state before you overwrite it.
- PHP timeouts on huge SQL. Snapshotify batches imports. If a host is extremely aggressive, retry and watch progress rather than assuming failure at the first stall.
- Assuming retention will tidy uploads. It will not. Delete ancient uploaded ZIPs yourself when you are sure you do not need them.
- Skipping a post-restore off-site copy. The whole point of surviving a hack is not leaving the only good copy on the same disk. Connect Drive, Dropbox, or OneDrive on Pro after you are stable.
How this fits DaftPlug Pro
Snapshotify is part of the same membership as Progressify, Lightify, Generatify, and Rankify. One licence, every Pro plugin, site-count tiers on pricing. Fourteen-day money-back. Free is enough to upload and restore. Pro is how you stop relying on manual heroics.
What “standard ZIP and SQL” buys you
Snapshotify packages its own snapshots as readable ZIP + SQL on purpose. You can open them without the plugin. That matters on the day a host is down and you need to inspect the archive on a laptop. When you upload someone else’s ZIP, prefer the same clarity: a folder tree that looks like WordPress and a SQL dump that imports cleanly.
If the archive is proprietary and encrypted to a dead vendor account, Snapshotify cannot invent a decryptor. Get a usable export first.
Notifications after you are stable
Once the emergency restore works, switch from heroics to boredom. On Pro, schedule daily or weekly backups to Google Drive, Dropbox, or OneDrive, set retention to keep the last N automatic copies, and turn on email notifications for finished and failed runs. An upload that fails should retry; a failure email means you still look.
Manual and uploaded archives stay until you delete them. Do not confuse that with “disk will manage itself.”
Agency / client note
Pro Plus covers 5 sites and Pro Max covers 100. White-label hides licence and branding details from client wp-admin. Upload-and-restore is especially useful when a client hands you “the backup from the old guy” as a random ZIP in Drive.
Takeaway
A backup stranded on a laptop is only useful if you can put it back. Upload the ZIP into Snapshotify in chunks, restore with the same path as a native snapshot, keep uploads out of auto-prune, then take a fresh off-site copy so the next emergency is boring.