Import Export Pro stores each configured job in wp_iep_jobs (with type='import' or type='export', schedule cadence, target post type, last run timestamp) and writes a history row to wp_iep_history for every cron tick. The default plugin admin tabs imports and exports separately so a unified audit view does not exist out of the box.

SleekView reads wp_iep_jobs joined to wp_iep_history as one flat workspace. The type column becomes a filter so imports and exports live in the same view but can be split by a single click. Counts for rows_created, rows_updated, rows_skipped, and rows_failed are sortable across every job regardless of direction.

Inline edits route through the plugin's save handlers where exposed, so renaming a job or toggling its scheduled flag still fires the plugin's own hooks. Direct writes fall back with conflict detection so concurrent operator and cron updates do not clobber each other.

Import-and-export plugins typically split the two directions in the UI because they evolved as separate features. That made sense when teams ran one feed in each direction. It does not scale to twenty feeds split across both.

The data is unified already: wp_iep_jobs has a single row per configured job regardless of direction, and wp_iep_history has a single row per cron tick. Splitting them in the admin is a UI choice, not a data constraint. Reading the tables directly through a flat workspace surfaces the audit questions the default UI hides: which feeds are stale across both directions, which scheduled jobs missed their last cron tick, which jobs trended toward higher failure counts week over week.

Those answers used to take a spreadsheet and a quiet hour. They become saved views once the data is treated as one queryable surface. The plugin keeps owning the import-and-export pipelines.

SleekView owns the audit layer that the UI never built.