Migrate from GameAnalytics

Moving from GameAnalytics to PlayGenus takes three steps: export your event history as JSON, upload it to the PlayGenus importer, and review the event mapping we propose. Once the mapping is confirmed, your history is ingested and the churn, LTV, and forecast models train on your real players — no waiting weeks for fresh data to accumulate.

The general import mechanics — file limits, the mapping review UI, multi-file imports — live in Import your historical data. This page covers the GameAnalytics-specific parts.

Step 1 — Export your events from GameAnalytics

1. In the GameAnalytics dashboard, go to Tools → Data Export.
2. Pick the date range and the event types you want.
3. Download the JSON/NDJSON file.

Export options vary by GameAnalytics plan — if your dashboard doesn't match the recipe above, their export documentation is canonical, and any raw JSON or NDJSON event dump they produce works for the import. Bring as much history as you have: 90 days is a sensible minimum for solid predictions, and more is better — the import guide breaks down exactly what each span of history unlocks.

Step 2 — Upload to PlayGenus

In the dashboard: Historical Imports → New import, pick GameAnalytics as the source format, and drop the file in. You need an onboarded game with an approved tracking plan first — import maps your old events onto that plan. Not there yet? Start with How onboarding works.

Files up to 1 GB upload straight from your browser; bigger exports can be split by date range, and after your first file's mapping is approved the rest can go up together in one batch.

Step 3 — Review the mapping

After parsing, you get a mapping table: every GameAnalytics event type in your file, matched to a target event in your PlayGenus tracking plan. The GameAnalytics event taxonomy translates naturally:

• Progression events (start / complete / fail, with their world:stage:level hierarchy) map onto your plan's progression events.
• Business events map onto purchase events.
• Resource events (source/sink flows) map onto economy_earn and economy_spend.
• Design events — the catch-all custom taxonomy — map onto your custom events, and this is where your review attention pays off, since design event naming is unique to your game.

Include what's worth keeping, exclude what isn't, correct anything we got wrong, and submit. A PlayGenus engineer confirms the mapping with you before anything is ingested — and if something about your export looks different from what this page describes, email us and we'll walk through it with you.

What happens after

Once confirmed, your history loads and the models that depend on it retrain — churn, LTV, survival, and the DAU, revenue, and session forecasts. Dashboards populate as soon as the import lands; predictions follow when retraining completes. From then on, live events come from the PlayGenus SDK and your history sits in the same dataset — one continuous record, no gap where the migration happened.

You don't have to switch off GameAnalytics on day one, either — plenty of studios run both during a transition and retire the old one when they're comfortable.