Duplicator Pro is one of the few WordPress migration tools that uses dedicated custom tables rather than serialized options. Package metadata lives in duplicator_pro_packages, storage destinations in duplicator_pro_storage, and run history is captured per-package as status and timestamp columns. That custom-table footprint is what makes Duplicator Pro genuinely auditable at scale, even though the default plugin UI surfaces it one package at a time.

SleekView reads duplicator_pro_packages directly and exposes package name, size, creation timestamp, source URL, and the linked storage destination ID as sortable columns. A second view joins to duplicator_pro_storage so the destination type (local, Amazon S3, Dropbox, Google Drive, OneDrive, FTP) becomes a first-class column, not a hidden reference.

Inline edits route through the plugin's package and storage classes where setters exist. Direct table writes are capability-gated and always capture a rollback snapshot, since the plugin's restore engine reads these tables on every package operation.

Most WordPress migration plugins serialize their state into wp_options because it's the path of least resistance. Duplicator Pro deliberately doesn't, and that architectural decision pays off the moment a portfolio gets large. Reading duplicator_pro_packages with proper indexes is fast even at thousands of packages, where a serialized option blob would have to be unpacked and re-serialized on every read.

SleekView leans on that custom-table footprint to make portfolio-wide audits actually viable. Stale packages on local storage become a filter, not an investigation. Destination drift across many clients becomes a single column.

Schedule failures surface in the same workspace as failed builds. Agencies that adopted Duplicator Pro for its restore reliability get the secondary benefit of a real audit surface, which the default plugin UI never exposes because it was built for single-install operators. Once that audit habit exists, package hygiene becomes a fifteen-minute weekly task rather than an annual deep-clean that nobody wants to schedule.