If your Episerver site still works, an upgrade may not feel urgent. Your pages load. Editors can publish content and more. So why change something that is working?
The problem is that an older CMS can continue working while becoming harder and more expensive to maintain. Developers may spend more time dealing with legacy code, marketing requests may keep landing in the development queue, and new integrations may require workarounds.
That is where the question “Why upgrade Episerver?” becomes more relevant.
Episerver is now Optimizely, and the upgrade path depends on the version, codebase, integrations, packages, and business requirements of your implementation. CMS 13 also introduces significant changes from CMS 12, including a move to .NET 10 and changes to search, routing, APIs, and other platform components.
So, is an Episerver upgrade worth it? It depends on what your current implementation is costing your team and what you need the platform to support next.
When Should You Upgrade Episerver?
You may want to consider an upgrade when:
- Your CMS version is no longer supported.
- Developers spend significant time maintaining legacy code.
- Routine content changes require development support.
- Third-party packages are difficult to keep compatible.
- Existing integrations need repeated custom fixes.
- Your architecture makes new digital experiences harder to implement.
- Your team is planning a major website, search, commerce, or integration project.
Why Upgrade Episerver? 5 Reasons to Consider It
1. Developers Spend Too Much Time Maintaining Legacy Code
One of the clearest reasons to upgrade Episerver is how much developer time an older implementation requires to keep running.
- Legacy code often includes older APIs, custom modules, third-party packages, and workarounds added over several years. None of these necessarily creates a problem on its own.
- The issue arises when a simple change requires developers to understand several layers of older code before they can make it safely.
For example, a request to change an existing integration may involve checking the CMS version, package compatibility, authentication method, custom services, and API dependencies before development can begin.
- An upgrade gives your team a chance to review those dependencies instead of carrying them forward. As, Optimizely recommends reviewing the affected areas and assessing the impact on custom code and integrations before beginning the upgrade.
2. Routine Marketing Changes Keep Becoming Development Tasks
This is an Episerver upgrade benefit if your current editing process creates unnecessary delays between content creation and publishing.
For example, a marketer might need to create a landing page, adjust a page layout, or work with approved content components. If these requests repeatedly become development tickets, the issue may be the editing experience or the way your implementation has been built.
- CMS 13 uses Visual Builder as its default editing experience. It allows editors to work with approved components when the implementation has been configured to support them.
- This does not eliminate the need for developers. Complex functionality, integrations, templates, and custom components still require development.
- The objective is simpler: reduce development involvement where a content team should reasonably be able to work independently.
3. Your Integrations Are Becoming Harder to Maintain
Your Episerver implementation may connect with a CRM, ERP, and many other applications. Those connections can become difficult to maintain when they rely on older APIs, packages, authentication methods, or custom middleware.
Let’s consider a real migration example.
For example, in a CMS 12-to-CMS 13 migration example published by Optimizely, the implementation included mixed-era NuGet references, extensive Search & Navigation usage, custom code, and reliance on CMS 12 APIs. The team had to resolve these dependencies to transition to .NET 10 and CMS 13 successfully.
- The migration also involved replacing Search & Navigation with Optimizely Graph while maintaining the existing search and listing experience. This shows why you should approach an upgrade as a comprehensive architectural update, not a simple version bump.
- Before deciding why to upgrade Episerver, review your current implementation dependencies. Your packages and integrations will often influence the project scope more than the core CMS version.
4. Your Current Architecture Makes New Requirements Difficult
While your original website architecture may have served its initial purpose, evolving business goals often demand more flexibility. Custom workarounds can slow development and increase complexity as your requirements grow to include:
- Managing multiple sites
- Supporting additional languages
Delivering content across various digital touchpoints
CMS 13 addresses this with Optimizely Graph, providing a modernized content delivery and search architecture. With the Optimizely Graph SDK, developers can query content directly using familiar C# patterns instead of raw GraphQL.
Ultimately, upgrading to a modern architecture isn’t just about adopting headless capabilities; it’s about ensuring your platform can support new experiences efficiently and scale smoothly without technical friction.
5. The Cost of Staying on the Old Version Keeps Growing
The Episerver upgrade cost is only one side of the decision. You should also consider what the existing implementation costs to maintain.
That cost can include:
- Developer hours spent fixing legacy issues
- Time spent investigating package conflicts
- Delays caused by development dependencies
- Custom workarounds
- Integration maintenance
- Testing older components
- Delayed product or marketing work
For example, if an internal development team spends 20 hours each month on legacy maintenance and its internal cost is $100 per hour, that represents $24,000 in annual development effort. That does not mean an upgrade will automatically save $24,000. The upgrade itself may require significant engineering work.
The point is to compare the two sides.
Current maintenance cost + business impact
Vs
Upgrade cost + expected maintenance requirements
That gives you a more useful basis for deciding whether an Episerver upgrade is worth it.
CMS 12 vs. CMS 13: Which Should You Choose?
If you are already on CMS 12, moving to CMS 13 is not simply a runtime update. CMS 13 targets .NET 10 and introduces changes across APIs, routing, security, plugins, scheduled jobs, UI components, and third-party package compatibility.
Search is another important consideration. Optimizely states that Search & Navigation is not compatible with CMS 13, so implementations using it need to address search as part of the upgrade.
| Area | CMS 12 | CMS 13 |
|---|---|---|
| Runtime | Modern .NET; supports .NET 10 | .NET 10 |
| Editing | CMS 12 editing experience | Visual Builder |
| Search | Search & Navigation or Optimizely Graph, depending on implementation | Optimizely Graph |
| Architecture | Existing CMS 12 architecture | Updated CMS 13 architecture |
| Upgrade considerations | Depends on existing implementation | Requires review of CMS 13 breaking changes and dependencies |
What Are the Main Episerver Upgrade Requirements?
Before you set a budget or Episerver upgrade timeline, review the areas that can change the project scope.
1. Current CMS and .NET Version
Document the CMS version, runtime, hosting model, and major packages currently in use.
2. Custom Code
Identify custom modules, controllers, services, scheduled jobs, routing logic, and other code that may depend on APIs changed or removed in the target version.
3. Third-Party Packages
Create an inventory of NuGet packages and Optimizely add-ons. Confirm whether each package supports your target CMS version.
4. Integrations
Review CRM, ERP, PIM, DAM, search, commerce, analytics, authentication, and other external connections.
5. Search
If the implementation uses Search & Navigation, include the search migration in your scope when targeting CMS 13.
6. Content and Editing
Review page types, blocks, properties, editor configurations, and content workflows.
7. SEO
Check URLs, redirects, canonical tags, XML sitemaps, metadata, structured data, and internal links before and after migration.
8. Testing Requirements
Identify the key journeys that need testing, including forms, search, navigation, content publishing, integrations, authentication, and commerce functionality.
These Episerver upgrade requirements help you identify the work before development begins, rather than discovering dependencies halfway through the project, and they explain why you should upgrade Episerver beyond the release number alone.
How Beanstalk Can Help With an Optimizely Upgrade
If you are working with a legacy Episerver implementation, the first step does not have to be a full migration. Upgrade when the current implementation is creating problems for your business.
If developers spend too much time maintaining legacy code, routine marketing changes require development support, integrations are becoming harder to maintain, or new requirements keep exposing limitations in the existing architecture, it is worth assessing your upgrade options.
Then decide whether staying on the current version, moving through a staged upgrade, or moving to the latest version like CMS 13 makes the most sense.
At Beanstalk Web Solutions, we work with Optimizely across upgrades, development, implementation, and support. The focus is on the existing site and the work it needs, rather than treating every upgrade as the same project.