WP All Export Pro layers FTP, HTTP, and S3 destinations on top of the Free engine but persists everything inside pmxe_exports. The destination config sits in the options column as serialized data; the schedule cadence in scheduled; the most recent file in the attch_id link to the media library. The plugin admin still presents each export as a card with a settings tab.

SleekView reads pmxe_exports directly. Pro fields stored serialized in options are parsed into named filterable columns: destination type, host, target path. Schedule cadence, last run, and exported row count become first-class sortable columns. The view turns the operational question "which feeds shipped to which partner" into a one-screen answer.

A second view joins attch_id to wp_posts so each export row exposes the URL of its most recent CSV or XML. Integrations teams stop digging through wp-content/uploads when finance asks for last Tuesday's customer feed.

Pro destinations are easy to add and hard to retire. The plugin lets a team wire FTP, HTTP, and S3 endpoints in minutes; the default admin gives no equally fast way to inventory those endpoints later. Three years in, a typical install has feeds shipping to an ERP that was replaced, a partner FTP whose credentials are revoked, an S3 bucket from a 2022 spike test.

None of them throw errors visible from the card grid. Reading pmxe_exports directly with the serialized options column parsed into named columns turns destination audit into a one-screen operation. Filter on host equals the churned-partner domain.

Filter on target path matches the deprecated S3 prefix. Sort by registered_on ascending to see the oldest configurations first. Once that visibility exists, deprecating dead feeds becomes a monthly twenty-minute task instead of a discovery exercise no one schedules.

Stale-export cleanup is the rare maintenance habit that lowers both attack surface and cron load in the same pass, and it only works when the inventory is queryable.