Caldera Forms stores submissions in three tables — cf_form_entries for the entry envelope, cf_form_entry_values for the field values, and cf_form_entry_meta for IP, user agent, and add-on metadata. The default Caldera entries screen shows them per-form with a small set of columns and basic filters. Anything beyond that — joining values across fields, filtering by conditional-logic outcome, surfacing entries from multiple forms together — requires custom queries. SleekView reads the same tables directly so you build the columns you actually need, then sort by submission date or filter by field value without leaving the list.

Caldera's conditional-logic engine writes the resolved field set to the entry, so SleekView can show only the fields that were active for each submission rather than a sparse grid where most cells are empty. On forms with many conditional branches that's the difference between a usable admin view and a wall of nulls. The same applies to entries flagged as drafts (Caldera's auto-save) — they're surfaced or hidden based on a saved filter rather than mixed into the published list.

Caldera Forms has been unmaintained for some years; that doesn't make existing data go away. Many sites still rely on it for legacy submissions, archive access, or compliance retention. SleekView treats the existing schema as a stable target: it reads the tables, exposes the values, and lets you export filtered sets to CSV when migrating to a maintained form plugin. Inline edits go through Caldera's own data API where present and direct table updates where not, with audit columns recording who changed what and when.

Caldera Forms was a strong drag-and-drop form plugin in its time and many sites still rely on it for legacy submissions even though it has been unmaintained for years. The data is fine — three normalised tables, conditional logic resolved per entry, metadata for IP and user agent — but the admin surface around it is locked to one form at a time and a small set of filters. That works while you're actively building forms.

It does not work when support needs cross-form triage, compliance needs filtered exports for data-subject requests, or ops needs a clear inventory before migrating to a maintained plugin. The default Caldera entries screen shows entries per form with limited columns. Joining across forms, filtering by field value, or surfacing conditional-branch fields in a useful layout requires custom queries.

SleekView turns the same data into the workspace each team needs: support sees unreplied entries across every form, compliance filters by date and email for audits, ops inventories every entry before a migration. Same database, dramatically less custom SQL.