MailerLite Classic is the WordPress plugin built against MailerLite's pre-2022 platform. New sites have moved to the modern MailerLite or MailerLite Pro plugin, but plenty of long-lived sites still run Classic because the migration to the new platform requires touching API keys, group IDs and consent strings, and nobody wants to break a working capture path. The local footprint is small but consequential: a legacy API key in wp_options as a serialized array, per-form group mappings in wp_postmeta, and a small set of sync timestamps that the plugin updates on each capture.

The default Classic plugin UI is era-appropriate: single-form mapping screens, no inventory view, no filter for forms whose target group no longer exists in MailerLite, no diff between staging and production capture configs. Sites that have been live for several years often accumulate stale mappings, orphaned consent overrides and disabled capture flags that nobody remembers setting. There is no admin surface that turns those rows into a workspace.

SleekView reads the Classic plugin's option row and postmeta directly and renders the integration as one table. Settings on top, form-bridge rows in the middle, with consent text, last-sync timestamp and a status pill on every row. Edits route through the plugin's options API where supported. For sites planning a migration to the new MailerLite plugin, the audit table is also the migration plan, an inventory of every mapping that needs to be moved and every group ID that needs to be repointed.

Legacy WordPress plugins are the easiest place for drift to hide because nobody's actively looking at them. A site that picked MailerLite Classic in 2018 might have ten form bridges, two consent overrides nobody remembers writing, an API key that still works but was issued under a deprecated format, and three group IDs that were archived in MailerLite years ago without anyone updating the WordPress side. None of that is visible from the Classic admin because the admin was designed for the small operational footprint a Classic install was supposed to have.

SleekView's contribution is to render every storage path as a column on one table, which is exactly the audit a legacy install needs. Once the audit table exists, stale rows show as red or amber and fixes become bulk edits. For owners deciding whether to migrate to the modern MailerLite plugin, the table is the prerequisite.

For agencies inheriting old sites, it's the day-one kickoff document. For privacy teams reviewing compliance on long-lived sites, it's the proof that the consent string actually shown to the user is the one currently stored on the form. None of that work disappears because the plugin is legacy.

SleekView just makes it tractable.