Enhanced Pivot Tables

Status: Idea Submitted

Pivot tables are one of our most used chart types in HubSpot, but they still have several frustrating limitations that force users to spend extra time in Excel or Google Sheets after every export. These are six high-impact enhancements:

1. Non-pivoting rows (show contextual data alongside pivoted data)

Current limitation: You can only have four row fields, and everything must pivot. There’s no way to display simple non-numerical data about a record (e.g. Close Date, Next Step, etc.) without sacrificing one of your actual pivot dimensions.

Proposed solution: Allow users to add “non-pivoting” data points that appear as additional columns on every unique row (similar to how Record ID works in list views). This would let us keep one row per deal/contact/company while still showing rich context.

2. Auto-fit column widths

Current limitation: Every column is forced to the exact same width, so longer text (especially Deal Name, Company Name, Notes, etc.) gets cut off.

Proposed solution: Add an “Auto-fit to content” toggle per column (or a global “Auto-fit all text columns” option) so important fields are fully readable.

3. Selective subtotals

Current limitation: Subtotals are all-or-nothing — you either subtotal every single row level or none at all. Many reports need subtotals on some groupings (e.g., by Owner or by Stage) but not others (e.g., by individual Deal Name).

Proposed solution: Let users choose which row levels should show subtotals and which should not.

4. Pagination for large pivot tables

Current limitation: When a pivot table exceeds the (undocumented) row limit, the entire chart fails to load.

Proposed solution: Automatically paginate large tables while keeping full pivot logic. Start pagination after the last complete row of the first pivot dimension so users can still see clean, usable pages instead of a blank screen.

5. Subtotals & Grand Totals in exports

Current limitation: When you export to Excel/CSV, all subtotals and the grand total disappear. Users have to manually recreate them every single time.

Proposed solution: Include subtotals and grand totals in the “Summarized” tab of every export (exactly as they appear on-screen).

6. Preserve original text formatting

Current limitation: Text properties like Deal Name, Ticket Subject, Company Name, etc. are forcibly converted to lowercase in pivot tables, making every report look informal and unprofessional. Proposed solution: Respect the original casing/formatting of all properties instead of defaulting everything to lowercase.

These six improvements would save HubSpot users hundreds of hours per year and make our exported reports look polished enough to send straight to executives and clients.

yes please. Pivot tables are like the most use report in big companies.

Agree with everything, plus it would be nice to use a different format (bold font, shaded background, etc) for the subtotal rows so it is easier to differentiate from individual data rows when reading.