Start with evidence, not an asset count
Confirm the exact product, edition, version, milestone type, and vendor source. A product family policy may not apply to every edition. Preserve the source and checked-at time before prioritizing work.
Identify the affected service
Map only enough context to make a decision: business owner, technical owner, criticality, exposure, recovery dependency, and the next safe maintenance window. A complete CMDB is not a prerequisite.
Choose migrate, isolate, extend, or retire
Document the selected treatment, named replacement when authoritative, compatibility constraints, licensing impact, and the vendor confirmation still required. Extended support should have an explicit cost and end date.
Keep the lifecycle date under observation
Vendors can revise published schedules. Subscribe the relevant team to source-backed changes and preserve old and new values so planning assumptions remain explainable.
Make it operational
Follow the relevant product versions, assign their criticality and exposure, then let verified source changes update the planning record.
Start with five version units free