WP Migration Duplicator records every clone it builds with source URL, target URL, destination, status, byte size and duration. The clone list screen renders that history as a paginated table with file actions next to each row. Useful for picking an archive to restore from. Useless for asking how many clones the team built this quarter, where they went, or how long the average run is taking.

SleekView Charts reads the same records directly. A Number card counts completed clones in the last 30 days. A Pie splits jobs by target environment so prod-to-staging against staging-to-dev against ad-hoc demo clones becomes a visible mix. A Bar groups jobs by status so a Failed cluster surfaces immediately instead of hiding between successful runs. An Area trends duration so a clone slowly drifting from 8 minutes to 17 minutes triggers a conversation before the schedule actually breaks.

Because the dashboard reads the same job records the clone list uses, no second history store is involved. The destination column, the status column and the size column all stay filterable. Save a view called Clone health and the morning check on the migration schedule becomes a glance at four cards rather than a click-through of every recent package.

A clone list is a file picker. It is excellent for finding the archive to restore from and bad at telling a team how the migration schedule is performing across a month or a quarter. A KPI of clones in the last 30 days pins the volume.

A pie of target environments separates staging clones from dev clones from ad-hoc demo work. A bar of status keeps failures visible instead of letting them hide between successful runs. An Area trend of duration catches the slow regression that turns a 8-minute job into a 17-minute job over six weeks.

Same records WP Migration Duplicator already writes; the chart cards just answer the schedule-shaped questions a paginated list cannot.