Hub for teams replacing Heap, now part of Contentsquare, with PostHog: session-based plans, data history limits, Heap Connect as the export path, and the migration, comparison and cost pages under it.
Heap against PostHog for product analytics: Heap's autocapture and retroactive virtual events versus PostHog's autocapture and actions, session-based versus event-based pricing, the Contentsquare roadmap question, and PostHog Cloud versus self-hosting.
Moving from Heap to PostHog using PostHog's documented Heap guide: exporting through Heap Connect or a one-time JSON export, querying per-event tables, converting events and users, aliasing identities, and the Heap plan you need to get the data out.
Heap's unpublished, session-based pricing and Heap Connect add-on against PostHog Cloud usage pricing or a self-hosted PostHog deployment: infrastructure, migration work, support, and the data history you pay to extend on Heap.
What it takes to get behavioral data out of Heap: Heap Connect warehouse sync and the plans that include it, the one-time JSON export from support, why chart CSV exports are not enough, and how data history limits cap what is left to export.
Heap agreed to join Contentsquare in 2023, and Contentsquare later merged Hotjar into its platform. This page sets out what is documented about Heap's future, the data history and Heap Connect terms to check at renewal, and how to plan an exit to PostHog.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.