WPvivid Migration Pro persists most of its state inside wp_options. Backup file metadata sits under wpvivid_backup_list, remote storage configuration under wpvivid_remote_storage, and schedule definitions in their own option keys. The default plugin UI surfaces those as separate panels, which works well for a single install but limits portfolio-wide audits across many client sites.

SleekView reads the backup-list option directly and unpacks each backup into a row with filename, size, creation timestamp, type (full, database-only, files-only), and the linked remote destination. Joining to wpvivid_remote_storage surfaces destination type (Dropbox, Google Drive, OneDrive, Amazon S3, FTP, Backblaze B2) as a sortable column.

Edits to backup metadata route through the plugin's option setters where available. Remote storage credentials remain encrypted; SleekView never decrypts or exposes them, surfacing only the destination type, label, and configuration timestamp for audit purposes.

WPvivid Migration Pro is popular precisely because its remote-storage support is easy to set up: connect Google Drive, Dropbox, S3, or Backblaze B2 once and walk away. The setup-once design works well until OAuth tokens expire, until a cron run drifts past its window, or until a junior staffer creates a local-only backup that never gets pushed offsite. None of those failures show up loudly in the default plugin UI.

Reading wpvivid_backup_list directly turns each into a column. Last-backup age, remote destination, upload status, and backup type all become sortable across the entire agency portfolio. Expired auth surfaces as a filter rather than a midnight 500 page.

Local-only backups become a quickly-visible audit rather than a discovery during an actual restore request. Once the habit exists, backup hygiene becomes a five-minute morning routine instead of a quarterly audit project, and the gap between scheduled and actually-uploaded closes from days to minutes.