Migrate from PostHog to Zenovay
Read this before you switch. If PostHog is your product analytics backbone, stay on it. If you adopted it mainly for website analytics and the nine-product bundle feels heavier than you need, this guide is for you.
Migration Steps
Decide whether you should actually move
If your team relies on PostHog for deep product analytics, feature-flag-driven release engineering at scale, or its data warehouse, you should probably stay on PostHog or run both. The teams who benefit from moving are the ones who adopted PostHog for website analytics, found the nine-product bundle heavier than they needed, and want something a non-engineer can drive.
Install Zenovay alongside PostHog
Create a free account, add your site, and paste one script tag. Collection starts immediately and the whole install takes about two minutes. Leave PostHog running so both tools see the same traffic while you compare them.
Import your PostHog pageview history
Zenovay imports pageview traffic from PostHog on Pro plans and above. In your site, open Data, then Import, and choose the PostHog tile. You will need your numeric PostHog project ID, a personal API key beginning with phx_ (a project API key returns 403), and your region: US Cloud, EU Cloud or your self-hosted host. app.posthog.com does not work, because it redirects to the regional host. The default window is the last 365 days ending yesterday, and a custom date range is optional. Custom product events, feature flags, experiments, surveys and session recordings are not imported, so export those with PostHog's batch exports, or keep the project readable for reference, before you cancel.
Rebuild the handful of things you actually look at
Most teams read a fraction of what they track. Recreate your goals, funnels and custom events in Zenovay, connect Stripe for revenue attribution, and add uptime checks. If you run experiments, A/B testing and feature flags are available on Pro and above, and a developer adds one line of JavaScript to read the assigned variant.
Compare for a couple of weeks, then decide
Run both side by side. The numbers will not match exactly because bot filtering, session rules and event definitions differ, and that is expected. Then either switch fully, or settle where many teams land: PostHog for in-product behaviour, Zenovay for marketing, traffic and revenue attribution.
Before and After
With PostHog
- Nine bundled products in one interface
- Deeper, more mature experiments and feature flags
- MIT-licensed core you can self-host
- Built-in data warehouse for joining external sources
- 1 million events a month on the free tier
- Cloud defaults to US hosting, with EU hosting available
With Zenovay
- One dashboard focused on web traffic and revenue
- Frequentist A/B/n testing and feature flags from Pro up
- Managed service only, no self-hosting option
- Warehouse export to your own S3-compatible storage on Scale
- 10,000 events a month on the free plan
- EU hosting in Frankfurt by default, cookieless mode available
What You Keep
- Custom event tracking
- Funnels, goals and retention
- Session replay and heatmaps
- A/B experimentation and feature flags on Pro and above
- Identified users and cross-domain identity
What You Gain
- Revenue attribution tied to Stripe
- Uptime monitoring and error tracking
- EU hosting in Frankfurt by default
- Cookieless mode with no cookies and no local storage
- Flat plan pricing instead of per-event billing
- A dashboard a marketer can drive without writing SQL
Frequently Asked Questions
Should I actually leave PostHog?
Often, no. If you rely on PostHog for deep product analytics, feature-flag-driven release engineering at scale, or its data warehouse, stay on PostHog. Zenovay is not a replacement for those. The teams who benefit from moving adopted PostHog mainly for website analytics and found the bundle heavier than they needed.
Can I run PostHog and Zenovay together?
Yes, and many teams do exactly that: PostHog for in-product behaviour, Zenovay for marketing, traffic and revenue attribution. This is not a forced either/or. Both are a single script tag, so running both is a normal setup rather than a compromise.
Will I lose my PostHog history?
Not your pageview history. Zenovay's PostHog importer brings across daily visitors and pageviews, plus top pages, referrers, countries, devices, browsers and operating systems, read from PostHog's $pageview event. It does not bring across custom product events, feature flags, experiments, surveys or session recordings. Because only part of your data transfers, still export your history with PostHog's batch exports, or keep the project in a read-only state for reference, before you cancel.
How does the PostHog import work, and why can it finish as partial?
It reads your data through PostHog's HogQL query endpoint. PostHog's own documentation deprecates the events API and steers bulk extraction towards batch exports, which land in your S3, BigQuery or Snowflake rather than anywhere Zenovay can read, so querying is the workable route. That endpoint is rate limited, at 120 queries an hour on legacy projects and 2,400 on newer ones, so a large import can stop short and report as partial. That is expected rather than a failure: run it again for the remaining dates with a custom date range.
Do I need an engineer to switch?
Not for the install. It is one script tag in your site's head, roughly two minutes. You will want a developer for one thing: reading the assigned variant in JavaScript if you run A/B tests. Note that in cookieless mode variant assignment is window-scoped and resets when the tab closes, so it suits short in-page tests better than long multi-session experiments.
Try it side by side
Install Zenovay next to PostHog, compare two weeks of real traffic, and decide with your own data instead of a pitch.
No credit card required · Setup in 2 minutes · Free plan forever