Migrate legacy A/B test

This topic maps each corresponding UI element for an A/B test in legacy Full Stack to an A/B test in Feature Experimentation. A Multi-Armed Bandit maps similarly in Feature Experimentation. For more information, see Feature Experimentation application migration.

Variations

1. 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.
   Because there is no corresponding name for a rule in Full Stack, Feature Experimentation creates a name based on the audience.
2. The A/B test rule's flag key is a randomly generated GUID.
3. The legacy experiment state Paused or Running becomes the A/B test rule's state.
4. 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)

1. A legacy A/B test's whitelist becomes the Feature Experimentation A/B test rule's allowlist.

• Legacy Full Stack Experimentation

  

• Optimizely Feature Experimentation

  

Audiences

1. A legacy A/B test's audience becomes the A/B test rule's audience.  

• Legacy Full Stack

  

• Optimizely Feature Experimentation

  

Traffic allocation

1. 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

1. The legacy A/B test's metrics become the A/B test rule's metrics. 

• Legacy Full Stack

  

• Optimizely Feature Experimentation