WarmTransfer
migration · published

Migrating from Avaya CS1000

Verified 2026-10-14 · 51 sources · tier 2–4

Avaya Device Adapter Snap-in acts as a protocol converter that lets deployed CS 1000 UNIStim IP, digital and analog devices be reused in an Avaya Aura solution 6. From Avaya Aura Release 10.2 onward, Avaya Aura does not support the Avaya Device Adapter Snap-in 11.

How Device Adapter works

Avaya Device Adapter is delivered as a snap-in that runs on the Avaya Breeze platform 8. Device Adapter connects to Avaya Aura Session Manager for SIP signalling and phone registration 7. Session Manager relies on Communication Manager for call services, and System Manager provides management 7. Device Adapter forwards XSM and PSTAT alarms from migrated TDM hardware to System Manager as SNMP traps 43.

Avaya Device Adapter Snap-in 10.1.2 is documented as interoperating with Session Manager, Communication Manager and System Manager 10.1.2 and Avaya Breeze platform 3.8.1.1 23. The Aura 10.2.x documentation catalog lists 2 Device Adapter documents: the Avaya Device Adapter Snap-in Reference and a Device Adapter User Guide for Avaya Experience Platform On-Prem (formerly Call Center Elite) agents 4.

TDM hardware constraints

Migrating CS 1000 analog and digital (TDM) sets to Device Adapter requires Media Gateway Controllers (MGC) or MG-XPEC units to drive the line cards 9. Device Adapter supports only Intelligent Peripheral Equipment (IPE) digital and analog line cards 5. The following hardware limits are documented: 47 46 48

  • NTDK50 and NTAK12 cabinets are not supported because they do not support an MGC, so sites must move line cards to a supported cabinet such as NTAK11 or replace the sets with Avaya J-series phones 47.
  • The MG-XPEC does not connect to Device Adapter over T1 or E1 links 46.
  • For Carrier Remote or Fiber Remote NT8D37 IPE shelves, the T1/E1 or fiber link must be replaced with an IP network connection to work with Device Adapter 48.

Licensing

Each instance of the Avaya Device Adapter Snap-in requires a license 24. The first Avaya Breeze platform server instance for Device Adapter is a Suite entitlement, and every subsequent Breeze server instance must be purchased 26. ProVision and its Nortel Migration Tool (NMT) are provided free of charge to Device Adapter users for migrating MGCs and CS 1000 UNIStim IP, digital and analog phones 27. CS 1000 endpoints migrated through Device Adapter carry an Avaya Aura endpoint licensing cost, priced through Avaya sales 25. Each endpoint migrated through Device Adapter consumes the same Aura capacity allocation as any other Aura SIP endpoint, so Aura must be sized for the added endpoints 32.

Planning sequence

Avaya's Device Adapter migration checklist puts "Determine migration dial plan" after CS 1000 discovery and choosing the migration approach, and before designing the Aura solution 15. The checklist requires System Manager, Session Manager and Communication Manager to be deployed, active and ready before CS 1000 data is migrated 13. Before running ProVision, the checklist calls for a Personal Directory backup XML file, a CS 1000 Call Server database backup archive and a record of the CS 1000 properties used by the migration 14. CS 1000 endpoint data and Media Gateway configuration are migrated with ProVision before Avaya Breeze and Device Adapter are deployed 17. UNIStim endpoints are switched from CS 1000 to Device Adapter before Media Gateway Controllers are configured for the Device Adapter environment, registered and secured 16.

Cutover procedure

The first step in switching from CS 1000 to Device Adapter is to put the Avaya Breeze platform cluster in Accept Service mode 38. UNIStim endpoints are then moved from CS 1000 to Device Adapter by updating their node IP address (S1), either manually or through DHCP 42. In a phased cutover, only the UNIStim endpoints belonging to the current phase have their S1 node IP updated, while a full cutover updates all endpoints at once 40. After cutover, a CS 1000 signaling server that hosts only UNIStim IP lines is shut down 41. If that signaling server also hosts H.323 or SIP trunks, a gatekeeper or proxy servers, only the IP lines are removed from it 41. Avaya states the switch procedure needs a maintenance window of about 1 hour 39.

Phased migration and coexistence

Avaya's phased migration divides existing CS 1000 endpoints into groups migrated in batches to reduce downtime and the risk of a major fault 31. Group features such as Multiple Appearance Directory Numbers (MADN) break if their members are split across migration phases 34. Members spread across several MGCs require migrating those MGCs together 34.

During coexistence, routing has to work in both directions: 33 30

  • Calls from CS 1000 to already-migrated endpoints can be routed with vacant number routing or with specific digit manipulation tables on CS 1000 33.
  • Avaya Aura must have SIP routes back to CS 1000 for the extension ranges that remain on CS 1000 30.
  • Migrated users can use Aura's centralized SIP trunks for PSTN access or keep using CS 1000 TDM DID trunks, with vacant number routing on CS 1000 sending calls on to Aura 35.

We infer that Avaya's documented coexistence pattern preserves CS 1000 extension dialling by mirrored routing (vacant number routing or digit manipulation on CS 1000 and SIP routes back on Aura) rather than by an automated import of the CS 1000 dial plan 22. Field reports suggest that, as of 2014, CS1000 migrations were typically phased rather than single cutovers, with voicemail and desk phones the hardest elements to retire 2.

Aura 10.2 and later

From Avaya Aura Release 10.2 onward, Avaya Aura does not support the Avaya Device Adapter Snap-in 11. Avaya's "Discontinued support for Avaya Device Adapter Snap-in" page states the non-support in 10.2 but names no replacement product or migration alternative 18. We infer that a CS 1000 site moving to Avaya Aura 10.2 or later cannot carry its UNIStim, digital or analog sets forward through Device Adapter and should plan for endpoint replacement such as J-series SIP phones 20.

Webex Calling routing to on-premises PBXs

A Webex Calling dial plan routes calls matching enterprise dial patterns (E.164 numbers, extensions or SIP URI domains) to an on-premises destination through a trunk or route group, and applies enterprise-wide 50. Webex Calling's Calls to On-Premises Extensions setting routes unknown 2 to 10 digit extensions dialled at a location to a PBX over an existing trunk or route group 51. Webex Calling supports third-party SBC integration only with certificate-based trunks 49.

Vendor position history

In October 2014 Avaya said it would add no new CS1000 features but would continue to issue patches and service packs 1. In January 2019 Avaya promoted a Loyalty2gether programme offering upgrade discounts, services credits and device offers to CS1000 customers moving to current Avaya Aura on-premises, cloud or hybrid 3.

See also

See also Avaya CS1000 and Nortel Meridian platform reference.

See also CUCM to Webex Calling migration.

Applicability

Applies to: Avaya Device Adapter Snap-in, Avaya Aura, Avaya Communication Server 1000, Avaya Breeze, Avaya ProVision, and Cisco Webex Calling. Deployments: on-premises and multi-tenant. Sources checked 2026-10-14. The Device Adapter migration procedure, hardware limits, licensing and checklist are documented for release 10.1.x 6 38 15. The documented interoperability set is Device Adapter 10.1.2 with Session Manager, Communication Manager and System Manager 10.1.2 and Avaya Breeze platform 3.8.1.1 23. Avaya Aura 10.2 and later does not support Device Adapter 11. Avaya's 2019 programme addressed CS1000 customers moving to Avaya Aura on-premises, cloud or hybrid 3.

What remains uncertain

The CS 1000 end of services parts support date is not covered by the sources below. A CS 1000 to Webex Calling migration and coexistence design is not covered by the sources below. Aura services support terms after end of manufacturer support for the release used with Device Adapter are not covered by the sources below. A CS 1000 migration path to another vendor's cloud phone service through Direct Routing is not covered by the sources below. Whether NMT converts CDP, UDP or ESN data into Communication Manager or Session Manager is not covered by the sources below. We infer that the documented coexistence pattern relies on mirrored routing rather than an automated import of the CS 1000 dial plan 22. Carry-over of E911 location and ELIN data from CS 1000 is not covered by the sources below. Device Adapter supports only IPE digital and analog line cards 5. A list of supported phone models, fax and modem devices for Device Adapter is not covered by the sources below. Whether a non-Avaya PBX platform is a suitable CS 1000 replacement is not covered by the sources below. Avaya's discontinuation page names no replacement product or migration alternative for Device Adapter in 10.2 and later 18.

See also

Migrates from

Sources

  1. 1
    In October 2014 Avaya said it would add no new CS1000 features but would continue to issue patches and service packs.
    The CS1000 and the Larger Migration · The CS1000 and the Larger Migration, paragraphs on Avaya's plans · Checked 2026-10-14
  2. 2
    No Jitter reported in 2014 that CS1000 migrations were typically phased rather than single cutovers, with voicemail and desk phones the hardest elements to retire.field report
    The CS1000 and the Larger Migration · The CS1000 and the Larger Migration, migration challenges paragraphs · Checked 2026-10-14
  3. 3
    In January 2019 Avaya promoted a Loyalty2gether programme offering upgrade discounts, services credits and device offers to CS1000 customers moving to current Avaya Aura on-premises, cloud or hybrid.
    What's Next for Your CS1000? · What's Next for Your CS1000?, Loyalty2gether paragraph · Checked 2026-10-14
  4. 4
    The Aura 10.2.x documentation catalog lists two Device Adapter documents: the Avaya Device Adapter Snap-in Reference and a Device Adapter User Guide for Avaya Experience Platform On-Prem (formerly Call Center Elite) agents.
    Avaya Device Adapter documentation (Avaya Aura Documentation Catalog 10.2.x) · Avaya Device Adapter documentation, document table · Checked 2026-10-14
  5. 5
    Device Adapter supports only Intelligent Peripheral Equipment (IPE) digital and analog line cards.
    Avaya Device Adapter Snap-in Overview (Avaya Device Adapter Snap-in Reference 10.1) · Avaya Device Adapter Snap-in Overview, TDM paragraph · Checked 2026-10-14
  6. 6
    Avaya Device Adapter Snap-in acts as a protocol converter that lets deployed CS 1000 UNIStim IP, digital and analog devices be reused in an Avaya Aura solution.
    Avaya Device Adapter Snap-in Overview (Avaya Device Adapter Snap-in Reference 10.1) · Avaya Device Adapter Snap-in Overview, opening paragraph · Checked 2026-10-14
  7. 7
    Device Adapter connects to Avaya Aura Session Manager for SIP signalling and phone registration, Session Manager relies on Communication Manager for call services, and System Manager provides management.
    Avaya Device Adapter Snap-in Overview (Avaya Device Adapter Snap-in Reference 10.1) · Avaya Device Adapter Snap-in Overview, architecture paragraph · Checked 2026-10-14
  8. 8
    Avaya Device Adapter is delivered as a snap-in that runs on the Avaya Breeze platform.
    Avaya Device Adapter Snap-in Overview (Avaya Device Adapter Snap-in Reference 10.1) · Avaya Device Adapter Snap-in Overview, opening paragraph · Checked 2026-10-14
  9. 9
    Migrating CS 1000 analog and digital (TDM) sets to Device Adapter requires Media Gateway Controllers (MGC) or MG-XPEC units to drive the line cards.
    Avaya Device Adapter Snap-in Overview (Avaya Device Adapter Snap-in Reference 10.1) · Avaya Device Adapter Snap-in Overview, TDM paragraph · Checked 2026-10-14
  10. 10
    Avaya's Aura 10.1 notice ends manufacturer support for Avaya Aura Release 10.1.x components effective 1 January 2026.
    End of Manufacturer Support Notice (Avaya Aura Platform Release 10.1) · Aura 10.1 EoMS notice (doc 101090414, revision dated 11 February 2026), dates section; page not extracted · Checked 2026-10-14
  11. 11
    From Avaya Aura Release 10.2 onward, Avaya Aura does not support the Avaya Device Adapter Snap-in.
    Avaya Aura Release 10.2.x components (What is New in Avaya Aura Release 10.2.x) · Avaya Aura Release 10.2.x components, note below component table · Checked 2026-10-14
  12. 12
    Avaya's Aura 10.1 notice declares no end of sale for Aura Release 10 because 10.1 and 10.2 are both offered as Release 10, with 10.2 the current release.
    End of Manufacturer Support Notice (Avaya Aura Platform Release 10.1) · Aura 10.1 EoMS notice (doc 101090414), end of sale statement; page not extracted · Checked 2026-10-14
  13. 13
    The checklist requires System Manager, Session Manager and Communication Manager to be deployed, active and ready before CS 1000 data is migrated.
    Migration and deployment checklist (Avaya Device Adapter Snap-in Reference 10.1) · Migration and deployment checklist, rows 7-8 · Checked 2026-10-14
  14. 14
    Before running ProVision, the checklist calls for a Personal Directory backup XML file, a CS 1000 Call Server database backup archive and a record of the CS 1000 properties used by the migration.
    Migration and deployment checklist (Avaya Device Adapter Snap-in Reference 10.1) · Migration and deployment checklist, rows 10-12 · Checked 2026-10-14
  15. 15
    Avaya's Device Adapter migration checklist puts 'Determine migration dial plan' after CS 1000 discovery and choosing the migration approach, and before designing the Aura solution.
    Migration and deployment checklist (Avaya Device Adapter Snap-in Reference 10.1) · Migration and deployment checklist, rows 1-5 · Checked 2026-10-14
  16. 16
    In the checklist, UNIStim endpoints are switched from CS 1000 to Device Adapter before Media Gateway Controllers are configured for the Device Adapter environment, registered and secured.
    Migration and deployment checklist (Avaya Device Adapter Snap-in Reference 10.1) · Migration and deployment checklist, rows 20-23 · Checked 2026-10-14
  17. 17
    In the checklist, CS 1000 endpoint data and Media Gateway configuration are migrated with ProVision before Avaya Breeze and Device Adapter are deployed.
    Migration and deployment checklist (Avaya Device Adapter Snap-in Reference 10.1) · Migration and deployment checklist, rows 14-16 · Checked 2026-10-14
  18. 18
    Avaya's 'Discontinued support for Avaya Device Adapter Snap-in' page states the non-support in 10.2 but names no replacement product or migration alternative.
    Discontinued support for Avaya Device Adapter Snap-in · Discontinued support for Avaya Device Adapter Snap-in, full page body · Checked 2026-10-14
  19. 19
    Avaya indicates that CS 1000M and Meridian 1 devices that can be migrated to a CS 1000E architecture (IP between call server and line cards) can then be migrated to Device Adapter, provided cards such as the MG-XPEC and XSM are of a supported vintage.
    Hardware requirements for migration (Avaya Device Adapter Snap-in Reference 10.1) · Hardware requirements for migration, body paragraph · Checked 2026-10-14
  20. 20
    A CS 1000 site moving to Avaya Aura 10.2 or later cannot carry its UNIStim, digital or analog sets forward through Device Adapter and should plan for endpoint replacement such as J-series SIP phones.inferred
    Avaya Aura Release 10.2.x components (What is New in Avaya Aura Release 10.2.x) · Avaya Aura Release 10.2.x components note · Checked 2026-10-14
  21. 21
    Because Device Adapter is unsupported from Aura 10.2 and Aura 10.1 is reported past manufacturer support since 1 January 2026, a CS 1000 to Aura migration that reuses CS 1000 sets via Device Adapter lands on a release line without manufacturer support as of 2026-10-14.inferred
    Avaya Aura Release 10.2.x components (What is New in Avaya Aura Release 10.2.x) · Avaya Aura Release 10.2.x components note, combined with doc 101090414 dates section · Checked 2026-10-14
  22. 22
    Avaya's documented coexistence pattern preserves CS 1000 extension dialling by mirrored routing (vacant number routing or digit manipulation on CS 1000 and SIP routes back on Aura) rather than by an automated import of the CS 1000 dial plan.inferred
    Phased migration (Avaya Device Adapter Snap-in Reference 10.1) · Phased migration, internal routing paragraph; Licensing ProVision bullet · Checked 2026-10-14
  23. 23
    Avaya Device Adapter Snap-in 10.1.2 is documented as interoperating with Session Manager, Communication Manager and System Manager 10.1.2 and Avaya Breeze platform 3.8.1.1.
    Interoperability (Avaya Device Adapter Snap-in Reference 10.1.x) · Interoperability, product and release table · Checked 2026-10-14
  24. 24
    Each instance of the Avaya Device Adapter Snap-in requires a license.
    Licensing (Avaya Device Adapter Snap-in Reference 10.1) · Licensing, Avaya Device Adapter Snap-in bullet · Checked 2026-10-14
  25. 25
    CS 1000 endpoints migrated through Device Adapter carry an Avaya Aura endpoint licensing cost, priced through Avaya sales.
    Licensing (Avaya Device Adapter Snap-in Reference 10.1) · Licensing, Avaya Aura bullet · Checked 2026-10-14
  26. 26
    The first Avaya Breeze platform server instance for Device Adapter is a Suite entitlement; every subsequent Breeze server instance must be purchased.
    Licensing (Avaya Device Adapter Snap-in Reference 10.1) · Licensing, Avaya Breeze platform bullet · Checked 2026-10-14
  27. 27
    ProVision and its Nortel Migration Tool (NMT) are provided free of charge to Device Adapter users for migrating MGCs and CS 1000 UNIStim IP, digital and analog phones.
    Licensing (Avaya Device Adapter Snap-in Reference 10.1) · Licensing, ProVision bullet · Checked 2026-10-14
  28. 28
    Optional migration of CS 1000 feature key labels with NMT requires a database.rec file retrieved from the source CS 1000.
    Getting Started with ProVision Tool Suite - ADA · Getting Started with ProVision Tool Suite - ADA, NMT prerequisites; page not extracted · Checked 2026-10-14
  29. 29
    Avaya's Nortel Migration Tool in ProVision takes a CS 1000 system as source and Avaya Aura Communication Manager and System Manager as targets, converting CS 1000 sets to CM stations.
    Getting Started with ProVision Tool Suite - ADA · Getting Started with ProVision Tool Suite - ADA, NMT section; page not extracted · Checked 2026-10-14
  30. 30
    During phased migration Avaya Aura must have SIP routes back to CS 1000 for the extension ranges that remain on CS 1000.
    Phased migration (Avaya Device Adapter Snap-in Reference 10.1) · Phased migration, internal routing paragraph · Checked 2026-10-14
  31. 31
    Avaya's phased migration divides existing CS 1000 endpoints into groups migrated in batches to reduce downtime and the risk of a major fault.
    Phased migration (Avaya Device Adapter Snap-in Reference 10.1) · Phased migration, opening paragraph · Checked 2026-10-14
  32. 32
    Each endpoint migrated through Device Adapter consumes the same Aura capacity allocation as any other Aura SIP endpoint, so Aura must be sized for the added endpoints.
    Phased migration (Avaya Device Adapter Snap-in Reference 10.1) · Phased migration, resources paragraph · Checked 2026-10-14
  33. 33
    Calls from CS 1000 to already-migrated endpoints can be routed with vacant number routing or with specific digit manipulation tables on CS 1000.
    Phased migration (Avaya Device Adapter Snap-in Reference 10.1) · Phased migration, internal routing paragraph · Checked 2026-10-14
  34. 34
    Group features such as Multiple Appearance Directory Numbers (MADN) break if their members are split across migration phases, and members spread across several MGCs require migrating those MGCs together.
    Phased migration (Avaya Device Adapter Snap-in Reference 10.1) · Phased migration, group features paragraph · Checked 2026-10-14
  35. 35
    During phased migration, migrated users can use Aura's centralized SIP trunks for PSTN access or keep using CS 1000 TDM DID trunks, with vacant number routing on CS 1000 sending calls on to Aura.
    Phased migration (Avaya Device Adapter Snap-in Reference 10.1) · Phased migration, PSTN access paragraph · Checked 2026-10-14
  36. 36
    Avaya's CS 1000 lifecycle bulletin PSN003499 states that CS 1000 Release 7.6 is at End of Manufacturer Support for software.
    PSN003499r2 - Communications Server 1000 (CS 1000) Life Cycle Management Status Update · PSN003499 (r2, July 2021), lifecycle status section; page not extracted · Checked 2026-10-14
  37. 37
    Per PSN003499, Avaya Tier IV (design) support for CS 1000 Release 7.6 ended after 9 April 2019, with a final service pack (SP 11) planned.
    PSN003499r2 - Communications Server 1000 (CS 1000) Life Cycle Management Status Update · PSN003499 (r2, July 2021), support milestones section; page not extracted · Checked 2026-10-14
  38. 38
    The first step in switching from CS 1000 to Device Adapter is to put the Avaya Breeze platform cluster in Accept Service mode.
    Switching from CS 1000 to Avaya Device Adapter Snap-in · Switching from CS 1000 to Avaya Device Adapter Snap-in, procedure step 1 · Checked 2026-10-14
  39. 39
    Avaya states the CS 1000 to Device Adapter switch procedure needs a maintenance window of about one hour.
    Switching from CS 1000 to Avaya Device Adapter Snap-in · Switching from CS 1000 to Avaya Device Adapter Snap-in, note after procedure · Checked 2026-10-14
  40. 40
    In a phased cutover, only the UNIStim endpoints belonging to the current phase have their S1 node IP updated; a full cutover updates all endpoints at once.
    Switching from CS 1000 to Avaya Device Adapter Snap-in · Switching from CS 1000 to Avaya Device Adapter Snap-in, procedure step 2 · Checked 2026-10-14
  41. 41
    After cutover, a CS 1000 signaling server that hosts only UNIStim IP lines is shut down; if it also hosts H.323 or SIP trunks, a gatekeeper or proxy servers, only the IP lines are removed from it.
    Switching from CS 1000 to Avaya Device Adapter Snap-in · Switching from CS 1000 to Avaya Device Adapter Snap-in, procedure step 3 · Checked 2026-10-14
  42. 42
    UNIStim endpoints are moved from CS 1000 to Device Adapter by updating their node IP address (S1), either manually or through DHCP.
    Switching from CS 1000 to Avaya Device Adapter Snap-in · Switching from CS 1000 to Avaya Device Adapter Snap-in, procedure step 2 · Checked 2026-10-14
  43. 43
    Device Adapter forwards XSM and PSTAT alarms from migrated TDM hardware to System Manager as SNMP traps.
    Supported TDM hardware (Avaya Device Adapter Snap-in Reference 10.1) · Supported TDM hardware, final note · Checked 2026-10-14
  44. 44
    Device Adapter supports MGC parts NTDW60BA, NTDW60BBE5, NTDW98AAE5, NTDW98AAE6 and NTDW98AAGS for Option 11 class, CS 1000E and MG1010 cabinets and chassis.
    Supported TDM hardware (Avaya Device Adapter Snap-in Reference 10.1) · Supported TDM hardware, MGC section · Checked 2026-10-14
  45. 45
    The MG-XPEC supported by Device Adapter for Meridian 1 and CS 1000M large-system IPE shelves is part NTDW20AAE6.
    Supported TDM hardware (Avaya Device Adapter Snap-in Reference 10.1) · Supported TDM hardware, MG-XPEC and IPE shelves section · Checked 2026-10-14
  46. 46
    The MG-XPEC does not connect to Device Adapter over T1 or E1 links.
    Supported TDM hardware (Avaya Device Adapter Snap-in Reference 10.1) · Supported TDM hardware, limitations notes · Checked 2026-10-14
  47. 47
    NTDK50 and NTAK12 cabinets are not supported for Device Adapter because they do not support an MGC; sites must move line cards to a supported cabinet such as NTAK11 or replace the sets with Avaya J-series phones.
    Supported TDM hardware (Avaya Device Adapter Snap-in Reference 10.1) · Supported TDM hardware, unsupported cabinets note · Checked 2026-10-14
  48. 48
    For Carrier Remote or Fiber Remote NT8D37 IPE shelves, the T1/E1 or fiber link must be replaced with an IP network connection to work with Device Adapter.
    Supported TDM hardware (Avaya Device Adapter Snap-in Reference 10.1) · Supported TDM hardware, limitations notes · Checked 2026-10-14
  49. 49
    Webex Calling supports third-party SBC integration only with certificate-based trunks.
    Configure trunks, route groups, and dial plans for Webex Calling · Configure trunks, route groups, and dial plans for Webex Calling, trunk types section · Checked 2026-10-14
  50. 50
    A Webex Calling dial plan routes calls matching enterprise dial patterns (E.164 numbers, extensions or SIP URI domains) to an on-premises destination through a trunk or route group, and applies enterprise-wide.
    Configure trunks, route groups, and dial plans for Webex Calling · Configure trunks, route groups, and dial plans for Webex Calling, Dial Plans section · Checked 2026-10-14
  51. 51
    Webex Calling's Calls to On-Premises Extensions setting routes unknown 2 to 10 digit extensions dialled at a location to a PBX over an existing trunk or route group.
    Configure trunks, route groups, and dial plans for Webex Calling · Configure trunks, route groups, and dial plans for Webex Calling, Calls to On-Premises Extensions section · Checked 2026-10-14

Documents

tier 2 current vendor documentation

Avaya Aura Release 10.2.x components (What is New in Avaya Aura Release 10.2.x)

Avaya · 2026-04-01 · accessed 2026-10-14

tier 2 current vendor documentation

Avaya Device Adapter documentation (Avaya Aura Documentation Catalog 10.2.x)

Avaya · 2023-12-07 · accessed 2026-10-14

tier 2 current vendor documentation

Avaya Device Adapter Snap-in Overview (Avaya Device Adapter Snap-in Reference 10.1)

Avaya · 2021-02-03 · accessed 2026-10-14

tier 2 current vendor documentation

Configure trunks, route groups, and dial plans for Webex Calling

Cisco Systems, Inc. (Webex Help Center) · 2026-09-07 · accessed 2026-09-16

tier 2 current vendor documentation

Discontinued support for Avaya Device Adapter Snap-in

Avaya · 2023-09-21 · accessed 2026-10-14

tier 2 current vendor documentation

End of Manufacturer Support Notice (Avaya Aura Platform Release 10.1)

Avaya · 2024-05-24 · accessed 2026-09-25

tier 2 current vendor documentation

Getting Started with ProVision Tool Suite - ADA

Avaya · 2018-01-01 · accessed 2026-10-14

tier 2 current vendor documentation

Hardware requirements for migration (Avaya Device Adapter Snap-in Reference 10.1)

Avaya · 2019-09-27 · accessed 2026-10-14

tier 2 current vendor documentation

Interoperability (Avaya Device Adapter Snap-in Reference 10.1.x)

Avaya · 2022-12-22 · accessed 2026-10-14

tier 2 current vendor documentation

Licensing (Avaya Device Adapter Snap-in Reference 10.1)

Avaya · 2019-07-05 · accessed 2026-10-14

tier 2 current vendor documentation

Migration and deployment checklist (Avaya Device Adapter Snap-in Reference 10.1)

Avaya · 2020-12-21 · accessed 2026-10-14

tier 2 current vendor documentation

Phased migration (Avaya Device Adapter Snap-in Reference 10.1)

Avaya · 2020-12-11 · accessed 2026-10-14

tier 2 current vendor documentation

PSN003499r2 - Communications Server 1000 (CS 1000) Life Cycle Management Status Update

Avaya · 2021-07-15 · accessed 2026-10-14

tier 2 current vendor documentation

Supported TDM hardware (Avaya Device Adapter Snap-in Reference 10.1)

Avaya · 2020-11-24 · accessed 2026-10-14

tier 2 current vendor documentation

Switching from CS 1000 to Avaya Device Adapter Snap-in

Avaya · 2021-05-19 · accessed 2026-10-14

tier 4 archived vendor documentation

The CS1000 and the Larger Migration

No Jitter · 2014-10-14 · accessed 2026-10-14

tier 4 archived vendor documentation

What's Next for Your CS1000?

International Avaya User Group · 2019-01-14 · accessed 2026-10-14

Cite this page

APA

WarmTransfer. (2026, October 14). Migrating from Avaya CS1000. WarmTransfer. https://warmtransfer.net/knowledge/avaya-cs1000-migration

BibTeX

@misc{warmtransfer-avaya-cs1000-migration,
  title  = {Migrating from Avaya CS1000},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/avaya-cs1000-migration},
  note   = {Verified 2026-10-14}
}