---
id: MAXCONNECT-TECH-002
title: OpenShift drives migration complexity
type: TECH
state: amber
area: F-feasibility
purpose: notebooklm-tier2
priority: S
work_kind: A
provenance: research
confidence: medium-high
triangulated: true
engagement: maxconnect
sources:
- uri: file://notebooklm/answers/20260611T200650Z-01-product-workings.md
role: supporting
- uri: file://notebooklm/answers/20260611T200650Z-02-architecture-integrations.md
role: supporting
- uri: file://notebooklm/answers/20260611T200650Z-03-migration-risks.md
role: supporting
- uri: file://notebooklm/answers/20260611T200650Z-04-licensing-economics-buyers.md
role: supporting
- uri: file://notebooklm/answers/20260611T200650Z-05-ecosystem-community-language.md
role: supporting
- uri: file://notebooklm/answers/20260611T200650Z-06-maxconnect-opportunity.md
role: supporting
- uri: file://notebooklm/answers/20260611T200650Z-07-community-opportunity.md
role: supporting
- uri: file://corpus/H-synthesis/tier2-notebooklm-synthesis-20260611.md
role: supporting
relates_to: []
feeds_atoms: []
open_questions: []
needs_validation: []
resolution_log: []
module:
---
The expanded corpus repeatedly points to Red Hat OpenShift, Kubernetes operators, embedded WebSphere Liberty, MongoDB/core services, persistent storage, relational database connections, API keys, and resource sizing as central MAS operating requirements.
For smaller Maximo customers, the OpenShift layer is likely a major source of confusion and partner dependence because it changes installation, upgrades, monitoring, backups, scaling, and troubleshooting.