Upgrade to Optimizely 12 – why it matters

Thinking about upgrading to Optimizely 12? If there is time and budget, there is really no reason to wait. The new version is admittedly more extensive than previous updates but contains surprisingly many treats. Here you’ll learn what the new version offers and get a few tips on what to consider before an upgrade project.

Why upgrade to Optimizely 12

1. Improved performance and security

When the new budget for the year has dropped in and it's time to plan all activities, updating the existing CMS may not end up at the top of the wish list. Especially not when this one is a fairly extensive and complex manoeuvre. It can feel a bit like installing triple-glazed windows during a renovation, when you'd really prefer to spend the time and budget on a spa area.

2. Why update when the existing version works?

With Optimizely 12 you get access to a range of new features that improve performance, security and usability. This version offers tools that make it easier to personalize and optimize your website, which in turn increases both conversions and customer satisfaction.

3. Support for older versions is being phased out

Another slightly dreary, but nonetheless important argument for updating Optimizely now rather than later is that the "end of life" for older versions is approaching. That is to say, support for earlier versions of Optimizely (which is already limited) will gradually cease entirely.

This means that if you continue to use an older version you will in time lose both technical support and security updates, which leads to any bugs or security vulnerabilities no longer being fixed. That makes your website more vulnerable. By upgrading to Optimizely 12 you not only ensure continued technical support, but also that your platform remains compatible with new technologies, APIs and integrations that are constantly evolving.

4. Risk of duplicated work

Another argument is increased development costs. Not upgrading can cause your website to fall behind technologically. A site running on an older, unpatched platform accumulates technical debt, with outdated code. New development then becomes not only more complicated, but also more expensive for you as the client. There is also a risk of duplicated work, since much will need to be adapted and redone when you finally carry out the upgrade.

Why is the upgrade to Optimizely 12 extensive?

Some CMS version updates involve just a few simple clicks and testing, and then it’s done. That is not the case with the upgrade to Optimizely 12.
Version 12 is more extensive than previous updates because it entails major changes both under the hood and in how the Optimizely platform functions.

Here are some of the main reasons why this upgrade is more complex:

Transition to .NET 5/6, and changes in API and codebase

Optimizely 12 has migrated to .NET 5 and 6, a modernized version of Microsoft’s framework. Earlier versions of Optimizely were built on the .NET Framework, but with the move to .NET Core the entire architecture has changed. APIs and code structures have also been altered or removed entirely. This means developers need to make significant code adjustments and that previous versions of websites and integrations are not directly compatible without rewriting the code to the new standards. This makes the upgrade more demanding compared with earlier, smaller updates.

New platform for development and deployment

Optimizely 12 has also improved its cloud-native infrastructure and its support for continuous integration and delivery (CI/CD). This shift to the cloud means users must adapt to new development and operational processes, which differ from traditional solutions. It can involve changes in how environments are managed and deployed.

Increased security and performance optimization

Optimizely 12 introduces new security features and performance improvements built on a modern architecture. These changes may require optimization of existing websites to take full advantage of the new enhancements. Previous upgrades were often more incremental and required less adjustment, whereas this version represents a more fundamental change.

Limited backward compatibility

With such a major technical transformation, Optimizely 12 is not always backward compatible with earlier versions of the tool. That means companies using older versions may need to upgrade their entire tech stack and sometimes migrate data or custom features, making the update more time-consuming.

Increased focus on headless and JAMstack

Optimizely 12 has expanded its support for headless CMS and JAMstack architecture (JavaScript, APIs and Markup), which means companies can separate the frontend from the backend for more flexible development. But for those not already working this way, it can mean a steeper learning curve and changed development practices.

Practical tips before upgrading to Optimizely 12

1. Take an inventory of the current solution

When moving house you naturally want to keep the number of moving boxes and trips up and down the stairs to a minimum. If you're smart you do a thorough tidy-up of shelves and storage, throw away those old boxes of course books and sell the exercise bike that's just collecting dust.

2. Focus on core features and cut unnecessary modules

That's exactly how you should think when moving to Optimizely 12. Take a thorough inventory of your current website. Are there page templates, modules and features that are hardly used? It's not uncommon to have lots of variants of modules that do roughly the same thing; which of them actually works best and is used the most? Be satisfied with moving only those. That way there's less code to update and you reduce complexity.

Every unnecessary component in the system requires extra time for testing and maintenance, which makes the upgrade more time-consuming. By removing things that are no longer used the development team can focus on core features, which speeds up the process and reduces the risk of errors. In addition performance is improved and technical debt is reduced, which makes it easier to further develop and maintain the platform in the future.

3. Don't make improvements - pause development

A common mistake in larger upgrade projects is being tempted to dip into budget and time to do new development and improvements while you upgrade to a new version. "Can we take the opportunity to do those simple fixes we've been waiting for?"

But doing that can be compared to starting to renovate the whole house at the same time as you move in – something that will probably be too much at once!

It's smarter to do one thing at a time; here's why:

Increased risk of errors

By mixing an upgrade with new development you add additional layers of code and features to the system, which can make it harder to identify and fix bugs. Any issues may be due to both the upgrade and the new functionality, which complicates troubleshooting. When you upgrade it will already be enough to keep track of that everything works as it should. If you also start adding new features at the same time it becomes harder to know what is causing problems if something goes wrong.

Longer test cycles

New development requires more extensive testing, which prolongs the entire upgrade process. If the focus is kept on getting the existing platform to work with the new version, testing becomes faster and more focused.

Security and stability

An upgrade in itself can be a challenging process that affects the stability of the entire system. By limiting changes to the necessary you minimize the risk of unexpected outages or performance problems.

Clarity in the project

By separating the upgrade from new development it becomes easier to keep the project structured. When the upgrade is complete you can focus on implementing improvements without worrying about backward compatibility or issues with the new version.

By keeping the upgrade clean and free from other changes the process can become smoother, safer and faster.

Also read