After deploying Avaya Contact Center – Extended Capacity, you can migrate contact center data and endpoints from your previous contact center. The time required to migrate your contact center depends on the contact center capacity and components. With contact centers that require complex networking, the migration process might take up to two years. For a simplified migration, Avaya recommends that you distribute the process into several phases, including planning, component migration, data migration, and migration verification.

Before data migration, you must consider your contact center topology and capacity. Certain contact center solutions, such as Avaya Aura® Call Center Elite, require several independent nodes to support high agent capacity. Avaya Contact Center – Extended Capacity is a single-server solution supporting up to 30,000 concurrent agents. You can migrate from your previous contact center to Avaya Contact Center – Extended Capacity without purchasing additional peripherals, such as endpoints and contact center applications.

You must also pre-plan and maintain component migration, such as migrating to internal AE Services. Avaya Contact Center – Extended Capacity supports two types of AE Services implementation: external and internal. External AE Services is part of the Avaya Aura® infrastructure and must be connected to Avaya Contact Center – Extended Capacity manually. Internal AE Services is integrated with the Routing Core Server and connects to Avaya Contact Center – Extended Capacity during the contact center deployment. For more information about internal AE Services administration, see Administering Application Enablement Services for Avaya Contact Center – Extended Capacity.

For automated data migration, the solution provides the Extraction Utility, which collects the data from your previous contact center and generates a .json file. You can use the generated file for data import on the Configuration Server web portal. To preserve your contact center performance, you must distribute data migration in phases and migrate one bulk of contact center objects at a time. When you are importing data from multiple contact center nodes, the Configuration Server validates the data and lists the duplicate objects in the migration report.