---
id: MAXCONNECT-TECH-003
title: Legacy integrations need rewrites
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:
---
Migration evidence identifies integration discontinuities: RMI is no longer supported, legacy authentication patterns such as maxauth are displaced, REST/API-key usage becomes central, and older messaging patterns may need Kafka or supported JMS replacement.
This implies that migration readiness must include an inventory of integrations, custom Java/classes, automation scripts, workflows, object structures, and service accounts before any credible MAS plan.