Custom tables. Since Jetpack CRM 3.0 the data lives in wp_zbs_contacts, wp_zbs_transactions, wp_zbs_invoices, wp_zbs_quotes, and a handful of supporting tables. SleekView queries those directly. Older CRMs still on the post-type model are supported via a separate view configuration.

Yes. Custom fields are stored in wp_zbs_customfields. SleekView pivots them into proper columns so you can sort and filter on them like any core field. Date and currency types render natively, and the agent samples existing rows to discover field keys without manual schema setup.

Yes. SleekView writes through Jetpack CRM's data layer when an API is available, so logs in wp_zbs_logs and event reminders fire as expected. The audit trail stays intact even when bulk-retagging across hundreds of rows from a saved filtered view.

Each table is one view, but you can stack views inside a single SleekView page as tabs. A common setup is Contacts, Transactions, Invoices — each with its own filters and column ordering. Capability gating per role keeps each tab scoped appropriately.

Segments live in wp_zbs_segments with conditions in wp_zbs_segments_conditions. You can either rebuild equivalent filters in SleekView or join the segment tables to limit the contact view. The segment table approach keeps segment definitions in one place; the filter approach gives more flexibility per saved view.

No. SleekView paginates and indexes server-side, and the move to wp_zbs_ tables in 3.0 was specifically intended to scale past the limitations of pigeon-holing data into a custom post type. Tens of thousands of contacts with multi-condition filters render quickly.

Yes. If your install registers Jetpack CRM workflow triggers as REST endpoints or actions, SleekView exposes them as row actions. Bulk-firing a workflow across a filtered segment becomes one click. Capability gating keeps that scoped to authorized roles.

Build a SleekView page that reads the legacy post-type CRM data alongside wp_zbs_ tables, identify gaps, and use the bulk-edit row actions to populate the wp_zbs_ tables through the Jetpack CRM API. The before-and-after coverage view is itself a useful migration audit.