Yes. SleekView Charts reads cf_form_entries, cf_form_entry_values, and cf_form_entry_meta directly. The schema does not change once the plugin stops getting updates, so the dashboard keeps working as long as those tables exist on your site.

Yes. The default groupings include form_id, so a single dashboard rolls up every form on the site. Filter to one form when you need that detail, but the rollup is the value the per-form admin never offered.

Caldera writes only the values for fields that were active under the logic for that submission. When charting by field value, rows where the field did not fire simply do not contribute to that group. Predictable and consistent.

Yes. Any aggregated chart exports as CSV with the same grouping the chart uses. Useful for migrations, audit responses, or sending a summary to a colleague.

No. The dashboard is read-only over the database tables. Caldera's submission flow, email notifications, and integrations all continue exactly as before. SleekView Charts only adds a reporting layer on top.

Queries hit indexed columns on cf_form_entries (entry ID, form ID, date_created, user ID) directly. Field-value aggregations join cf_form_entry_values scoped to the columns the dashboard uses. Long compliance archives stay responsive.

If your Caldera install collected payment data via an add-on writing to cf_form_entry_meta, yes. The dashboard joins meta and charts payment status, amount, or gateway as needed.

Yes. The Bar card ranks forms by entry count, the Donut shows the mix, and the Number gives the total. Migration plans start with the forms that carry the data and skip the ones with five entries from 2018.