Modernize CMS 13 Without Architectural Chaos
Graph adoption, search redesign, and legacy dependencies create hidden migration risk. We modernize Optimizely platforms through governed, AI-augmented migration delivery.
Upgrade Complexity
Complexity depends on where you start.
| Current Version | Nature of Update | Key Focus Areas | Main Challenges |
|---|---|---|---|
| CMS 12 → 13 | Architectural transition | Graph adoption, search redesign, Opti ID | Search logic, Graph queries, integrations |
| CMS 11 → 13 | Platform + architecture | ASP.NET Core, Graph, identity | Legacy dependencies, refactoring |
| CMS 10 and earlier | Staged or partial replatforming | CMS 12 readiness, API changes, architecture alignment | Deprecated components, cumulative complexity |
For organizations on CMS 11 or earlier, Optimizely recommends upgrading to CMS 12 first before introducing CMS 13-specific architectural changes.
Know Where Migration Risk Actually Lives
Identify architectural complexity before it becomes delivery delay and technical debt.
Book a Migration ReviewOptiup Framework
OptiUP is the tooling layer behind our migration delivery.
It encodes migration patterns into rules that:
scan,
transform,
validate,
stabilize codebases
Without engineers manually rewriting thousands of lines.
How Optiup Works
Scan
Static analysis identifies:
- versions,
- packages,
- dependencies,
- custom code patterns,
- migration risks.
No production access required.
Convert
Automated fixers handle deterministic migration tasks:
- project file migration,
- package updates,
- dependency injection conversion,
- configuration migration,
- authentication updates,
- logging,
- legacy API cleanup.
Verify
Eight automated validation criteria detect issues before deployment.
Fix Loop
AI-assisted convergence:
- analyses build errors,
- applies fixes,
- reruns validation,
- stabilizes builds iteratively.
The process does not move forward until each step passes.
Accelerate Migration Without Losing Control
Use AI where automation creates value, while engineering governs platform quality and business logic.
Explore the OptiUP Framework0→ 0
Build errors resolved
0/ 9
Migration milestones passed
→0
Original CMS 11 database migrated with all content preserved
Automation Vs Engineering
| Automated by OptiUP | Requires Engineering Expertise |
| Project file and package migration | Business logic in custom modules |
| Program.cs / Startup.cs generation | Complex integrations and third-party plugins |
| web.config → appsettings.json migration | Commerce migration |
| DI container replacement | Search migration (Find → Graph) |
| Logging and authentication updates | Editorial workflow validation |
| Static verification against defined criteria | Graph and Opti ID architecture alignment |
AI accelerates migration.
Engineering governs the platform.
FAQ
Does OptiUP fully automate migration?
No. Architecture, business logic, and integrations still require engineering expertise.
Does OptiUP require production access?
No. Initial analysis works through source code and architecture review only.
Can migration risks be detected before deployment?
Yes. Validation criteria identify issues before runtime deployment.
Is Commerce migration included automatically?
No. Commerce migration is treated as a separate engineering workstream.
Can CMS 10 environments move directly to CMS 13?
Usually not. Most require staged modernization and CMS 12 readiness validation first.
Plan Migration Around Architecture
Reduce delivery risk with structured migration planning and AI-assisted modernization.
Schedule a Technical Discussion