Feature Flag Migration Playbook by mintlify[bot] · Pull Request #95 · mixpanel/docs

mintlify · 2026-07-14T14:24:56Z

Summary

This update introduces a new guide for migrating feature flags and experiments from other platforms to Mixpanel. It outlines a five-part process to ensure a smooth transition, covering exposure events, configurations, and verification.

Changes

Added guides/strategic-playbooks/feature-flag-migration-playbook.mdx.
Included new images: images/FeatureFlagSetup.png, images/ExperimentSetup.png, and images/ExperimentSetupMetrics.png.
Integrated the new playbook into the docs.json navigation structure.

Mintlify

0 threads from 0 users in Mintlify

No unresolved comments

- Updated docs/what-is-mixpanel.mdx - Created images/FeatureFlagSetup.png - Created images/ExperimentSetup.png - Created images/ExperimentSetupMetrics.png - Created guides/strategic-playbooks/feature-flag-migration-playbook.mdx - Updated docs.json Mintlify-Source: dashboard-editor

kurbycchua

Overall comment is we need to make sure we fact check these as we do not want a customer ending up in messing up their experiment / FF data in mixpanel. Migrating the exposure of $experiment_started I find it the easy part, the challenging part is the Experiment report and the FF report of which underlying drives the analysis and the gates

kurbycchua · 2026-07-15T06:34:25Z

+- **One-off**: From the Console, open the experiment's Pulse Results page and click _Export Report_ to download exposures and raw data as CSV.
+- **Bulk / ongoing**: Use a Data Warehouse Export or the generic Event Webhook to stream raw exposure events out.
+
+#### E**quivalent events**


Assume this section was validated by someone who is familiar with these 3rd party tools?

this was initially written for Statsig, but as it is now vendor agnostic i will update with a generic instruction on how to export the events.

kurbycchua · 2026-07-15T06:37:31Z

+
+Most vendors have a dedicated exposure event you can export. Each event should have the following at minimum:
+
+- The enrollment ID: This is either the user ID, device ID, or group ID


so these "minimum" required fields we should somewhat map them to the section on "
Import events into Mixpanel as $experiment_started" where we have the source code example.. maybe something like this as comments

{
"event": "$experiment_started",
"properties": {
"distinct_id": "alice@example.com", //The enrollment ID
"time": 1709275888, //Timestamp
"$insert_id": "statsig_exp_4821_alice_1709275888", //prevent re-run duplicates
"Experiment name": "checkout_flow_test", //experiment or feature flag name
"Variant name": "treatment" //assigned variant
}
}

there is an example code snippet in section 1b below, will incorporate the comments there

kurbycchua · 2026-07-15T06:38:47Z

+
+This section moves the configurations themselves into Mixpanel. It covers both experiment **setup** and experiment **reporting**.
+
+### Export configurations from your vendor


Are we talking about completed experiments here or ongoing experiments or both? Reason I'm asking especially for Experiments I don't see like start date or sample sizes in the example? SO not sure did someone actually checked these examples to make sure that

For historical completed experiments, or the various feature flag options they are correct in that it would recalculate any necessary metrics / exposures? Numbers might be different perhaps so that's a caveat

For ongoing experiments - this is more challenging how do you reconcile the numbers between the 2 systems

kurbycchua · 2026-07-15T06:43:54Z

+}
+```
+
+## Step 3. Continue setup in the Mixpanel UI


ok now I'm kinda confused... so in Step 2 we use API to create experiments and now in Step 3 we are recreating again?

unfortunately yes because there are configs in vendors that cannot be forwarded over to mixpanel eg the rollout group definition, runtime event, which are based on the events in the vendor itself

in that case would it be better to now use the API? just a thought

kurbycchua · 2026-07-15T06:46:19Z

+
+In the case of live experiments, migration might result in users getting reassigned to a different variant mid-experiment. We recommend completing any existing experiments and importing the historical exposure events into Mixpanel, then launching the equivalent experiment fresh in Mixpanel post-cutover.
+
+1. **If your code uses OpenFeature**: Swap the provider — replace your current provider with the Mixpanel provider and leave your existing evaluation calls unchanged, as long as your flag keys carried over identically.


Did we fact check these?

do you mean the live experiment or the openfeature? for Live experiment, i checked with Shalina as she worked on that for tiket, and they did it by concluding their experiments before porting over

Sorry to be clear when I said Did we fact check these? it's basically the whole "Step 4. Recreate critical flags and experiments in your code" section

Like are we sure about that OpenFeature just "swap the provider"? - Not very clear on that and for the 2nd point on simply replacing the evaluation calls... just making sure these are correct code snippets as I didn't vett through them.

mintlify Bot requested review from a team as code owners July 14, 2026 14:24

mintlify Bot requested review from caracheng and hywel-mixpanel July 14, 2026 14:24

mintlify Bot deployed to staging July 14, 2026 14:27 View deployment

hywel-mixpanel requested changes Jul 14, 2026

View reviewed changes

Comment thread docs/what-is-mixpanel.mdx

re-add buttons

5dad299

mintlify Bot deployed to staging July 14, 2026 19:26 View deployment

hywel-mixpanel approved these changes Jul 14, 2026

View reviewed changes

kurbycchua reviewed Jul 15, 2026

View reviewed changes

Merge branch 'main' into amymadden-ffmigration

e80d6d6

mintlify Bot deployed to staging July 15, 2026 06:53 View deployment


		Most vendors have a dedicated exposure event you can export. Each event should have the following at minimum:

		- The enrollment ID: This is either the user ID, device ID, or group ID


		This section moves the configurations themselves into Mixpanel. It covers both experiment setup and experiment reporting.

		### Export configurations from your vendor


		In the case of live experiments, migration might result in users getting reassigned to a different variant mid-experiment. We recommend completing any existing experiments and importing the historical exposure events into Mixpanel, then launching the equivalent experiment fresh in Mixpanel post-cutover.

		1. If your code uses OpenFeature: Swap the provider — replace your current provider with the Mixpanel provider and leave your existing evaluation calls unchanged, as long as your flag keys carried over identically.

Uh oh!

Conversation

mintlify Bot commented Jul 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Changes

Mintlify

Uh oh!

Uh oh!

kurbycchua left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

mintlify Bot commented Jul 14, 2026 •

edited

Loading