SleekView for Backup Migration
Backup Migration ships archives to /wp-content/backup-migration and writes a job entry in wp_options for each run. SleekView reads that history and renders backups and migration-prep runs as a sortable, filterable grid.
♾️ Lifetime License available
Backups and migrations on one operational surface
Backup Migration (by Migrate, formerly BackupBliss) does a job a lot of WordPress sites need at the same time: one-click backup and one-click migration, both producing a single .zip archive under /wp-content/backup-migration. The plugin records each run in wp_options with status, started_at, duration, size_bytes, and a flag for whether the run was a backup or a migration-prep build. The default admin lists those archives with a download button and a manual trigger, which is the right surface for grabbing the latest copy and the wrong surface for asking which migration-prep build is on schedule for next week's cutover.
SleekView reads the same job log and reconciles it with the archive manifest on disk. Each row carries the started_at timestamp, the run type (Backup or Migration), the trigger (Scheduled or Manual), the archive size, the duration, and the outcome. A 1.4 GB scheduled backup sitting next to a 1.6 GB manual migration-prep run gives the migration lead a defensible number to bring to a cutover meeting instead of a guess based on the latest archive size.
Saved filters carry across both surfaces. Filter to type equals Migration in the last 14 days and the same filter narrows the chart view in SleekView Charts. The plugin keeps doing the backups and migrations; SleekView turns the result into a queryable record the whole team can read.
Workflow
From an archive folder to a real backup grid
Read the job log
Map the columns
Save the migration window
Drill into the archive
Sample columns
Backup and migration runs
wp_options job entries written by Backup Migration and .zip archives in /wp-content/backup-migration
| Started | Type | Trigger | Size | Duration | Outcome |
|---|---|---|---|---|---|
| 2026-05-15 02:30 | Backup | Scheduled | 1.4 GB | 8m 12s | Success |
| 2026-05-14 14:08 | Migration | Manual | 1.6 GB | 11m 02s | Success |
| 2026-05-13 02:30 | Backup | Scheduled | 1.4 GB | 14m 47s | Slow |
| 2026-05-12 02:30 | Backup | Scheduled | 0 MB | 4s | Failed |
| 2026-05-11 02:30 | Backup | Scheduled | 1.4 GB | 8m 02s | Success |
Comparison
Default Backup Migration admin vs SleekView
Default Backup Migration
- Archive list mixes backups and migration-prep runs without filters
- Cannot isolate scheduled runs from manual triggers
- No saved view for failed or slow runs over a rolling window
- Duration is not surfaced on the default archive screen
- No queryable record for migration-cutover audits
SleekView
- One row per run with type, trigger, size, and duration
- Filter to migration-prep runs in the last 30 days
- Filter to scheduled vs. manual to audit automation health
- Saved view for failed runs in the last 7 days
- Same filters apply across SleekView and SleekView Charts
Features
What SleekView gives you for Backup Migration
Migration cutover audit
Filter the grid to type equals Migration in the project window and the row history becomes a defensible record for a cutover review. No screenshots of an archive list.
Scheduled vs. manual
Filter by trigger to separate the runs the schedule produced from the runs an admin clicked. Useful when automation seems healthy but the actual cadence is being kept up by ad-hoc clicks.
Failure feed
A saved view of failed and slow runs in the last week catches the night the scheduled backup ended in four seconds with a zero-byte archive.
Audience
Who uses SleekView for Backup Migration
Migration leads
Track migration-prep cadence and average archive size in the weeks before a cutover. The grid replaces 'we are probably around 1.5 GB' with a row history the destination host can be briefed against.
Agencies
Roll out the same backup-and-migration grid across every Backup Migration install in the client portfolio. Each retainer review opens with the same saved filters.
Site admins
Confirm the schedule is firing without scrolling the archive screen. A glance at the grid answers 'is everything green this week?' in one sortable view.
The bigger picture
Why backup and migration data wants to live on one surface
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 audiences with different questions. Site admins want to know whether the nightly schedule is still firing.
Migration leads want to know whether the next archive is going to be tractable on the destination host. The default UI offers a flat list that half-answers both questions and fully answers neither. SleekView splits the difference by giving both audiences a queryable grid on the same dataset.
The admin reads the failure-feed filter. The migration lead reads the type and size columns. Same job log, same archives, two saved views that finally answer the right questions for each role.
Questions
Common questions about SleekView for Backup Migration
No. Backup Migration owns the schedule, the archive build, and the migration handoff. SleekView reads the job log Backup Migration writes and renders it as a grid. The destructive operations stay behind the plugin's own UI, where they belong.
From the wp_options entries Backup Migration writes for each run (status, started_at, duration, size_bytes, type, trigger) and the .zip archives in /wp-content/backup-migration. No premium add-on or external logger is involved.
Yes. The type column is filterable, so isolating migration-prep builds from scheduled backups is one click. That filter is the foundation of any cutover audit, because the migration narrative wants only the runs that fed the destination handoff.
Yes. Backup Migration writes the same job entries regardless of plan, and SleekView reads what is already present. There is no premium dependency on the Backup Migration side and no separate logging integration required.
Yes. Each job entry carries a trigger flag for whether it was fired by the schedule or by an admin clicking Run. The trigger column makes that split immediately visible, which catches the case where automation looks healthy but the cadence is actually being kept up by manual clicks.
Yes. Backup Migration writes per-site job entries, and SleekView respects that scope. On multisite each subsite has its own grid, and a network-level view can roll runs up across blogs when one ops team monitors the whole network.
No. Only the rows on the current page are queried, and the wp_options entries are small. A site with eighteen months of nightly history queries the same as a site with two weeks because pagination keeps the row count constant.
Yes. Filter to type equals Migration in the project window and export the grid to CSV. The export is the cutover audit, ready to drop into a project doc without manually retyping archive sizes.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout