Documentation

StifLi Backup Tools documentation for WordPress backup, restore and migration workflows.

Use this guide to install the plugin, create a reliable backup strategy, connect remote storage, restore safely, move sites and maintain WordPress installations with less operational risk.

Installation Create a backup Remote destinations Restore workflow Migration and staging Security and privacy

Installation

Install StifLi Backup Tools from your WordPress dashboard or by uploading the plugin ZIP. After activation, open the plugin screen in the WordPress admin area and review the default configuration before running your first backup.

Open Plugins > Add New in WordPress.
Search for StifLi Backup Tools or upload the plugin ZIP.
Activate the plugin.
Open the StifLi Backup Tools admin page.
Review backup components, storage location, retention and notification settings.

Recommendation: create a manual full backup immediately after installation so you can confirm the plugin works correctly on your hosting environment.

Create a Backup

A manual backup is the fastest way to confirm that your site can be archived successfully. For most sites, start with a full backup that includes WordPress files, uploads, plugins, themes and the database.

Choose components

Select a full site backup, database-only backup, uploads, plugins, themes or a custom component set.

Run the backup

Start the backup and keep the admin page open until the process confirms completion or moves to background processing.

Verify the archive

Check that the backup appears in the backup list and, if remote storage is configured, confirm the remote copy exists too.

Scheduled Backups

Scheduled backups are designed for recurring protection. Configure the frequency, components, destinations and retention policy according to how often your site changes.

Site type	Suggested schedule	Notes
Static business site	Weekly full backup	Add a manual backup before major updates.
Blog or content site	Daily database, weekly full backup	Useful when content changes often but files change less frequently.
WooCommerce or membership site	Frequent database backups	Use a remote destination and conservative retention rules.
Development or staging site	Before deployment or testing	Create a manual backup before running risky experiments.

All Features

Full backups

Archive WordPress files and database content for complete recovery workflows.

Database backups

Create lighter database-only backups for content-heavy sites and pre-update snapshots.

Differential backups

Reduce recurring backup size by storing changes between full backup runs.

Selective restore

Restore the full site or specific components such as database, uploads, plugins or themes.

Remote storage

Send backup archives to external storage providers so the only copy is not on the same server.

Migration and staging

Move a site to a new domain or create a staging copy for safer testing.

Remote Destinations

Remote destinations keep backups outside the web server. This is important because local-only backups can disappear if the hosting account is damaged, suspended or deleted.

Google Drive

Store backup archives in a Drive folder selected during configuration.

Configure Google Drive

Dropbox

Use Dropbox as an off-site backup destination with folder-level organization.

Configure Dropbox

Amazon S3

Connect to AWS S3 buckets for scalable object storage.

Configure Amazon S3

S3-compatible storage

Use compatible providers such as Backblaze B2, Wasabi, MinIO or DigitalOcean Spaces.

Configure S3-compatible storage

FTP

Send backups to a remote FTP server when provided by your hosting or infrastructure stack.

Configure FTP

SFTP

Use encrypted file transfer for servers that expose secure SSH-based storage access.

Configure SFTP

Restore Workflow

Restores should be handled carefully. Before restoring production data, confirm the backup date, the selected components and whether the restore will overwrite files, database tables or both.

Open the backup list and select the archive you want to use.
Review the backup type, creation date and included components.
Choose full restore or selective restore.
Confirm the restore action and wait for completion.
Clear caches and verify the front end, admin area, forms and critical workflows.

Safe practice: if the site is business-critical, test restore on staging before restoring production.

Migration & Staging

Migration workflows help move a WordPress site between domains, hosts or environments. Staging workflows help create a copy of the site where updates and experiments can be tested before touching production.

Domain migration

Use a backup package and URL replacement workflow when moving a site to a different domain.

Server migration

Transfer a backup to the new host, restore it, then verify file permissions, permalinks and PHP settings.

Staging copy

Create a copy in a subdirectory or separate environment to test updates without risking the live site.

Retention & Exclusions

Retention rules prevent backup storage from growing forever. Exclusion rules keep cache folders, temporary files, logs and unnecessary directories out of backup archives.

Keep more restore points for active sites and fewer for static sites.
Exclude cache directories, temporary folders and generated files when they are not required for restore.
Use separate retention policies for local and remote backups when possible.
Periodically check storage usage on both the WordPress server and remote destinations.

Maintenance Tools

Backup strategy works best when the site is kept clean. StifLi Backup Tools includes maintenance utilities for common WordPress housekeeping workflows.

Database cleanup

Clean revisions, spam comments, transients and table overhead where appropriate.

Temporary file cleanup

Remove generated temporary files that do not need to be archived long-term.

Image optimization

Reduce media weight where supported by the current hosting environment and plugin configuration.

Logs & Reports

Use logs to diagnose incomplete backups, permission problems, remote upload errors, memory limits and timeout-related issues. For scheduled backups, configure notifications so failures do not go unnoticed.

Review the latest backup log after changing settings.
Use system information to check PHP limits and server capabilities.
Enable email or webhook notifications for scheduled backup status.
Keep failure messages when requesting support, because they usually point to the exact bottleneck.

Security & Privacy

Backups can contain sensitive data, including user records, order data, private content, API keys stored in WordPress settings and uploaded files. Treat backup archives with the same care as production data.

Use remote destinations you control and trust.
Limit access to backup files and remote storage credentials.
Delete old backups that are no longer needed.
Do not share backup archives through public links.

Privacy model: external services are only contacted when you configure and enable a feature that uses them, such as remote storage, webhooks or site-to-site workflows.

FAQ

Should I keep local backups?

Local backups are useful for quick restores, but at least one remote destination is recommended for real disaster recovery.

Can I restore only part of a site?

The plugin is designed around selective restore workflows, so you can restore specific components when a full restore is unnecessary.

How often should I schedule backups?

Match the schedule to site activity. Sites with orders, bookings or frequent content changes need more frequent database backups.

What should I test first?

Create a manual full backup, confirm the archive exists, send it to remote storage and test a restore on staging when possible.