# Planning a contact center platform migration Canonical: https://warmtransfer.net/knowledge/contact-center-migration-planning Last verified: 2026-09-25 Planning a contact center platform migration requires coordinating telephony cutover, application architecture, operational readiness, and data retention[^37][^14][^15]. AWS guidance warns that treating a contact center migration purely as a technology delivery project risks overlooking staff training and operating model changes[^37]. ## Migration Strategy and Cutover Approach AWS guidance positions customers as the highest priority for avoiding disruption during migration, even if that results in more disruption for agents and backend system operators[^13]. AWS guidance states that zero downtime may not be achievable depending on opening hours and backend systems, and that accepting minimal disruption can reduce project risk or cost elsewhere[^17]. AWS guidance also recommends keeping the period of running two contact center platforms as short as practical to avoid increased costs, operator burden, and the risk of administrative errors such as applying changes to the wrong platform[^45]. For Avaya migrations, AWS guidance outlines 2 approaches: a phased approach that moves components or interactive voice response (IVR) business functions 1 at a time, or a full migration switching everything at once[^38]. A phased approach is often preferred for complex systems or risk minimization, whereas a full migration can be faster but requires meticulous planning and preparation[^38][^26]. When migrating an IVR workload in phases, such as by business unit, AWS guidance notes that selecting which business unit moves first is extremely important[^22]. AWS guidance advises against replicating a complex on-premises DTMF or speech IVR as-is in Amazon Lex, though it permits rehosting very basic call flows first and modernizing later[^16]. Migration plans must review all existing call flows to ensure that logic is neither duplicated nor dropped while operating 2 telephony systems concurrently[^41]. AWS guidance contrasts hard-to-change infrastructure components with contact flows and caller journeys, which are easy to change, recommending starting early with a basic flow and iterating with stakeholders instead of rigidly adhering to an initial design[^33]. In addition, AWS guidance advises obtaining security compliance approval for items such as call-recording encryption policies, along with design sign-offs, before starting the build[^46]. ## Telephony Cutover and Cross-Platform Routing AWS guidance identifies 2 primary methods to cut over public numbers to Amazon Connect: backend repointing of a non-geographic number (NGN) to a Connect-hosted direct inward dialing (DDI) number, or porting the number itself[^14]. Backend repointing requires no change to the public-facing number, can be scheduled for a specific date and time, and is usually handled via a service request to the NGN carrier[^36]. Before porting, charging models should be compared because some NGN or toll-free providers do not charge for out-of-hours calls when they handle schedule checks and messaging directly[^35]. AWS guidance notes that number porting can take several weeks, recommending early ticket submission to establish the cutover date and time[^39]. Under United States regulation 47 CFR 52.35(a), carriers must complete simple wireline-to-wireline and intermodal ports within 1 business day unless a longer interval is requested by the customer or new provider[^20]. Non-simple wireline-to-wireline and intermodal requests must complete within 4 business days under 47 CFR 52.35(d), unless requested otherwise[^19]. Under 47 CFR 52.35(e)(2), intermodal ports include wireline-to-wireless, wireless-to-wireline, and ports involving interconnected VoIP service[^18]. Before a port completes, call forwarding from the legacy platform to the new platform can be used to move agents early and enable rapid rollback without carrier dependency[^25]. However, AWS guidance recommends not leaving number forwarding in place for long, because each forwarded call is charged inbound on the old DDI, outbound on the forward and inbound on the new DDI, and uses an outbound circuit for every inbound call[^24]. Organizations often transition agents in waves by line of business or job role over several months, requiring cross-platform call routing during the transition[^2]. To manage this, AWS guidance advises: - Reserving dedicated PSTN DDI numbers exclusively for cross-platform transfers to measure, report, and prioritize transfer traffic separately[^50]. - Migrating teams that frequently transfer calls to one another in the same wave to avoid building cross-platform data-exchange mechanisms[^57]. - Using a rolling DNIS technique when split teams require call-attached data, such as caller security status, passed across platforms for extended periods[^42]. ## Configuration Migration and Platform Tools Flow definitions and resource mappings require platform-specific migration handling: - **Amazon Connect:** Flows can be exported only if they contain fewer than 200 blocks and have a total size under 1 MB, requiring larger flows to be split[^10]. Imported flows resolve resources by name when instance ARNs differ, and flows with unresolved required parameters cannot be published[^11]. Bulk migrations across instances rely on an API procedure (`ListContactFlows`, `DescribeContactFlow`, `CreateContactFlow`, `UpdateContactFlowContent`) that fails with `InvalidContactFlow` unless an explicit ARN-to-ARN mapping for queues, flows, and prompts is provided[^7]. Importing legacy-format flows stopped being supported after the 03/31/2026 deadline[^12]. AWS also recommends maintaining separate AWS accounts for development, testing, and production instances to establish billing boundaries and isolate changes[^44]. - **Genesys Cloud:** Architect exports flows as i3-format files by flow type; imports into a new organization may require manual updates to elements such as data actions to resolve validation errors[^30]. For PureConnect hybrid deployments running CIC 2016 R3 or later, administrators can pair a Genesys Cloud organization directly from CIC Interaction Administrator to sync user records, extensions, and phone numbers continuously[^28]. - **Webex Contact Center:** Cisco provides a UCCX discovery tool (v3.5) that extracts configuration into an Excel workbook and exports audio prompts into a zip file for bulk upload[^55]. To prevent dependency errors, Cisco defines an import order starting with `MultimediaProfiles.csv` and `Site.csv`, continuing through profiles, skills, teams, entry points, and queues, and concluding with `Users.csv`[^52]. Webex Contact Center bulk CSV files cannot exceed 5000 rows[^58]. Cisco notes that this migration tool continues to evolve and may not support all recent features[^54]. ## Operational Readiness, Testing, and Cutover Governance Operational changes are frequently overlooked until late in a migration[^49]. AWS guidance recommends treating handover into business-as-usual operations as a formal go-live approval gate, including securing agreement on platform ownership prior to go-live[^5]. Finance teams must also be notified before cutover that usage billing will shift into AWS billing structures to ensure costs map to correct business units[^6]. Operational preparation items include: - **Agent Workstations:** Shifting from desk phones to softphones introduces an operational learning curve that requires dedicated training time[^47]. Agents with accessibility needs regarding tactile hardware should be consulted so their requirements are included in softphone designs[^1]. Legacy habits, such as relying on Wi-Fi instead of wired networks, present technical risks, and concurrent apps like Teams or Zoom can compete for audio peripherals[^34]. For remote agents on VPNs, split tunneling voice traffic helps avoid latency, concentrator saturation, and egress bandwidth costs[^56]. - **Validation and Testing:** User acceptance testing must evaluate softphones running simultaneously with standard desktop workloads to ensure host performance remains acceptable[^51]. Operational test plans should include raising test tickets to level 1 support to trace escalation procedures[^48]. Back-office routing, case escalations, and cross-department transfers must also be verified in test scripts[^4]. ## Data Retention and Historical Migration AWS guidance identifies 2 strategies for historical reporting and recordings: migrating records to the target platform following format compatibility checks, or archiving data in place until its retention schedule expires[^15]. In-place archiving is often more cost-effective for rarely accessed data on purchased systems[^3]. In the field, practitioners report that transforming legacy Cisco Unified Contact Center Enterprise (UCCE) historical tables into a cloud schema is impractical, choosing instead to export raw database tables prior to decommissioning and querying them alongside cloud data via a BI reporting layer[^21]. Security teams must verify target retention architectures and logging capabilities[^43]. | Platform | Data type | Retention limit | |---|---|---| | Amazon Connect | Contact records | 24 months[^8] | | Amazon Connect | Analytics data lake | 25 months (fixed rolling window)[^9] | | Genesys Cloud | Conversation data | 90 days to 5 years (undefined by default)[^29] | | Genesys Cloud | Screen recordings | Up to 365 days[^31] | | Genesys Cloud | Customer audit logs | 365 days[^27] | | Genesys Cloud | SIP diagnostic PCAP | 21 days[^27] | | Webex Contact Center | Recordings & transcripts | 7 to 3600 days (1095 days default in new orgs)[^60] | Genesys Cloud sets no maximum or minimum limits for standard voice and digital recordings, but documentation states certain data types must be exported routinely during normal operations due to volume limits[^31][^32]. In Webex Contact Center, existing organizations retain recordings indefinitely until configured otherwise, and expired recordings are purged oldest first without recovery options[^60][^59]. ## See also - See also [Migrating Unified CCE or Unified CCX to Webex Contact Center](https://warmtransfer.net/knowledge/webex-cc-migration-from-ucce). - See also [Porting numbers to Webex Calling](https://warmtransfer.net/knowledge/webex-calling-number-porting). - See also [Voice for remote and home workers](https://warmtransfer.net/knowledge/remote-worker-voice). - See also [Troubleshooting Webex Contact Center flows](https://warmtransfer.net/knowledge/wxcc-flow-troubleshooting). ## Applicability Applies to: Amazon Web Services Amazon Connect Customer, Amazon Web Services Amazon Lex, Amazon Web Services Amazon Connect Customer analytics data lake, Genesys Cloud, Genesys Cloud Architect, Genesys Cloud for PureConnect, Cisco Webex Contact Center, and Cisco Unified Contact Center Enterprise. Deployments: on-premises, hybrid, multi-tenant, and any. Sources checked 2026-09-25. The Cisco UCCX-to-Webex Contact Center discovery tool claims apply to tool version v3.5[^55]. The Genesys Cloud for PureConnect pairing integration requires Customer Interaction Center (CIC) release 2016 R3 or later[^28]. Porting intervals under 47 CFR 52.35 apply specifically to telecommunications providers in the United States[^20][^19]. Amazon Connect legacy flow format import support ended on 03/31/2026[^12]. ## What remains uncertain Toll-free number porting rules and the RespOrg change process for contact center cutover are not covered by the sources below. Official Genesys migration methodology for Engage or PureConnect to Genesys Cloud is not covered by the sources below. Current Amazon Connect default service quotas for concurrent calls and phone numbers per instance are not covered by the sources below. Emergency calling validation from agent devices as a cutover test item is not covered by the sources below. Third-party cross-vendor flow and IVR conversion tools and their fidelity are not covered by the sources below. Migration guidance for other contact center platforms is not covered by the sources below. Webex Contact Center Analyzer and reporting data retention periods are not covered by the sources below. Sector retention obligations for recordings and interaction records under PCI DSS and financial services recordkeeping standards are not covered by the sources below. ## Sources [^1]: AWS guidance recommends consulting agents with accessibility concerns about moving from tactile desk phones, and including their feedback in soft phone design specifications. Source: [Operational considerations - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/ops-considerations.html), Shifting to soft phones, second bullet. Checked 2026-09-25. [^2]: AWS guidance says organizations often move agents in groups by line of business or job type, a phase that can last several months and requires cross-platform call transfers between teams during that time. Source: [Technical considerations - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/tech-considerations.html), Transferring calls between other platforms and Amazon Connect, first paragraph. Checked 2026-09-25. [^3]: AWS guidance says archiving legacy data in place may be more cost-effective than migrating it, especially when the data is on a purchased platform and rarely accessed, so that using two portals for old and new data is practical. Source: [Technical considerations - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/tech-considerations.html), Data migration, second bullet. Checked 2026-09-25. [^4]: AWS guidance recommends including back-office task workflows and routing, such as call transfers and case escalations that may change, in migration test scripts. Source: [Operational considerations - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/ops-considerations.html), Back office. Checked 2026-09-25. [^5]: AWS guidance recommends making the new platform's handover into business-as-usual operations a gate for go-live approval, and agreeing platform ownership before go-live. Source: [Overview - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/overview.html), Targeted business outcomes, bullet Smooth and timely service introduction. Checked 2026-09-25. [^6]: AWS guidance recommends telling finance teams before go-live that platform charges move into AWS billing after migration, so that costs can be mapped to the right business unit. Source: [Operational considerations - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/ops-considerations.html), Billing. Checked 2026-09-25. [^7]: To move hundreds of Amazon Connect flows between instances, AWS documents an API procedure (ListContactFlows, DescribeContactFlow, CreateContactFlow, UpdateContactFlowContent) that requires an ARN-to-ARN mapping for queues, flows and prompts; without it, UpdateContactFlowContent fails with InvalidContactFlow. Source: [Migrate flows to an instance, Region, or environment in Connect Customer](https://docs.aws.amazon.com/connect/latest/adminguide/migrate-contact-flows.html), procedure and paragraph following the Destination instance list. Checked 2026-09-25. [^8]: Amazon Connect contact records remain available in the instance for 24 months from when the contact was initiated. Source: [Data model for Connect Customer contact records](https://docs.aws.amazon.com/connect/latest/adminguide/ctr-data-model.html), Important things to know, second bullet. Checked 2026-09-25. [^9]: The Amazon Connect analytics data lake keeps a fixed, rolling 25-month window of data that cannot be changed; to keep data longer, for example for statutory retention, customers must copy it to storage they control before it ages out. Source: [Data retention in the Connect Customer analytics data lake](https://docs.aws.amazon.com/connect/latest/adminguide/data-lake-data-retention.html), first paragraph and Retaining data past the 25-month window. Checked 2026-09-25. [^10]: Amazon Connect can export a flow only if it has fewer than 200 blocks and a total size under 1 MB; AWS recommends splitting larger flows. Source: [Import and export flows between flow designers in Connect Customer](https://docs.aws.amazon.com/connect/latest/adminguide/contact-flow-import-export.html), Export limitations. Checked 2026-09-25. [^11]: When an Amazon Connect flow is imported into a different instance, resource ARNs no longer match, so Connect falls back to resolving resources by name; a flow with an unresolved required parameter cannot be published. Source: [Import and export flows between flow designers in Connect Customer](https://docs.aws.amazon.com/connect/latest/adminguide/contact-flow-import-export.html), Resolve resources in imported flows. Checked 2026-09-25. [^12]: AWS set 03/31/2026 as the date when importing legacy-format flows into the Amazon Connect flow designer stops being supported; flows kept offline in the old format had to be converted before then. Source: [Import and export flows between flow designers in Connect Customer](https://docs.aws.amazon.com/connect/latest/adminguide/contact-flow-import-export.html), Important box: Deprecation of Legacy Flow Import Support. Checked 2026-09-25. [^13]: AWS guidance ranks customers as the highest priority for avoiding disruption during migration, even if that means more disruption for agents and backend system operators. Source: [Overview - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/overview.html), Primary vision, bullet User list in order of significance. Checked 2026-09-25. [^14]: AWS guidance describes two ways to cut over public numbers to Amazon Connect: backend repointing of a non-geographic (NGN) number to a Connect-hosted DDI, or porting the number itself. Source: [Technical considerations - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/tech-considerations.html), Cutover approaches for porting numbers. Checked 2026-09-25. [^15]: For legacy call recordings and reporting statistics, AWS guidance offers two options: migrate the data to the new platform after a feasibility check such as audio format compatibility, or archive it in place and decommission it when the minimum retention period expires. Source: [Technical considerations - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/tech-considerations.html), Data migration. Checked 2026-09-25. [^16]: AWS guidance does not recommend replicating a complex on-premises DTMF or speech IVR as-is in Amazon Lex; where existing call flows are very basic, it allows rehosting first and modernizing later. Source: [Decision-making processes - Migrating an on-premises Avaya contact center to Amazon Connect and Amazon Lex (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/migrate-avaya-to-connect-lex/decision-making-processes.html), Step 3: Choose a migration strategy. Checked 2026-09-25. [^17]: AWS guidance says zero downtime may not be achievable, depending on opening hours and backend systems, and that accepting minimal disruption can reduce risk or cost elsewhere in the project. Source: [Overview - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/overview.html), Primary vision, bullet Minimal user disruption. Checked 2026-09-25. [^18]: 47 CFR 52.35(e)(2) defines intermodal ports to include wireline-to-wireless, wireless-to-wireline and ports involving interconnected VoIP service. Source: [47 CFR § 52.35 - Porting Intervals](https://www.law.cornell.edu/cfr/text/47/52.35), paragraph (e)(2). Checked 2026-09-25. [^19]: Under 47 CFR 52.35(d), non-simple wireline-to-wireline and intermodal port requests must be completed within four business days, unless the new provider or the customer asks for a longer period. Source: [47 CFR § 52.35 - Porting Intervals](https://www.law.cornell.edu/cfr/text/47/52.35), paragraph (d). Checked 2026-09-25. [^20]: Under 47 CFR 52.35(a), US carriers must complete simple wireline-to-wireline and intermodal ports within one business day, unless the new provider or the customer asks for a longer period. Source: [47 CFR § 52.35 - Porting Intervals](https://www.law.cornell.edu/cfr/text/47/52.35), paragraph (a). Checked 2026-09-25. [^21]: Practitioners report that converting UCCE historical reporting data into a cloud vendor's reporting schema is impractical, and instead dump the historical database tables before decommissioning and query them next to the new platform's data through a BI layer (field report). Source: [UCCE Migration Planning: The UC Engineer's Guide to Field Parity, Reporting, and Data Retention](https://www.metropolis.com/articles/ucce-migration-planning.php), Historical data strategy section. Checked 2026-09-25. [^22]: AWS guidance says an IVR workload can be migrated in phases, such as by business unit, and that choosing which business unit goes first is extremely important. Source: [Migration planning - Migrating an on-premises Avaya contact center to Amazon Connect and Amazon Lex (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/migrate-avaya-to-connect-lex/migration-plan.html), Preparing your data. Checked 2026-09-25. [^23]: The flow export formats documented by Amazon Connect (JSON with instance-specific ARNs) and Genesys Cloud Architect (i3 flow files) are platform-native, so a cross-vendor migration should plan to rebuild routing logic rather than import it (inferred). Source: [Import and export flows between flow designers in Connect Customer](https://docs.aws.amazon.com/connect/latest/adminguide/contact-flow-import-export.html), Flows are exported to JSON files; Resolve resources in imported flows. Checked 2026-09-25. [^24]: AWS guidance recommends not leaving number forwarding in place for long, because each forwarded call is charged inbound on the old DDI, outbound on the forward and inbound on the new DDI, and uses an outbound circuit for every inbound call. Source: [Technical considerations - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/tech-considerations.html), Cutover approaches for porting numbers, Number porting, bullet Number forwarding. Checked 2026-09-25. [^25]: AWS guidance describes forwarding calls from the old platform to a number on the new platform as an optional step before the port completes, allowing agents to move before the port and allowing fast rollback by changing forwarding rules, with no carrier dependency. Source: [Technical considerations - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/tech-considerations.html), Cutover approaches for porting numbers, Number porting, bullet Number forwarding. Checked 2026-09-25. [^26]: AWS guidance says a full migration may be faster but requires meticulous planning and preparation. Source: [Decision-making processes - Migrating an on-premises Avaya contact center to Amazon Connect and Amazon Lex (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/migrate-avaya-to-connect-lex/decision-making-processes.html), Step 2, bullet Full migration. Checked 2026-09-25. [^27]: In Genesys Cloud, customer audit data is kept for 365 days and SIP diagnostic PCAP files for 21 days, both fixed periods. Source: [Data retention periods and export functionality by feature - Genesys Cloud Resource Center](https://help.genesys.cloud/articles/data-retention-periods-by-feature/), retention table, audit and SIP PCAP rows. Checked 2026-09-25. [^28]: Genesys Cloud for PureConnect lets CIC administrators set up a paired Genesys Cloud organization from within CIC Interaction Administrator, which continuously syncs CIC user information such as name, email, extension and phone numbers; it requires CIC 2016 R3 or later. Source: [Genesys Cloud for PureConnect - Genesys Cloud Resource Center](https://help.genesys.cloud/articles/genesys-cloud-for-cic/), article body, overview and requirements. Checked 2026-09-25. [^29]: Genesys Cloud conversation data retention can be set between 90 days and five years, and the retention period is undefined by default. Source: [Data retention periods and export functionality by feature - Genesys Cloud Resource Center](https://help.genesys.cloud/articles/data-retention-periods-by-feature/), retention table, conversation/interaction data row. Checked 2026-09-25. [^30]: Genesys Cloud Architect exports flows as i3-format files by flow type; importing a flow from another organization may need configuration updates, for example to data actions, and Architect reports validation errors until they are fixed. Source: [Import or export a flow - Genesys Cloud Resource Center](https://help.genesys.cloud/articles/import-export-call-flow/), export and import procedures. Checked 2026-09-25. [^31]: Genesys Cloud sets no minimum or maximum retention for voice and digital recordings, but screen recordings can be kept for at most 365 days. Source: [Data retention periods and export functionality by feature - Genesys Cloud Resource Center](https://help.genesys.cloud/articles/data-retention-periods-by-feature/), retention table, recordings and screen recordings rows. Checked 2026-09-25. [^32]: Genesys documentation states that, because of data volume, some data types must be exported routinely while the platform is in use. Source: [Data retention periods and export functionality by feature - Genesys Cloud Resource Center](https://help.genesys.cloud/articles/data-retention-periods-by-feature/), introductory text above the retention table. Checked 2026-09-25. [^33]: AWS guidance contrasts infrastructure components, which are hard to change, with contact flows and caller journeys, which are easy to change, and recommends starting early with a basic flow and iterating with stakeholders rather than rigidly following the original design. Source: [Overview - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/overview.html), Targeted business outcomes, bullet Agile customer experience. Checked 2026-09-25. [^34]: AWS guidance lists legacy agent habits as a migration risk: agents used to Wi-Fi may resist a wired-connection requirement, and other collaboration apps such as Teams or Zoom on the same device can clash with contact center calls for audio devices. Source: [Technical considerations - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/tech-considerations.html), Legacy habits. Checked 2026-09-25. [^35]: AWS guidance cautions that some NGN or toll-free providers do not charge for out-of-hours calls when they handle the hours check and messaging themselves, so this should be included when comparing charging models before porting. Source: [Technical considerations - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/tech-considerations.html), Number porting, first bullet. Checked 2026-09-25. [^36]: In AWS guidance, NGN backend repointing needs no change to the public-facing number, is usually handled as a service request to the NGN carrier, and can be scheduled for a specific date and time. Source: [Technical considerations - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/tech-considerations.html), Cutover approaches for porting numbers, NGN backend repointing. Checked 2026-09-25. [^37]: AWS guidance warns that treating a contact center migration purely as a technology delivery project risks overlooking staff training and operating model changes. Source: [Overview - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/overview.html), Pillars of successful migration, first paragraph. Checked 2026-09-25. [^38]: AWS guidance for Avaya migrations gives two approaches: phased, moving components or IVR business functions one at a time, which is often preferred for complex systems or to minimize risk; or a full migration that switches everything at once. Source: [Decision-making processes - Migrating an on-premises Avaya contact center to Amazon Connect and Amazon Lex (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/migrate-avaya-to-connect-lex/decision-making-processes.html), Step 2: Choose between a phased approach or a full migration. Checked 2026-09-25. [^39]: AWS guidance says number porting can take several weeks and recommends filing the port request early and using the ticket to fix the cutover date and time. Source: [Technical considerations - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/tech-considerations.html), Number porting, second bullet. Checked 2026-09-25. [^40]: The several-week porting lead time in AWS guidance does not conflict with the FCC one- and four-business-day intervals. The FCC intervals govern completion after a valid request, apply only to US local wireline and intermodal ports, and allow longer periods at the customer's request, while project lead time also covers preparing the request and scheduling the cutover (inferred). Source: [47 CFR § 52.35 - Porting Intervals](https://www.law.cornell.edu/cfr/text/47/52.35), paragraphs (a) and (d), read against aws-pg-connect-migration-tech Number porting. Checked 2026-09-25. [^41]: AWS guidance says the migration plan must review all existing call flows and, during a hybrid period with two telephony systems, make sure no part of a flow is duplicated and no important logic is dropped. Source: [Migration planning - Migrating an on-premises Avaya contact center to Amazon Connect and Amazon Lex (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/migrate-avaya-to-connect-lex/migration-plan.html), Evaluating the current architecture, final paragraph. Checked 2026-09-25. [^42]: For teams that stay split across platforms for a long time and need call-attached data (such as caller security status) passed on transfer, AWS guidance names a technique called rolling DNIS. Source: [Technical considerations - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/tech-considerations.html), Transferring calls between other platforms and Amazon Connect, bullet Transfers with call attached data. Checked 2026-09-25. [^43]: AWS guidance says the security team should confirm that the proposed target architecture meets organizational requirements such as retention policies, and that logging is planned and documented. Source: [Migration planning - Migrating an on-premises Avaya contact center to Amazon Connect and Amazon Lex (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/migrate-avaya-to-connect-lex/migration-plan.html), Defining cloud infrastructure and security requirements. Checked 2026-09-25. [^44]: AWS guidance recommends separate AWS accounts for development, testing and production Amazon Connect instances, both to limit the impact of changes and to set billing boundaries. Source: [Technical considerations - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/tech-considerations.html), Separate AWS accounts. Checked 2026-09-25. [^45]: AWS guidance recommends keeping the period of running two contact center platforms as short as practical, because a longer period raises cost, operator burden and the risk of errors such as making changes on the wrong platform. Source: [Overview - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/overview.html), Primary vision, bullet Pace. Checked 2026-09-25. [^46]: AWS guidance advises getting security compliance approval of decisions such as call-recording encryption policy, and sign-off on designs, before starting the build, because infrastructure decisions are costly to change later. Source: [Overview - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/overview.html), Targeted business outcomes, bullet Improved total cost of ownership (TCO). Checked 2026-09-25. [^47]: When agents move from desk phones to a soft phone, AWS guidance recommends building adjustment time into the training schedule and expecting a learning curve after go-live. Source: [Operational considerations - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/ops-considerations.html), Shifting to soft phones, first bullet. Checked 2026-09-25. [^48]: AWS guidance recommends testing the support model before go-live by raising a test incident to the level 1 support desk and tracking it through the support process to find gaps. Source: [Operational considerations - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/ops-considerations.html), Support model. Checked 2026-09-25. [^49]: AWS guidance notes that user training, process changes and service desk changes are often overlooked until the migration project is close to completion. Source: [Overview - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/overview.html), Targeted business outcomes, bullet Smooth and timely service introduction. Checked 2026-09-25. [^50]: AWS guidance recommends using PSTN DDI numbers reserved only for cross-platform transfers, so that transfers can be measured and reported separately and prioritized differently. Source: [Technical considerations - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/tech-considerations.html), Transferring calls between other platforms and Amazon Connect, second paragraph. Checked 2026-09-25. [^51]: AWS guidance recommends user acceptance testing where end-users run the soft phone alongside their usual business applications, to check that devices still perform well. Source: [Operational considerations - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/ops-considerations.html), Device inventory, third bullet. Checked 2026-09-25. [^52]: Cisco specifies a recommended CSV import order for UCCX-to-Webex Contact Center migration to avoid dependency errors. It starts with MultimediaProfiles.csv and Site.csv, then covers profiles, skills, teams, entry points and queues, and ends with Users.csv. Source: [Migrate Cisco Unified Contact Center Express to Webex Contact Center](https://help.webex.com/en-us/article/0hd75db/Migrate-Cisco-Unified-Contact-Center-Express-to-Webex-Contact-Center), Import section, recommended order paragraph. Checked 2026-09-25. [^53]: The Cisco UCCX migration article lists configuration entities (profiles, skills, teams, entry points, queues, users) and prompts as tool output but does not list CCX scripts, which suggests CCX script logic has to be rebuilt as Webex Contact Center flows rather than converted automatically (inferred). Source: [Migrate Cisco Unified Contact Center Express to Webex Contact Center](https://help.webex.com/en-us/article/0hd75db/Migrate-Cisco-Unified-Contact-Center-Express-to-Webex-Contact-Center), Excel sheet entity list. Checked 2026-09-25. [^54]: Cisco says the UCCX migration tool is still evolving and may not support all of the latest features. Source: [Migrate Cisco Unified Contact Center Express to Webex Contact Center](https://help.webex.com/en-us/article/0hd75db/Migrate-Cisco-Unified-Contact-Center-Express-to-Webex-Contact-Center), limitations note. Checked 2026-09-25. [^55]: Cisco's UCCX-to-Webex Contact Center discovery tool (v3.5) extracts CCX configuration into an Excel workbook for review and editing, plus a zip file of audio prompts for bulk upload. Source: [Migrate Cisco Unified Contact Center Express to Webex Contact Center](https://help.webex.com/en-us/article/0hd75db/Migrate-Cisco-Unified-Contact-Center-Express-to-Webex-Contact-Center), Discovery and data extraction section. Checked 2026-09-25. [^56]: For remote agents on VPN, AWS guidance recommends considering split tunneling for voice traffic, because backhauling it through the data center increases latency, VPN concentrator load and internet egress charges. Source: [Technical considerations - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/tech-considerations.html), Remote agents. Checked 2026-09-25. [^57]: To avoid building call-attached-data exchange between platforms, AWS guidance suggests migrating teams that frequently transfer calls to each other together, and shortening the cross-platform transfer period. Source: [Technical considerations - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance)](https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-migration-connect/tech-considerations.html), Transferring calls between other platforms and Amazon Connect, bullet Transfers without call attached data. Checked 2026-09-25. [^58]: Webex Contact Center bulk operations limit each import CSV file to 5000 rows. Source: [Migrate Cisco Unified Contact Center Express to Webex Contact Center](https://help.webex.com/en-us/article/0hd75db/Migrate-Cisco-Unified-Contact-Center-Express-to-Webex-Contact-Center), Import section, row limitation note. Checked 2026-09-25. [^59]: Webex Contact Center purges recordings and transcripts past their retention period oldest first; purge on the exact scheduled day is not guaranteed, and purged recordings cannot be recovered. Source: [Manage Retention and Purge Recordings and Transcripts in Webex Contact Center](https://help.webex.com/en-us/article/uimme/Manage-Retention-and-Purge-Recordings-and-Transcripts-in-Webex-Contact-Center), purge and limitations sections. Checked 2026-09-25. [^60]: Webex Contact Center keeps voice recordings and transcripts for 1095 days by default in new organizations; in existing organizations they are kept indefinitely until an administrator sets a period. The configurable range is 7 to 3600 days. Source: [Manage Retention and Purge Recordings and Transcripts in Webex Contact Center](https://help.webex.com/en-us/article/uimme/Manage-Retention-and-Purge-Recordings-and-Transcripts-in-Webex-Contact-Center), default retention and configuration sections. Checked 2026-09-25.