Migrate legacy A/B test
7 min
- Optimizely Feature Experimentation
- Optimizely Full Stack (Legacy)
This topic maps each corresponding UI element for an A/B test in legacy Full StackA/B test in legacy Full Stack to an A/B test in Feature ExperimentationA/B test in Feature Experimentation. A Multi-Armed Bandit maps similarly in Feature Experimentation. For more information, see Feature Experimentation application migrationFeature Experimentation application migration.
Note
Optimizely creates one A/B test for each environment in Feature Experimentation. The original (Full Stack) experiment ID is only preserved for production.
Variations
- The legacy Optimizely Full Stack Experimentation A/B test's experiment name 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 A/B test rule's flag key is a randomly generated GUID.
- The legacy experiment state Paused or Running becomes the A/B test rule's state.
- The legacy experiment's variations and traffic distribution percentages become the A/B test rule's variation traffic percentage.
- Legacy Full Stack
- Feature Experimentation
Allowlist (previously known as whitelist)
Note
WhitelistWhitelist was renamed to allowlist in Optimizely Feature Experimentation.
- A legacy A/B test's whitelist becomes the Feature Experimentation A/B test rule's allowlistallowlist.
- Legacy Full Stack Experimentation
- Optimizely Feature Experimentation
Audiences
- A legacy A/B test's audience becomes the A/B test rule's audience.
- Legacy Full Stack
- Optimizely Feature Experimentation
Traffic allocation
- The legacy A/B test's traffic allocation percentage becomes the A/B test rule's Percentage Included.
- Legacy Full Stack
- Optimizely Feature Experimentation
Metrics
- The legacy A/B test's metrics become the A/B test rule's metrics.
- Legacy Full Stack
- Optimizely Feature Experimentation
