Gamification platform migration
Migrating a live casino brand from a legacy gamification platform without losing player progress.
Context
A casino brand was moving from a legacy gamification platform to a newer one. The work had been scoped in pieces by different people over several months, with no single document anyone could quote against. Engineering was reluctant to start. The brand team thought it was a copy job.
The problem
Platform migrations of this kind have three failure modes: player progress loss, broken triggers, and stakeholder mismatch on what's actually changing. Without a unified brief, the migration was on track for at least two of those.
What I did
- → Audited the existing gamification implementation — campaigns, triggers, player segments, reward types
- → Mapped each existing component to its equivalent on the new platform, flagging what didn't translate cleanly
- → Wrote a single migration brief covering scope, sequencing, data migration, rollback, and out-of-scope items
- → Surfaced risks that hadn't been raised — segment definitions that wouldn't survive the migration, triggers that depended on legacy event names, edge cases around in-flight campaigns at cutover
- → Coordinated stakeholder sign-off across product, brand, and engineering before build started
Outcome
- ✓ Migration brief became the single source of truth referenced through build
- ✓ Edge cases caught at spec stage rather than at QA — saving roughly two weeks of rework based on previous similar migrations
- ✓ Rollout plan adapted and reused for the second brand with minor edits
- ✓ Stakeholder alignment held through to launch, with no scope changes after sign-off
What was used
Linear Figma
Interested in working together?
Book a free 30-minute discovery call. No pitch deck, no proposal until we've talked.
Book a discovery call