⌘K · Import · PostHog
via the event importer
- ✓ lands on the spine, joined to accounts
- ✓ one-way — read-only on PostHog
- ✓ free on every plan
Token used once · not stored
Import from PostHog in minutes.
Your event history writes into analytics, so funnels and retention open full — not from zero.
Free · the token is used once and never stored.
PostHog holds your behavioural history — the events, funnels, and retention you've been tracking. Starting fresh somewhere else usually means an empty dashboard for months.
The event importer writes your history into AIOProductOS analytics, so funnels and retention have real depth on day one — and every event joins the account it belongs to.
What comes across
Bringing PostHog onto the spine
-
Event history, not zero
Your past events write into the analytics stream, so funnels and retention aren't empty on launch.
-
Joined to accounts
Imported events attach to the customer record, so behaviour sits next to revenue and feedback.
-
First-party from here
After the import, the drop-in SDKs capture going forward — cookieless, DNT and GPC honoured.
FAQ
Migrating from PostHog
What does the PostHog importer bring?
Your event history, written into the analytics_event stream so funnels, retention, and paths have real data immediately.
Do the events keep their account context?
Yes. Imported events join the matching account, so behaviour and revenue read on the same customer record.
Is it free?
Yes. Importing your own history is free on every plan.
Start full, not empty.
Bring your PostHog history onto one record per customer — revenue, feedback, work, and code, joined. Free on every plan.