If you’re on Optimizely CMS 12, you’ve probably heard that CMS 13 is here and that you’ll need to make the move at some point. It’s easy to think of it as just another update for the developers to sort out, but it’s actually a bit bigger than that, and it’s worth giving it some proper thought before you dive in.
I’ve been working with clients on their CMS 13 plans this year, and the ones who get the most out of it treat it as a business decision first and a technical project second. So I wanted to share the steps we walk through with them, in plain English, for anyone who’s starting to think about the move.
Step 1: Start with why you’re doing it
Before anything else, it’s worth agreeing why you’re upgrading and what a good result looks like for you. It sounds obvious, but it makes every decision after this so much easier, from budget and timelines to getting sign-off internally.
For most of the clients I speak to, it comes down to three things:
- Staying supported. CMS 13 runs on a newer version of Microsoft’s .NET framework. The version most CMS 12 sites use (.NET 8) stops getting support from Microsoft on 10 November 2026, so staying put means running on technology that no longer gets security updates.
- Making life easier for your editors. CMS 13 brings a simpler editing experience and a tool called Visual Builder, so your marketing team can build and publish pages without having to wait on a developer.
- Being found in AI search. More and more people are asking tools like ChatGPT rather than searching Google. CMS 13 includes features to help your content show up in those answers, and lets you see how AI tools are reading your site.
Try to turn these into two or three goals you can actually measure. “Stay on a supported platform” is completely fine as a goal! The important bit is that everyone agrees what the project is there to deliver.

Step 2: Find out what you’re working with
Every website is built a bit differently, so how much work it takes to get to CMS 13 really depends on what’s under the hood of yours. That’s why we always start with a short discovery phase, usually about a week, before committing to a full plan.
Discovery is where we answer questions like:
- How much has your site been customised? The more bespoke features you have, the more there is to check and update.
- Do any add-ons or plugins need replacing? Some third-party tools might not be ready for CMS 13 yet, and Optimizely themselves say this is usually where most of the time goes.
- Are you using Optimizely’s older search tool (Search & Navigation, sometimes called Find)? It doesn’t work in CMS 13, so you’ll need to choose a replacement. That’s really a decision about how your visitors find things, not just a technical swap.
- How does your team log in? CMS 13 changes how editors sign in and the web address they use to get into the CMS, so it’s good to know who’ll be affected.
- How does your site perform today? We take a snapshot of your current speed and performance so we can show the new version is just as good, or better.
At the end you should have a simple report covering what needs fixing, what needs replacing and how it’ll all be tested. It’s the foundation for everything that follows, so it’s worth doing properly.
Step 3: Decide how big you want to go
This is probably the biggest decision you’ll make. Broadly, there are two ways to approach it:
| |
Keep it like-for-like |
Upgrade and add new features |
| What you get |
Your site, on a supported platform |
Your site on a supported platform, plus new tools for your team |
| What’s involved |
Upgrading, fixing anything that’s changed and testing it all |
All of that, plus setting up things like Visual Builder, AI search features or a new search tool |
| Risk |
Lower, as you’re just checking everything still works |
Higher, as there’s more changing at once |
| Best if |
You’re up against a deadline, or a redesign is coming soon |
Your site has plenty of life left and your team are asking for more |
Most of the time I’d suggest going like-for-like first, then adding new features in stages afterwards. It keeps testing simple (does everything still work like it did before?) and gives you a solid base to build on.
The one thing I’d think about early is Optimizely Graph. It’s the engine behind the new search and a lot of the AI features, and Optimizely recommend getting it set up sooner rather than later because it’s harder to add down the line. So even if you’re keeping things like-for-like, it’s worth deciding where you stand on Graph from the start.
Step 4: Map out the plan
For a like-for-like upgrade, we usually plan for around eight weeks from kick-off to launch. Along the way there are three quick check-ins (we call them stage gates) where everyone agrees it’s OK to move on to the next bit.
- Discovery (week 1). We agree what we’ve found, what needs fixing and how we’ll test it. This is the first check-in.
- Build (weeks 2 to 3). Our developers do the upgrade itself and fix anything that’s changed.
- Testing (week 4). We test the whole site to make sure everything works as it should. Then it’s the second check-in: is it ready for your team to try?
- Your team tests it (weeks 5 to 7). Two rounds of user testing, with a week in between for us to fix anything you find.
- Go live (week 8). A final check-in to make sure everyone’s happy, then we launch.
- Aftercare (the first few days after launch). We keep a close eye on things and fix anything that pops up quickly.

A couple of things that make a big difference:
- Your team’s time really matters. Having testers booked in, someone around to make decisions at each check-in and quick feedback on any issues all keep things on track. If any of these slip, launch usually slips too, so it’s worth getting time in diaries early.
- Have a backup plan. Once your database moves over to CMS 13 there’s no undo button, so you’ll want a tested backup and a clear plan for who decides to roll back if something goes wrong. Hopefully you’ll never need it, but it’s good peace of mind.
Step 5: Bring your team along
At the end of the day, it’s the people using the CMS every day who’ll decide whether the upgrade feels like a success. A few things that really help:
- Be clear on who’s doing what. Know who on your side signs things off, who’s testing and who makes the final call. It saves a lot of back and forth.
- Choose testers who use the site every day. Your editors know the site inside out and will spot things a test script won’t, like a page that looks slightly off or a form that’s behaving strangely.
- Give people a heads up. If the login or the way into the CMS is changing, let your team know before launch day rather than them finding out on a Monday morning.
- Agree what counts as a big problem. Decide upfront how you’ll rate issues and how quickly they need fixing, so there’s no debate in the moment.
- Make sure the knowledge doesn’t walk out the door. At the end of the project your team should get a clear handover of what was done and why, so whoever works on the site next isn’t starting from scratch.

Step 6: Test what matters and launch with confidence
Testing an upgrade isn’t really about trying out shiny new features. It’s about making sure nothing important has broken along the way. We check that:
- pages look and work the same as before
- your editors can create, preview and publish content without any workarounds
- forms, logins and any connected systems still work
- tracking and SEO are still in place, so your analytics and Google rankings don’t quietly take a hit
- the site is at least as fast as it was before
We also agree a simple rule for launch: no serious issues left open. Anything smaller gets agreed by both sides, with a date to fix it.
Once you’re live, we keep a close eye on things for the first few days. Most issues only show up once real people start using the site, so having support on hand straight away makes a big difference.
Step 7: Think about what’s next
Going live is really just the start. Once you’re settled on CMS 13, you can start making the most of it, ideally linking back to the goals you set at the very beginning. A few ideas:
- Give your editors Visual Builder so they can build pages more easily.
- Use the new AI search tools to see how AI is reading your content, and act on what you find.
- Look at smarter search options if you swapped out your old search tool like-for-like.
- Tidy up anything Optimizely have already said will be removed in CMS 14, so your next upgrade is a smaller job.
Thinking about your move to CMS 13?
CMS 13 is a great chance to get your website on a solid, supported footing and give your team (and your audiences) better ways to work with your content. The upgrades that go smoothly are the ones where everyone knows why they’re doing it, takes the time to understand what they’re working with, keeps the scope realistic and brings their people along for the ride.
If you’re starting to think about your CMS 13 upgrade, we’d love to chat. Get in touch and we can talk you through a discovery session to map out your route, any risks and what comes next.