Migrate legacy feature test

  • Updated
  • 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

  1. 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.
    Because there is no corresponding name for a rule in Full Stack, Feature Experimentation creates a name based on the audience.
  2. The feature test's key becomes the A/B test rule's key.
  3. The feature test's variations and traffic distribution percentages display in the A/B test rule's variation traffic percentage.
    The variation description in legacy Full Stack has no corresponding element in Feature Experimentation.
  4. The feature test's variable values are reflected in the A/B test rule's variables.
    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.
  • Legacy Full Stack Experimentation

    FS-feature-test.png

  • Optimizely Feature Experimentation

    FX-part1.png

    FX-variations.png

    The traffic allocation of a legacy feature test becomes the A/B test rule's Ramp Percentage.
  • Legacy Full Stack Experimentation

    traffic-allocation-fs.png

  • Optimizely Feature Experimentation

    traffic-allocation-fx.png

Whitelist/Allowlist

Whitelist was renamed to allowlist in Optimizely Feature Experimentation.
  1. A feature test's whitelist becomes the A/B test rule's allowlist.
  • Legacy Full Stack Experimentation

    whitelist-fs.png

  • Optimizely Feature Experimentation

    allowlist-fx.png

Audiences

  1. A legacy feature test's audience becomes the A/B test rule's audience.  
  • Legacy Full Stack Experimentation

    audience-fs.png

  • Optimizely Feature Experimentation

    audiences-fx.png

Metrics

  1. The legacy feature test's metrics become the A/B test rule's metrics. 
  • Legacy Full Stack Experimentation

    metrics-fs.png

  • Optimizely Feature Experimentation

    metrics-fx.png