Dev guideAPI Reference
Dev guideAPI ReferenceUser GuideGitHubNuGetDev CommunitySubmit a ticketLog In
GitHubNuGetDev CommunitySubmit a ticket

Feature Experimentation migration timeline

Timeline of migration from Optimizely Full Stack Experimentation to Optimizely Feature Experimentation.

After two years of running legacy and current Feature Experimentation products, Optimizely is officially sunsetting legacy Full Stack Experimentation on July 29, 2024.

Optimizely Feature Experimentation is the default experience for projects and Free Rollouts accounts since its launch in February 2021. Feature Experimentation offers a simplified workflow, data model, and API for experimenting with and delivering experiences to your end users.

Starting in 2024, you must migrate from legacy Full Stack Experimentation to Feature Experimentation.

Important dates

March 29, 2024

Creating Optimizely Full Stack Experimentation projects will no longer be available.

May 31, 2024

Creating new experiments or feature rollouts in Optimizely Full Stack Experimentation projects will no longer be available.

July 29, 2024

Optimizely Full Stack Experimentation software will be sunset. Optimizely will still support Legacy Full Stack Experimentation's isFeatureEnabled, GetFeatureVariable, Activate, and Track methods.

Benefits of migrating

Self-service migration

You can migrate your legacy Full Stack Experimentation project using the self-service migration option. Self-service migration is available in the Settings of a Full Stack Experimentation project.

Migration eligibility check

Optimizely will automatically run an eligibility check on your project to see if it can be upgraded to Feature Experimentation. For information on your project's eligibility for automatic migration, see Upgrade to Optimizely Feature Experimentation from Optimizely Full Stack Experimentation.

Steps to migrate

  1. Check your project's self-service migration eligibility. In your legacy Full Stack Experimentation project, go to Settings > Migration. Click Check Eligibility.

  2. (Optional) Resolve any issues with the migration. See Upgrade to Optimizely Feature Experimentation from Optimizely Full Stack Experimentation for information on how to fix any issues with your automatic migration.

    resolve issues with automatic migration
  3. If your project has no issues, or after you have resolved them, you will get a confirmation window letting you know your project is eligible for upgrade. Click Close.

  4. Click Begin Migration. Click Migrate on the confirmation window.

  5. Your project will start migrating. Depending on your project's size, this should only take a short amount of time. The page will update with the percentage of migration completed.

  6. After the migration, a Migration Complete confirmation window displays. Click Continue to view the newly migrated Feature Experimentation project.

Familiarize yourself and your team with the Feature Experimentation application UI and key concepts. Although not required, it is recommended you update your code to use the Decide and Track methods.

If you encounter any issues while migrating or have questions, contact your Customer Success Manager.


Review the following end-user articles for information on how certain features of Full Stack Experimentation are migrated to Feature Experimentation.