SleekView for WP Time Capsule Migration
SleekView reads the WP Time Capsule run records that already track every incremental backup, restore and migration to Google Drive, Dropbox, Amazon S3 and Wasabi, then renders type, destination, diff size, duration and outcome as a column-perfect grid.
♾️ Lifetime License available
The calendar picks a date. The table answers the audit question.
WP Time Capsule's signature UI is the calendar view: every nightly incremental snapshot rendered as a dot on a timeline, perfect for picking a date to restore from. The calendar is excellent at one job and weak at another. It cannot tell a team how many migrations completed this month, which destinations they shipped to, or which incrementals drifted past 20 minutes across a quarter. The data is already in WP Time Capsule's run records; the surface to read it as columns is just missing.
SleekView reads the same WP Time Capsule run records and renders them as a real table view. Started timestamp, type, destination, changed files, diff size, duration and outcome all become first-class columns with sort, filter and saved views. Filters compose, so a backup auditor can pull every failed run against Wasabi in the last 14 days in one click without opening individual snapshot detail.
WP Time Capsule keeps owning the incremental engine, the calendar view and the destination wiring. The table view owns the audit surface, so failed runs, oversized diffs and the destination that quietly stopped receiving work stop hiding between green dots on the calendar.
Workflow
How SleekView surfaces WP Time Capsule run records
Point at the run records
Compose the columns
Filter and sort like a database
Save and gate the view
Sample columns
A typical WP Time Capsule audit view
WP Time Capsule run records
| Started | Type | Destination | Changed files | Diff size | Outcome |
|---|---|---|---|---|---|
| 2026-05-13 02:14 | Incremental | Wasabi | 412 | 48 MB | Success |
| 2026-05-12 14:02 | Migration | Amazon S3 | 12 184 | 612 MB | Success |
| 2026-05-12 02:14 | Incremental | Wasabi | 1 207 | 184 MB | Slow |
| 2026-05-11 02:14 | Incremental | Google Drive | 298 | 38 MB | Failed |
| 2026-05-10 02:14 | Incremental | Dropbox | 344 | 42 MB | Success |
Comparison
Default WP Time Capsule admin vs SleekView
Default WP Time Capsule calendar
- Calendar is great for picking a restore date, weak for cross-run audit
- No way to filter by destination plus outcome in a single composed query
- Diff size and changed-file count hide behind individual snapshot detail
- Failed runs stay buried between green dots instead of clustering at the top
- Sorting runs by duration across months needs manual log work
SleekView
- Type, destination, diff size, duration and outcome as real columns
- Filter incrementals out from migration runs in one composed query
- Inline edit on writable WP Time Capsule fields without leaving the table
- Saved views per role: ops audit, agency review, on-call cockpit
- Same dataset the chart view reads, so table and dashboard stay in sync
Features
What SleekView gives you for WP Time Capsule Migration
WP Time Capsule runs as real columns
Type, destination, changed files, diff size, duration and outcome become first-class table columns instead of fields hidden behind individual calendar dots.
Composable filters across the schedule
Stack filters on destination, type, outcome and started date to pull failed runs against Wasabi, slow incrementals over 20 minutes or every migration run during a deploy window.
Inline edits route through WordPress
Updates to writable WP Time Capsule fields go through the standard WordPress save path, so plugin hooks fire exactly the way they would from the calendar view.
Audience
Who uses SleekView for WP Time Capsule Migration
Site reliability
Filter to outcome equals Failed across Google Drive, Dropbox, Amazon S3 and Wasabi to triage a bad night. The audit table is the morning check, the calendar becomes the restore tool.
Migration ops
Track migration runs as a filtered table scoped to type equals Migration, so nightly incrementals stop blurring the cross-run picture during a deploy window.
Agencies
One saved audit view per client showing every incremental and every migration run with its destination and outcome. Retainer reviews stop being a walk through the calendar grid.
The bigger picture
Why incremental schedules need a real audit table
WP Time Capsule built its UI around the calendar because the calendar is the right tool for one of the two jobs an incremental backup tool has to do: picking a restore date. The second job, telling a team how the schedule is performing across a quarter, is where the calendar runs out of headroom. The data is already in WP Time Capsule's run 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 type, destination, diff size, duration and outcome as first-class columns. Filters compose, so a single click pulls failed runs against Wasabi or every migration during a deploy window, and the calendar stays the right tool for picking a restore date.
Questions
Common questions about SleekView for WP Time Capsule Migration
From the WP Time Capsule run records in the plugin's own tables and option entries, plus its log files where they are still present. Started timestamp, type, destination, changed files, diff size, duration and outcome are all surfaced as columns.
No, the two complement each other. The WP Time Capsule calendar stays excellent for picking a snapshot date to restore from, and the audit table stays excellent for cross-run reporting. Most teams keep the calendar open during a restore and the table open during the morning ops check.
Yes. WP Time Capsule supports Google Drive, Dropbox, Amazon S3 and Wasabi, and all four write the same run-record schema. SleekView surfaces them as filterable values on the destination column, so a single table can compare all four side by side.
Yes. The type column distinguishes Incremental, Migration and Restore. Filter to type equals Migration and the entire table narrows to migration work without nightly incremental volume blurring the picture during a deploy window.
Yes. Diff size is a sortable, filterable column. A storage ops view typically filters to diff size greater than 100 MB and sorts by started date to spot the runaway plugin update or media import that added unexpected weight to an incremental run.
Inline edits route through the standard WordPress save path that WP Time Capsule itself uses. Updates to writable fields fire the same hooks they would from the plugin's own screens, so incremental scheduling and destination wiring stay consistent.
Yes. Any filtered view exports to CSV with the same columns the table shows, so a list of failed runs, a destination breakdown or a quarterly schedule report can land in a handover document in one step.
No. WP Time Capsule keeps owning the incremental engine, the calendar view and the destination wiring. SleekView adds a sortable, filterable audit table on top of the run records the plugin 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