Legacy feature and targeted rollout to Feature Experimentation migration example

This topic maps each corresponding UI element for a feature with two experiments and a targeted rollout in legacy Optimizely Full Stack Experimentation to a flag with two A/B tests and a targeted delivery rule in Optimizely Feature Experimentation.

Legacy feature with two A/B tests

The feature name in legacy Full Stack becomes the flag name in Feature Experimentation.
The feature key becomes the flag's key.
The feature's variables becomes the flag's variables.
The feature test experiment feature_test_archive becomes an A/B test rule attached to the flag.
The feature test experiment started_running_feature becomes an A/B test rule attached to the flag.
The targeted rollout rule state on or off becomes the rule's status, play or paused.
The targeted rollout traffic allocation Traffic % becomes the rule's Ramp Percentage.
The targeted rollout audience becomes the targeted delivery rule's audience.

The legacy rollout rule's audience becomes the targeted delivery rule's name and audience in Feature Experimentation.

Because there is no corresponding name for a rule in Full Stack, Feature Experimentation creates a name based on the audience.
The legacy rollout rule's traffic allocation percentage becomes the targeted delivery's traffic allocation percentage
The Rollout traffic setting at 0% becomes the Off variation in Feature Experimentation.
The feature test tied to the feature f2_test becomes an A/B test rule attached to the flag
The feature test tied to the feature f2_test_2 becomes an A/B test rule attached to the flag