---
id: MAXCONNECT-TECH-013
title: SAML user mismatches can cause data migration conflicts
type: TECH
state: red
area: F-feasibility
purpose: notebooklm-tier2-decomposition
priority: A
work_kind: A
provenance: research
confidence: medium
triangulated: false
engagement: maxconnect
sources:
- uri: file://notebooklm/answers/20260611T200650Z-03-migration-risks.md
role: supporting
relates_to: []
feeds_atoms: []
open_questions: []
needs_validation:
- Validate with Maximo practitioners how frequently this affects smaller legacy customers.
resolution_log:
- 2026-06-12: Decomposed from broad NotebookLM synthesis into pack-grade atom for Max Connect Discovery.
module:
---
If a legacy Maximo environment uses SAML and user IDs do not match usernames, the migration can hit a data conflict. The NotebookLM synthesis says a specific OpenShift ConfigMap may be needed to migrate data with the correct SAML ID field.