Migrate legacy feature

This topic maps each corresponding UI element for a feature with two experiments in legacy Optimizely Full Stack Experimentation to a flag with two A/B tests in Optimizely Feature Experimentation. See Feature Experimentation application migration.

When there are multiple rollout rules on a Full Stack feature, Optimizely converts the Full Stack everyone rule to the default Feature Experimentation everyone else rule drop-down (must be either 0 or 100%, nothing in between).

When there is one rollout rule on a Full Stack feature (default everyone rule), Optimizely adds it as a new Targeted Delivery rule in Feature Experimentation (allowing for any percentage between 0 and 100).

1. The feature name (with_audience) in legacy Full Stack becomes the flag name in Feature Experimentation.
2. The feature key (with_audience) becomes the flag's key.
3. The feature's variables (str_var) become the flag's variables.
4. The feature test experiment (feature_test_archived) becomes an A/B test rule attached to the flag.
5. The feature test experiment (started_running_feature) becomes an A/B test rule attached to the flag.

6. The targeted rollout rule state on or off becomes the rule's status, play or paused.

7. The targeted rollout traffic allocation Traffic % (72) becomes the rule's Ramp Percentage.

8. The targeted rollout audience becomes the targeted delivery rule's audience (aud1).

• Legacy Optimizely Full Stack Experimentation

  

• Optimizely Feature Experimentation