SleekView for WPvivid Migration
SleekView reads the WPvivid history records that already track every backup, restore, migration and remote-send, then renders action type, destination, size, duration and outcome as a column-perfect grid you can sort, filter and export.
♾️ Lifetime License available
WPvivid writes the records. The table view gives them a working surface.
WPvivid Migration writes a record for every job it runs: full backup, incremental, restore, remote-send, push migration, pull migration. Each record carries a start time, an action type, a source environment, a target environment, a destination (OneDrive, Amazon S3, Local), a byte size, a duration and an outcome. The default history page renders those records as a paginated list optimised for picking one specific job, weak at exposing cross-job patterns like a migration spike during a redesign sprint or a destination that has quietly stopped receiving work.
SleekView reads the same WPvivid history records and renders them as a real table view. Action type, destination, size, duration and outcome all become first-class columns with sort, filter and saved views. Filters compose, so a backup auditor can scope the table to migrations only, against a specific target, in the last 14 days, in a single click without leaving WP Admin.
WPvivid keeps owning the backup engine, the migration handlers and the destination wiring. The table view owns the audit surface, so failed runs, the redesign-sprint migration spike and a destination that has slipped off the schedule stop hiding inside a paginated history page.
Workflow
How SleekView surfaces WPvivid Migration data
Point at the WPvivid history
wp-content/wpvividbackups). Started timestamp, action type, source URL, target URL, destination, size, duration and outcome all become sortable, filterable columns.
Compose the columns
Filter and sort like a database
Save and gate the view
Sample columns
A typical WPvivid Migration audit view
WPvivid history records
| Started | Action | Target | Destination | Size | Outcome |
|---|---|---|---|---|---|
| 2026-05-13 02:14 | Migration | staging.studio.com | Amazon S3 | 612 MB | Success |
| 2026-05-12 02:00 | Full backup | — | OneDrive | 584 MB | Success |
| 2026-05-11 14:32 | Migration | dev.studio.com | Local | 598 MB | Failed |
| 2026-05-10 02:00 | Incremental | — | OneDrive | 48 MB | Success |
| 2026-05-09 18:07 | Remote-send | demo.studio.com | Amazon S3 | 612 MB | Slow |
Comparison
Default WPvivid admin vs SleekView
Default WPvivid history page
- History page is paginated, never exposes action type as a sortable column
- Migrations and nightly backups share the same list with no built-in separation
- Destination is visible per row but not filterable across the schedule
- Failed outcomes hide inside per-job log files instead of clustering at the top
- Sorting by duration or size requires opening every job's detail screen
SleekView
- Action type, destination, size, duration and outcome as real columns
- Filter migrations out from nightly backups in one composed query
- Inline edit on writable WPvivid fields without leaving the table
- Saved views per role: ops audit, agency review, backup auditor
- Same dataset the chart view reads, so table and dashboard stay in sync
Features
What SleekView gives you for WPvivid Migration
WPvivid history as real columns
Action type, destination, size, duration and outcome become first-class table columns instead of fields you only see one job at a time on the history page.
Composable filters across the schedule
Stack filters on action_type, destination, outcome and started date to pull failed migrations from last week, slow remote-sends or every nightly backup against a single destination.
Inline edits route through WordPress
Updates to writable WPvivid fields go through the standard WordPress save path, so WPvivid hooks fire exactly the way they would from the history page.
Audience
Who uses SleekView for WPvivid Migration
Site reliability
Filter to outcome equals Failed across every destination to triage a bad night. The dashboard table is the morning check, the WPvivid history page becomes the file picker.
Migration ops
Track migration jobs as a filtered table scoped to action_type equals Migration, so nightly backups stop blurring the cross-job picture during a redesign sprint.
Agencies
One saved audit view per client showing every WPvivid job, its action type and its outcome. Retainer reviews stop being a walk through the history page.
The bigger picture
Why WPvivid sites need a real audit table
WPvivid does two jobs unusually well for a free plugin: it backs up sites on a schedule and it migrates them on demand. The catch is that both jobs end up on the same paginated history page, which makes ops reporting noisy in a redesign sprint when migrations briefly outnumber nightly backups. The data is already in the WPvivid history records; the surface to read it as columns is just missing.
SleekView reads the same records and renders them as a sortable, filterable audit grid with action type, destination, size, duration and outcome as first-class columns. Filters compose, so a single click pulls failed migrations from the last 14 days or every nightly backup against a destination that quietly stopped receiving work.
Questions
Common questions about SleekView for WPvivid Migration
From the WPvivid job history records (option-based with per-job log files in wp-content/wpvividbackups) plus, when relevant paid extensions are active, the extended migration log. Action type, destination, size, duration and outcome are all surfaced as filterable columns.
Yes. The free WPvivid plugin already writes the records SleekView reads. The paid extensions add cloud-destination state and richer migration logs, which the table surfaces additionally when present, but the core columns work on a free install.
Yes. The action_type column distinguishes Full backup, Incremental, Migration, Restore and Remote-send. Filter to action_type equals Migration and the entire table narrows to migration work without nightly backup volume blurring the picture.
Yes. Destination becomes a column and a filter, so a backup auditor can scope the table to OneDrive only, Amazon S3 only or Local only, and confirm whether each configured destination is actually receiving work this week.
Inline edits route through the standard WordPress save path that WPvivid itself uses. Updates to writable fields fire the same hooks they would from the history page, so backup behaviour and destination wiring stay consistent.
Pagination keeps the row count constant on the page, and WPvivid history records are small per row. A site with two years of nightly backups plus ad-hoc migrations renders fast because filters compose into a single query against the underlying records.
Yes. Any filtered view exports to CSV with the same columns the table shows, so a list of failed migrations, a destination breakdown or a quarterly schedule report can land in a handover document in one step.
No. WPvivid keeps owning the backup engine, the migration handlers, the destination wiring and the history page for picking individual jobs. SleekView adds a sortable, filterable audit table on top of the records WPvivid already writes.
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