Migrate legacy feature test

8 min

Optimizely Feature Experimentation

Optimizely Full Stack (Legacy)

This topic maps each corresponding UI element for a feature test from legacy Optimizely Full Stack Experimentation to a flag with an A/B test rule in Optimizely Feature Experimentation. See Feature Experimentation application migration.

Variations

The feature test's name in legacy Full Stack Experimentation becomes the A/B test rule's name attached to the flag in Optimizely Feature Experimentation.

Note

Because there is no corresponding name for a rule in Full Stack, Feature Experimentation creates a name based on the audience.

The feature test's key becomes the A/B test rule's key.

The feature test's variations and traffic distribution percentages display in the A/B test rule's variation traffic percentage.

Note

The variation description in legacy Full Stack has no corresponding element in Feature Experimentation.

The feature test's variable values are reflected in the A/B test rule's variables.

Note

The featureEnabled toggle should be set to On because it does not have a Feature Experimentation equivalent mapping in the UI (the backend maps the correct value). If your legacy Full Stack Experimentation project contains a Feature Test with an off variation, the variations remain off in your migrated project. See Warnings when upgrading to Optimizely Feature Experimentation from Optimizely Full Stack Experimentation for more information.