⌘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
Migrate from PostHog — import in minutes.
Your event history writes into analytics, so funnels and retention open full and adoption reads against the requests that drove the work.
Free · the token is used once and never stored.
PostHog holds the behavioural history: events, funnels, retention. Starting fresh elsewhere usually means an empty dashboard for a quarter, and a roadmap ranked without adoption data.
The event importer writes your history into AIOProductOS analytics. 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 are not empty on launch day.
-
Joined to accounts
Imported events attach to the customer record, so behaviour sits next to revenue and the requests from the same account.
-
First-party from here
After the import, the drop-in SDKs capture going forward. No cookies, DNT and GPC honoured.
FAQ
Migrating from PostHog
What does the PostHog importer bring?
Your PostHog event history, written into the AIOProductOS analytics stream so funnels, retention and paths carry real data from the first day instead of filling up over months.
Do the events keep their account context?
Yes. Imported events join the matching account, so behaviour, revenue and feature requests read on the same customer record.
Is it free?
Yes. Importing your own history is free on every AIOProductOS plan, and the import is one-way and read-only on PostHog.
Start full, not empty.
Bring your PostHog history onto one record per customer — revenue, feedback, work, and code, joined. Free on every plan.