Migrate to HitKeep

HitKeep supports a few migration paths. Use native imports when HitKeep understands the source export, replay historical logs when you have raw request or event data, run both tools in parallel when there is no reliable historical import, and use open exports when you need to keep data portable after the move.

Choose a migration path

Source or task	Recommended path	Notes
Plausible	Import Plausible data	HitKeep accepts the Plausible export ZIP or loose CSV files with supported Plausible headers.
Simple Analytics	Import Simple Analytics data	HitKeep imports the All datapoints CSV into compatible historical reports.
Google Search Console	Connect Google Search Console	HitKeep imports finalized Search Analytics aggregates through Google’s API. This is a connected sync, not a file upload.
Web server, reverse proxy, or CMS logs	Replay historical logs	Use server-side tracking when you have original timestamps, URLs, IPs, and user agents.
Google Analytics 4	Parallel tracking and report validation	HitKeep does not import GA4 history. See the GA4 comparison and self-hosted GA4 alternative guides.
Matomo	Parallel tracking and report validation	HitKeep does not import Matomo history. See the Matomo comparison for migration notes.
Umami	Parallel tracking and report validation	HitKeep does not import Umami history. See the Umami comparison for migration notes.
Fathom	Parallel tracking and report validation	HitKeep does not import Fathom history. See the Fathom comparison for migration notes.
Other analytics tools	Parallel tracking or log replay	Use native imports only for supported source formats. Use log replay when you can reconstruct pageviews or events from raw logs.
Leaving HitKeep or validating portability	Open exports and takeout	Export site data in CSV, Parquet, JSON, NDJSON, or XLSX.

Native imports

Native imports are best when HitKeep understands the source export schema. They validate the uploaded files before writing data, show warnings for unsupported rows, and keep imported historical data separate from native HitKeep events where the source export cannot prove raw relationships.

Use these guides when the source is supported:

Google Search Console uses a different path. It connects through OAuth, maps a Search Console property to a HitKeep site, and imports aggregate Search Analytics rows from Google’s API.

For automation, use the Imports API reference. The API follows the same lifecycle as the dashboard and CLI: create an upload, send file chunks, validate, start, check status, list history, and delete imports when needed.

Historical replay

Use server-side tracking when you have raw logs or source events with original timestamps. This path is useful for web server logs, reverse proxy logs, CMS jobs, backend events, and one-off replay scripts.

Replay sends pageviews or events through HitKeep’s ingest endpoints. It can preserve the original event time, but it cannot recover dimensions that were never present in the source log.

Parallel tracking

Run HitKeep beside the existing analytics product when there is no direct import path or when reporting owners need a live comparison before switching tags. A short parallel period lets you validate traffic levels, sources, pages, events, goals, funnels, ecommerce, and stakeholder reports against the questions your team asks each week.

For GA4 replacements, start with the self-hosted GA4 alternative guide and the HitKeep vs Google Analytics comparison. For other products, use the relevant comparison page, such as Plausible, Simple Analytics, Matomo, Umami, or Fathom, to check migration notes and product fit.

After the move

After importing or replaying historical data, open the destination site dashboard and select the migrated date range. Confirm the reports that matter to your team before removing the old tag or ending the parallel run.

Keep open exports and takeout in the migration checklist. Exports are useful for audits, warehouse checks, portability reviews, and vendor exit planning.