Data

Import from PostHog

Move your PostHog events and persons into Tracklyne and switch your SDK calls.

Import your history

In PostHog, export the events you want to keep as CSV or JSON lines (from an insight, the events explorer or a batch export).
In Tracklyne open Data pipelines → Imports, choose PostHog and upload the file.
The import runs in the background: follow its progress and keep using Tracklyne meanwhile.

Event names and properties are kept as is ($pageview, $autocapture…), $set and person properties are applied, and events that carry a uuid are never imported twice, so re-running an import is safe.

The import only reads the file you upload. Tracklyne never connects to your PostHog account.

Switch the SDK

The calls map one to one:

PostHog	Tracklyne
`posthog.init(key, { api_host })`	`tracklyne.init(token, { api_host })`
`posthog.capture(event, props)`	`tracklyne.capture(event, props)`
`posthog.identify(id, set, setOnce)`	`tracklyne.identify(id, set, setOnce)`
`posthog.opt_out_capturing()`	`tracklyne.opt_out_capturing()`
`posthog-node`, `posthog-ios`	`@tracklyne/node`, `TracklyneSwift` (same method names)
`posthog.isFeatureEnabled(key)`	`tracklyne.isFeatureEnabled(key)`
`posthog.reset()`	`tracklyne.reset()`

Run both side by side for a few days, compare numbers, then remove PostHog.