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 status, the byte size, and the run duration. The Packages screen lists those rows page by page with file-management actions next to each one. Useful for finding a specific archive to restore from. Useless for asking which target environments saw the most migrations this quarter or how long the average prod-to-staging clone has been taking.

SleekView Charts reads the same table directly. A Number card counts completed migrations in the last 30 days. A Pie splits jobs by destination so ops can see whether Google Drive or S3 dominates the schedule. A Bar groups jobs by status (Complete, Failed, Throttled) so a failure cluster is visible at a glance instead of buried mid-list. An Area trends duration over time, which is the chart that catches a clone slowly creeping from 9 minutes to 22 minutes before the schedule actually breaks.

Because the cards read wp_duplicator_packages directly, no second history store is involved. The recovery-point flag, the installer-status flag and the destination field all surface as filterable dimensions. Save a view called Migration health and the morning ops check becomes a glance at four cards rather than a paginated walk through the Packages screen.

Duplicator Pro is one of the most-used migration tools in WordPress, and the Packages screen does file management well. It is a poor instrument for understanding the schedule across a month or a quarter. A paginated list cannot answer how many migrations completed, where they went, or whether the average duration is drifting upward.

Those are aggregate questions, and they only have aggregate answers. A Number card pins the volume. A pie splits destinations honestly.

A bar separates Complete from Failed without scrolling. An Area trend catches the slow regression weeks before the schedule breaks. The Packages screen and the chart cards read the same wp_duplicator_packages rows; the difference is the question each surface is built to answer.