Optimizely CMS 13 Upgrades Are Faster With AI - Here's the Claude Code Prompt That Gets You Started

Apr 10, 2026

Optimizely CMS 12 to 13 upgrade using Claude Code AIInterest in Optimizely CMS 13 has been incredibly high since it reached general availability and for good reason, it's the biggest shift the platform has seen in years, bringing with it AI tooling, a modern visual editing experience and a composable architecture that changes how you think about content delivery.

If you're on CMS 12 and wondering how to get started, I wanted to share something that has genuinely changed how I approach upgrades: using Claude Code to kick off the process.

Here's the prompt I used:

Claude CODE Prompt

You are a world class .NET developer expert in all things .NET including all versions of .NET core. You are also an expert in the PaaS version of Optimizely CMS (previously known as Episerver CMS). Use the /effort maximum available in Claude. 

First things first lets create a claude.md file to keep a track of what we are doing and to ensure I can start the conversation back up again whenever its needed.

I am engaging you to assist with an upgrade project for Optimizely CMS. The current latest version of Optimizely CMS is v13.x. I have an older project running on Optimizely CMS v12.x. I want you to do the following:

1. Research all there is to know about the PaaS edition of Optimizely PaaS CMS v12.x and v13.x
2. Analyse the current codebase to check what needs to be done in order to upgrade to the latest version
3. List out all add-ons installed that are not compatible with CMS v13
4. Create a plan to go through the upgrade steps
5. Check with me on the plan so we can fine tune the steps
6. Ensure the plan is written to the claude.md file
7. Once the steps above are complete we can proceed with the upgrade

Points to note:

There is a running local version of v12.x version of the CMS running at https://your.current.url/ which is running on this machine which should be left untouched, this is your reference to check back on as part of the upgrade. The site to be upgraded is running here: https://url.to.instance.to.be.upgraded/ 

Let me know if you want me to provide credentials so you can log into admin mode and/or if you need any access to the database. You can use this to find out the URL structure and what the site does.

The work will also include installing Optimizely Graph in place of Optimizely Search and Nav, let me know when you need the Graph credentials for this. You can start your research on the .NET SDK from Graph here: https://world.optimizely.com/blogs/jake-minard/dates/2026/3/introducing-optimizely-cms-13-graph-sdk/

 That single starting point sets the upgrade in motion and lets you continue the work in a fraction of the time previous upgrades would have taken. It's not magic, you still need to understand what you're doing and it requires the mother of all code reviews but it removes a huge amount of the mechanical groundwork.

Why upgrade?

If you're weighing up the effort, here's what's waiting for you on the other side:

  • Opal tooling - access to Optimizely's AI agent orchestration platform directly within the platform
  • Visual Builder - a modern, drag-and-drop experience for building pages
  • Optimizely Graph - structured content querying for headless and composable architectures
  • Optimizely Connect Platform - a growing library of integrations to connect your stack

Each of these represents a meaningful shift in what you can do with the platform. Opal alone is worth the move.

Getting started

The prompt above kicks things off, but here are a few things worth knowing before you dive in:

  • Optimizely Graph is a requirement for CMS 13 - it's not optional and replaces Search and Navigation. If you're an Optimizely DXP customer, the good news is that Graph is included in your subscription. If you're not on DXP, you'll need to factor this in. Jake Minard has a great write-up on the .NET SDK for Graph which makes the transition familar and easier than ever: Introducing the Optimizely CMS 13 Graph SDK
  • Expect API changes — there are breaking changes across content management, routing, security, and the UI layer. Review the Breaking Changes in CMS 13 documentation carefully before starting
  • Use the CLI throughout — dotnet commands are your friend here; Claude Code handles a lot of this but it helps to know what's happening under the hood

The upgrade process is well within reach and Claude Code AI assistance makes it faster than it's ever been.

Have you started your CMS 13 upgrade? I'd love to hear how you're getting on — find me on LinkedIn or X.

This blog represents personal views and experiences. For official Optimizely documentation, visit docs.developers.optimizely.com.

Comments