The Substack Importer plugin ingests a Substack archive export (the ZIP a publisher can download from Substack) and creates posts in wp_posts with the original Substack URL, publication date, and post slug captured in wp_postmeta under keys like _substack_original_url and _substack_post_id. Subscriber-list CSVs land in wp_options for later use, and the importer maintains a small redirect map so old Substack URLs route to the new WordPress post.

The default importer screen shows an upload form and a log of the last import. It doesn't expose the migrated content as a managed inventory: there's no aggregated view of which posts came from which import batch, which redirects still point at the old domain, or which Substack subscribers were resolved to WordPress users. Auditing the migration today means SQL against wp_postmeta on a custom key, or scrolling through Posts > All filtered by date.

SleekView reads the import provenance meta, the redirect map, and the cached subscriber CSV together, then joins everything to wp_posts and wp_users. Failed redirects, posts missing their Substack slug, and unresolved subscribers become row-level cohorts, and inline edits route through the importer's own update functions so the redirect map stays consistent.

Substack migrations look like one-time data transfers in the install wizard but behave like long-running projects in practice. The archive export lands hundreds of posts in wp_posts, each with provenance meta and a redirect map, plus a subscriber CSV that has to resolve to WordPress users. Some posts come in as drafts because the importer can't confidently match a cover image; some redirects fail silently because the original Substack URL was rewritten between the export and the import; some subscribers don't match any existing WP user.

The plugin's own admin tops out at an import log because that's the most useful surface during ingestion, but it's the wrong surface for the weeks of cleanup that follow. SleekView lifts the resulting state into a row-level workspace with redirect health, batch grouping, and subscriber resolution joined inline, so the migration becomes a finishable project rather than a forever-stalled cleanup queue. For publishers leaving Substack, that workspace is what makes the move auditable and the archive feel native rather than imported.