Source note · Migrating from Avaya Aura
An ASA field export is not a complete configuration capture, because at least one station attribute (service link extension) cannot be exported, so migration discovery should also read the live CM configuration.
inferred · Checked 2026-09-25
- Vendor
- Avaya
- Product
- Communication Manager
- Subsystem
- data-export
- Deployment
- on-premises
- Region
- not restricted
- Release range
- not release-scoped
- Status
- inferred
- Checked
- 2026-09-25
Sources
- How to export the active 'station service link extension' from a station from the Communication Manager with Site Administration? — Avaya · tier 2 current vendor documentation · FAQ116513, Answer section
Cite this note
APA
WarmTransfer. (2026, September 25). Migrating from Avaya Aura: source note avaya-aura-migration-export-not-config-complete. WarmTransfer. https://warmtransfer.net/knowledge/claims/avaya-aura-migration-export-not-config-complete
BibTeX
@misc{warmtransfer-claim-avaya-aura-migration-export-not-config-complete,
title = {Migrating from Avaya Aura: source note avaya-aura-migration-export-not-config-complete},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/avaya-aura-migration-export-not-config-complete},
note = {Source note avaya-aura-migration-export-not-config-complete, checked 2026-09-25}
}