Source note · Migrating from Avaya Aura
Gateways of the same G450 model can fall on opposite sides of a support boundary because support depends on hardware vintage, so migration inventories need the vintage and not just the model.
field report · Checked 2026-09-25
- Vendor
- Avaya
- Product
- G430
- Subsystem
- inventory
- Deployment
- on-premises
- Region
- not restricted
- Release range
- Aura 10.2
- Status
- field report
- Checked
- 2026-09-25
Sources
- Avaya End of Life List: Models & EOL Dates (2026) — ContactCenterGuide.com (Foretel Solutions) · tier 4 archived vendor documentation · G430/G450 section, emphasis note on identical-looking G450s
Cite this note
APA
WarmTransfer. (2026, September 25). Migrating from Avaya Aura: source note avaya-aura-migration-g4xx-vintage-field-risk. WarmTransfer. https://warmtransfer.net/knowledge/claims/avaya-aura-migration-g4xx-vintage-field-risk
BibTeX
@misc{warmtransfer-claim-avaya-aura-migration-g4xx-vintage-field-risk,
title = {Migrating from Avaya Aura: source note avaya-aura-migration-g4xx-vintage-field-risk},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/avaya-aura-migration-g4xx-vintage-field-risk},
note = {Source note avaya-aura-migration-g4xx-vintage-field-risk, checked 2026-09-25}
}