Migrate from PlayFab

Moving your analytics history from PlayFab to PlayGenus takes three steps: export your event history, upload it to the PlayGenus importer, and review the event mapping we propose. Once confirmed, your history is ingested and the churn, LTV, and forecast models train on your real players immediately.

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

Step 1 — Export your events from PlayFab

1. In PlayFab Game Manager, go to Data → Event History.
2. Set the date range and click Export.
3. Download the JSON/NDJSON file when the export email arrives.

PlayFab's Event History covers a limited window on some tiers; if you've previously wired PlayFab's data export to your own storage, those JSON dumps work just as well. Bring as much history as you have — 90 days is a sensible minimum, and the import guide breaks down what each span unlocks.

Step 2 — Upload to PlayGenus

Historical Imports → New import, pick PlayFab as the source format, and drop the file in. You need an onboarded game with an approved tracking plan first, because import maps your old events onto that plan — see How onboarding works if you're not there yet.

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

Step 3 — Review the mapping

The mapping table shows every PlayFab event type in your file matched to a target event in your tracking plan:

• PlayStream system events — logins, registrations, real-money purchases — map naturally onto session, lifecycle, and purchase events.
• Title events (your custom PlayStream events) map onto your custom events; this is where your review attention matters most, since the naming is unique to your game.
• Player identifiers — the importer maps PlayFab's player IDs onto player_id, so a player's history stays stitched together.

Include, exclude, and correct as needed, then submit. A PlayGenus engineer confirms the mapping with you before anything is ingested — and if your export looks different from what this page describes, email us and we'll walk through it together.

What happens after

Your history loads, the dependent models retrain — churn, LTV, survival, and the DAU, revenue, and session forecasts — and dashboards populate as soon as the import lands. Live events then come from the PlayGenus SDK into the same dataset: one continuous record.

And since PlayFab is more than analytics, note what this migration does not touch: your LiveOps, economy, and backend services on PlayFab keep working untouched. You're moving the analytics story, not the game backend — many studios keep PlayFab for services and PlayGenus for the predictive layer on top.