SSF Backup & Migrate

The supported scope is your WordPress database tables for this installation’s prefix and supported wp-content files, including eligible media, plugins and themes.

WordPress core, wp-config.php, external directories, symlinks, caches, private backup storage and specified sensitive/excluded paths are outside that scope. Keep hosting access, configuration and an independent recovery route separately. Existing third-party proprietary backup formats are not accepted.

Backup work is split into bounded steps and its progress is saved. Reopen the job and inspect its current state before resuming supported work. Pro also lets an administrator adjust the work-item budget per step.

Actual capacity depends on hosting resources and archive safety limits. A stated code ceiling is not a promise that every host can process that size. Restore is a separate, non-atomic operation and is not resumable in this version.

Import a supported SSF archive, check its integrity and preview the source, destination and overwrite scope. Create a fresh backup of the destination, pause orders and other writes, then type the required confirmation to apply the reviewed operation.

Supported migration updates source/destination URLs in database content, including supported serialized values. Afterward, check administrator login, pages, images and your site’s important workflows. Database restoration can replace newer orders, content and accounts; live order merging is not included.

Integrity checking is not an automatic test restore. Filesystem and database changes are not one atomic transaction, so retain the recovery point and inspect the saved report after an interruption.

Choose hourly, twice-daily, daily or weekly scheduled backup work. Retention removes older scheduled backups managed by this add-on while keeping your chosen newest minimum. Independently created manual backups are outside that retention rule.

WP-Cron depends on traffic or a real server cron, so exact-minute execution is not guaranteed. Scheduled captures are not a cross-request transactional snapshot: keep source writes quiet for consistency. Protected recovery records are retained rather than silently deleted.

Pro creates a separate password-encrypted download or off-site copy and can decrypt an encrypted SSF file before validating its import. The original local source ZIP stays unencrypted in private storage.

Keep the recovery passphrase outside the website. SSF cannot recover a lost passphrase. Scheduled encrypted transfers need a private server-side recovery-passphrase setting; the configuration file is excluded from the content archive.

Choose specific content-relative file paths from a supported archive, review the list and restore those selected files with a current destination recovery point. This Pro workflow leaves the database unchanged.

It is useful when you need to recover a known file rather than apply the full content scope. It does not automatically repair relationships between media files and database records; inspect the resulting site afterward.

Configure your own private bucket, signing region and public HTTPS endpoint. Transfers remain off until you explicitly enable that destination. Storage-provider capacity and charges are separate from the plugin plan. Your credential should have only the permissions it needs.

The connector’s streamed upload, request signature, encrypted bytes and downloaded-backup recovery have been checked through an isolated local HTTPS protocol fixture. A real provider account and its bucket permissions have not yet been verified. Test your chosen provider and a recovery copy before relying on it.

This version uses single uploads up to 5 GiB, with a transfer timeout. Multipart transfer, remote retention and an automatic provider-download workflow are not included. An upload response does not prove a later restore; inspect uncertain remote outcomes before retrying.

The downloadable Pro report identifies the backup, archive hash, size and local integrity-check result without including credentials or private filesystem paths. Optional notices alert the existing WordPress administrator email after completion or when attention is needed.

Neither an email-send attempt nor an archive-integrity result proves inbox delivery or successful website recovery. Check the actual result relevant to your workflow.

Choose updates/support coverage for 1, 5 or 20 active production websites. The implemented Pro feature set is the same across the plans. One payment covers one year; there is no automatic renewal.

Installed local tools and recovery of existing backups continue after that year. Further updates and support need an optional renewal. The site allowance concerns service-entitlement activations and does not remove GPL software rights. Update delivery is manual in this release.

Choose your plan above to purchase through Lemon Squeezy and access the Pro ZIP and customer guide from your purchase. Install Free first, then activate the separate Pro add-on. Use your purchased licence key for the plan’s updates and support entitlement.