Backup Migration (by Migrate, formerly BackupBliss) is widely used because it gets the basics right: one-click backup, one-click migration, a single archive file written to /wp-content/backup-migration. The admin screen lists the archives with a download link and a manual run button. That list answers 'do I have a backup?' but not 'are backups still happening on the schedule I set up six months ago?' or 'has migration ever failed silently on this stack?'

SleekView Charts reads the archive manifest and the wp_options job entries Backup Migration writes for each run. A Number card surfaces total successful runs in the last 30 days. A Pie splits jobs across backup, migration-prep and restore. A Bar groups archive size per month so trend lines for the dataset itself become visible. An Area trends scheduled runs over time so a stalled CRON becomes a chart break, not a silent gap.

The chart view and table view share the same dataset. Filter to runs over 500 MB or to runs flagged Slow, and both surfaces narrow together. Same plugin doing the work, much better visibility into what it has been doing.

Backup Migration's combined positioning (backup and migration in one plugin) is a real strength: one tool, one archive format, one screen. The cost of that simplicity is that the screen has to serve two very different audiences. Site admins want to know whether the schedule still fires.

Migration leads want to know whether the next archive will be tractable on the destination host. The default UI offers a list that half-answers both questions and fully answers neither. Charting the same data fixes that.

The admin reads the KPI card and the cadence trend. The migration lead reads the size-per-month bar and the type pie. Both surfaces sit on the same job log Backup Migration is already writing, and both replace a manual scroll with a glance.