✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView for Duplicator Pro

SleekView reads the wp_duplicator_packages rows Duplicator Pro already writes per migration and renders the source URL, target URL, destination, status, size and duration as a column-perfect grid you can sort, filter and export from WP Admin.

♾️ Lifetime License available

SleekView table view for Duplicator Pro

Duplicator stores the rows. The table view gives them a working surface.

Duplicator Pro records every migration in wp_duplicator_packages with the source URL, the target environment, the destination (Local, Google Drive, Dropbox, Amazon S3, OneDrive, FTP), the package status, the byte size and the run duration. The Packages screen renders those rows as a paginated list optimised for file management: download archive, rebuild installer, delete package. Useful for picking an archive to restore from, weak for asking which target environments saw the most migrations this quarter or which packages failed last week.

SleekView reads the same wp_duplicator_packages rows and renders them as a real table view. Source URL, target URL, destination, status, size and duration all become first-class columns with sort, filter and inline edit on the writable fields. Filters compose, so an ops lead can pull every failed package against an S3 destination in the last 14 days in one click without opening a single log file.

Duplicator Pro keeps owning the archive build, the installer and the destination handlers. The table view owns the audit surface, so failed jobs, stale packages and the redesign-sprint migration spike stop hiding inside a paginated list.

Workflow

How SleekView surfaces Duplicator Pro data

1

Point at the Duplicator records

Pick wp_duplicator_packages. Created timestamp, source URL, target URL, destination, status, package size, run duration, the recovery-point flag and the installer-status flag all become sortable, filterable columns.
2

Compose the columns

Drag in Created, Source URL, Target URL, Destination, Status, Size, Duration, Recovery point and Installer status. Reorder, hide or rename any column without touching the database or a custom-column callback.
3

Filter and sort like a database

Filter to destination equals S3 and status equals Failed to pull the cluster a triaging engineer needs first. Sort by duration to find the slow clones, or by created to scope the table to the last 14 days.
4

Save and gate the view

Name the view ("Migration audit", "Failed packages last 14 days", "Recovery points only") and gate it by WordPress capability so ops, agency leads and on-call engineers each land on the slice they need.

Sample columns

A typical Duplicator Pro audit view

Duplicator package rows joined with destination and status metadata, rendered as a sortable audit grid. The same dataset that drives the Packages screen now drives a cross-package table.
Source: wp_duplicator_packages
Created Target URL Destination Status Size Duration
2026-05-12 staging.studio.com Amazon S3 Complete 412 MB 8m 14s
2026-05-10 dev.studio.com Google Drive Complete 398 MB 9m 02s
2026-05-09 staging.studio.com Amazon S3 Failed 2m 41s
2026-05-08 demo.studio.com Dropbox Throttled 407 MB 22m 18s
2026-05-07 staging.studio.com Local Complete 415 MB 7m 49s

Comparison

Default Duplicator Pro admin vs SleekView

Default Duplicator Pro admin

  • Packages screen is built for file actions, not for cross-package audit
  • No way to filter by destination plus status in a single composed query
  • Source and target URLs are visible per row but not sortable as columns
  • Recovery-point and installer-status flags hide inside individual package detail
  • Sorting packages by duration or size requires manual SQL against wp_duplicator_packages

SleekView

  • Source URL, target URL, destination, status, size and duration as real columns
  • Filter by destination, status and recovery-point flag in one composed query
  • Inline edit on writable Duplicator Pro 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 Duplicator Pro

wp_duplicator_packages as real columns

Source URL, target URL, destination, status, size and duration become first-class table columns instead of fields you only see one package at a time.

Composable filters across the schedule

Stack filters on destination, status, recovery point and created date to pull failed S3 jobs from last week, slow clones over 15 minutes or every recovery-point package in one go.

Inline edits route through WordPress

Updates to writable Duplicator Pro fields go through the standard WordPress save path, so Duplicator hooks fire exactly the way they would from the Packages screen.

Audience

Who uses SleekView for Duplicator Pro

Site reliability

Filter to status equals Failed across all destinations to triage a bad night. Recovery-point packages get their own saved view for on-call engineers during a deploy window.

Migration ops

Track prod-to-staging clones as a filtered table scoped to a single target URL, with size and duration columns surfaced for the schedule review.

Agencies

One saved audit view per client showing every migration package, its destination and its outcome. Retainer reviews stop being a walk through the Packages screen.

The bigger picture

Why Duplicator Pro sites need a real audit table

Duplicator Pro is one of the most-used migration tools in WordPress, and the Packages screen does file management well. It was never designed to answer cross-package questions: which destinations are carrying the schedule, which packages failed this week, which clones are drifting slower over time. The data is already in wp_duplicator_packages; the surface to read it as columns is just missing.

SleekView reads the same rows and renders them as a sortable, filterable audit grid with source, target, destination, status, size and duration as first-class columns. Filters compose, so a single click pulls failed S3 jobs from the last 14 days or every recovery-point package, and the schedule review stops being a walk through paginated file rows.

Questions

Common questions about SleekView for Duplicator Pro

Directly from wp_duplicator_packages, the table Duplicator Pro writes per migration. Created timestamp, source URL, target URL, destination, status, package size, run duration, the recovery-point flag and the installer-status flag are all surfaced as columns.

 

Both. The free Duplicator plugin writes the same wp_duplicator_packages schema with a smaller destination set, so the table works against both editions. Pro-only fields like the recovery-point flag and the extended destination list are surfaced additionally when present.

 

Yes. Filters compose, so a query like destination equals Amazon S3 and status equals Failed and created in the last 14 days resolves to a single SQL statement against the indexed columns on wp_duplicator_packages.

 

Yes. Source URL and target URL become first-class columns, so a content lead can sort the table by target URL to group every package that shipped to staging or dev, without opening per-package detail.

 

Inline edits route through the standard WordPress save path that Duplicator Pro itself uses. Updates to writable fields fire the same hooks they would from the Packages screen, so installer behaviour and destination wiring stay consistent.

 

Queries hit indexed columns on wp_duplicator_packages (created timestamp, status, destination). Pagination keeps the row count constant on the page, so even sites with two years of nightly recovery points and ad-hoc migrations render fast.

 

Yes. Any filtered view exports to CSV with the same columns the table shows, so a list of failed packages, a destination breakdown or a quarterly schedule report can land in a handover document or a renewal review in one step.

 

No. Duplicator Pro keeps owning the archive build, the installer, the destination handlers and the Packages screen for file actions. SleekView adds a sortable, filterable audit table on top of the rows Duplicator Pro 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.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

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