Migrating from Avaya to Amazon Connect: The Real Cost and Timeline for UK Contact Centres
Avaya's financial turbulence has forced thousands of UK contact centre leaders into a decision they were hoping to defer. If you are running Avaya Aura, Avaya IP Office, or an Avaya-based CCaaS platform, the question is no longer whether to migrate but when and to what.
Amazon Connect is the destination most enterprises land on. It is AWS-native, consumption-based, and genuinely capable of supporting enterprise-grade contact centre operations at scale. But the migration journey is where most projects go wrong, and where most vendors give you numbers that bear no resemblance to reality.
This post gives you the real numbers, the real timeline, and the decisions you need to make before you spend a penny.
Why UK Contact Centres Are Moving Now
The trigger is not just Avaya's Chapter 11 filing. It is the compounding effect of several pressures arriving at once:
- Support costs rising sharply. Avaya maintenance contracts have increased 20 to 40 percent for many UK customers since 2023. Third-party support fills some gaps but introduces compliance risk.
- Integration debt. Legacy Avaya infrastructure was not built for modern CRM, AI, or workforce management integrations. Every new capability requires expensive middleware.
- Regulatory pressure. FCA Consumer Duty, GDPR, and PCI DSS requirements are harder to evidence on ageing infrastructure. Compliance teams are pushing for platforms with native audit trails.
- Talent scarcity. Avaya-certified engineers are retiring or retraining. Finding people who can maintain your existing estate is genuinely difficult.
What Amazon Connect Actually Costs
This is where most conversations go wrong. Amazon Connect is priced on consumption, which sounds appealing until you add up everything you actually need to run a production contact centre.
Amazon Connect Core Pricing (as of 2024, UK region)
| Component | Pricing Model | Indicative Cost |
|---|---|---|
| Inbound telephony | Per minute | £0.004 per minute |
| Outbound telephony | Per minute | £0.012 per minute |
| Agent usage | Per hour connected | £0.018 per hour |
| Amazon Connect Cases | Per case | £0.12 per case |
| Contact Lens (analytics) | Per minute analysed | £0.015 per minute |
| Voice ID | Per transaction | £0.012 per transaction |
For a 100-seat contact centre handling 500,000 inbound minutes per month, you are looking at roughly £8,000 to £14,000 per month in pure AWS consumption before any implementation or support costs. Compare that to a typical Avaya maintenance contract of £15,000 to £25,000 per month for a similar estate, and the economics are clear.
The Full Cost Picture
Where budgets blow out is in the surrounding costs that do not appear on the AWS bill:
Implementation and configuration: A production-grade Amazon Connect deployment for a 100 to 500 seat UK contact centre typically costs £80,000 to £250,000 depending on complexity. This covers IVR design, CRM integration, telephony porting, agent desktop build, and testing. Number porting: UK geographic and non-geographic number porting to Amazon Connect takes 4 to 12 weeks depending on your current carrier. Porting fees vary but budget £500 to £2,000 for a typical DDI estate. Training: Amazon Connect is genuinely different from Avaya. Supervisor and agent training typically runs 2 to 5 days. Administrator and developer training is more substantial. Budget £5,000 to £20,000 depending on team size. Third-party integrations: Salesforce, Dynamics, ServiceNow, and Zendesk all have Amazon Connect connectors, but they require configuration and testing. Budget £10,000 to £40,000 per integration depending on complexity. Ongoing managed service or internal resource: Someone has to own this platform. If that is internal, you need at least one AWS-trained contact centre engineer. If it is outsourced, budget £3,000 to £8,000 per month for a managed service.The Real Migration Timeline
Most vendors quote 8 to 16 weeks. The reality for a complex Avaya estate is 16 to 32 weeks from contract signature to full production cutover. Here is why, and where the time actually goes.
Phase 1: Discovery and Design (Weeks 1 to 4)
This phase is consistently underestimated. You need to document every Avaya flow, every queue, every IVR branch, every integration, and every exception. Most organisations discover they have 3 to 5 times more complexity than they thought.
Key outputs:
- Current state contact flow inventory
- Integration dependency map
- Number porting schedule
- AWS architecture design
- Compliance and data residency confirmation (Amazon Connect EU-WEST-2 for UK data residency)
Phase 2: Build and Configure (Weeks 3 to 10)
Amazon Connect flows are built in a visual editor but the production-grade version requires infrastructure as code. We build everything in AWS CDK so that environments are reproducible, auditable, and deployable without manual steps. This matters enormously for regulated industries.
Key activities:
- Contact flow development in Amazon Connect
- CRM and ticketing system integration
- Agent desktop configuration
- Amazon Connect Contact Lens configuration for call recording and analytics
- PCI DSS pause-and-resume for payment handling (critical for UK retail and financial services)
- Workforce management integration
Phase 3: Testing (Weeks 8 to 14)
This phase cannot be compressed. You need:
- Functional testing of every IVR path
- Integration testing with live CRM data
- Load testing at peak volumes
- Failover and resilience testing
- UAT with actual agents and supervisors
- Security and penetration testing if required by your compliance framework
For FCA-regulated contact centres, you also need to evidence that call recording, data retention, and access controls meet regulatory requirements before go-live.
Phase 4: Cutover and Stabilisation (Weeks 12 to 20)
Most migrations use a phased cutover approach rather than a big-bang switch. A typical pattern:
- Week 1: 10 to 20 percent of agents on Amazon Connect, remainder on Avaya
- Week 2 to 3: 50 percent on Amazon Connect
- Week 4: Full cutover, Avaya on standby
- Week 6 to 8: Avaya decommission
The stabilisation period is where you tune routing logic, adjust thresholds in Contact Lens, and resolve edge cases that did not appear in testing.
What Most Vendors Won't Tell You
1. Number porting is the critical path
Your go-live date is determined by when your numbers port, not when your platform is ready. Start the porting process in week one, not week eight. UK carriers require a Letter of Agency, and some legacy Avaya deployments have numbers spread across multiple carriers, which multiplies the complexity.
2. Avaya call recordings need a migration plan
You may have 3 to 7 years of call recordings on Avaya infrastructure that need to be retained for compliance. These do not automatically move to Amazon Connect S3 storage. You need a data migration and archival strategy before you decommission anything.
3. Amazon Connect does not replace your WFM platform
Amazon Connect has native scheduling features, but most enterprise contact centres need a dedicated workforce management platform. Amazon Connect integrates well with NICE, Verint, and Calabrio, but that integration needs to be scoped, built, and tested.
4. Your IVR redesign is an opportunity, not just a migration task
Most Avaya IVR trees were built incrementally over 10 to 15 years and are genuinely difficult for customers to navigate. Migration is the right moment to redesign them. Organisations that redesign their IVR during migration typically see a 10 to 20 percent reduction in average handle time and a measurable improvement in CSAT within 90 days of go-live.
Compliance Considerations for UK Regulated Industries
If you operate in financial services, insurance, healthcare, or utilities, your migration has a compliance dimension that cannot be treated as an afterthought.
FCA Consumer Duty: You need to evidence that your contact centre can capture, store, and retrieve customer interaction data to demonstrate fair outcomes. Amazon Connect Contact Lens with proper configuration gives you this capability, but it needs to be designed in from the start. PCI DSS: If agents take card payments over the phone, you need a pause-and-resume recording solution or a DTMF masking integration. Amazon Connect supports both approaches. The architecture decision affects your PCI scope and needs to be made in the design phase. GDPR and data residency: Amazon Connect in EU-WEST-2 (London) keeps call recordings and contact data in the UK. Confirm this explicitly in your AWS architecture documentation for your DPO. Call recording retention: FCA rules require certain call recordings to be retained for 5 to 7 years depending on the activity. Your S3 retention policies and lifecycle rules need to reflect this.Build vs. Buy vs. Configure: Choosing Your Implementation Partner
There are three types of organisations offering Amazon Connect implementations in the UK:
Large SIs (Accenture, Deloitte, Capgemini): They have Amazon Connect practices, but contact centre work is rarely their core focus. Expect long timelines, large teams, and governance overhead. Suitable for very large, complex estates above 1,000 seats. Resellers and managed service providers: Many AWS partners resell Amazon Connect with light-touch configuration. They are cost-effective for simple deployments but struggle with regulated environments, custom integrations, and agentic AI requirements. Specialist practitioners: Teams like ours at Rel8 CX who build exclusively on AWS, focus on contact centres, and have direct experience in regulated industries. We build production systems, not proof-of-concept demos. Our typical engagement goes from contract to production in 4 to 6 weeks for mid-market deployments, and 12 to 20 weeks for complex enterprise migrations.The question to ask any implementation partner: can you show me a production Amazon Connect deployment in a UK regulated environment that you built, not one you consulted on?
A Realistic Migration Budget: Three Scenarios
Scenario A: 50-seat contact centre, single site, simple IVR
- Implementation: £45,000 to £70,000
- Number porting: £500 to £1,000
- Training: £3,000 to £6,000
- Monthly AWS consumption: £3,000 to £6,000
- Timeline: 6 to 10 weeks
Scenario B: 200-seat contact centre, multi-site, CRM integration, regulated
- Implementation: £120,000 to £200,000
- Number porting: £1,000 to £3,000
- Training: £8,000 to £15,000
- Compliance work (PCI, FCA): £15,000 to £30,000
- Monthly AWS consumption: £12,000 to £22,000
- Timeline: 14 to 20 weeks
Scenario C: 500-seat contact centre, complex Avaya estate, multiple integrations, AI requirements
- Implementation: £250,000 to £450,000
- Number porting and carrier transition: £3,000 to £8,000
- Training and change management: £20,000 to £40,000
- Compliance and security: £25,000 to £60,000
- Monthly AWS consumption: £30,000 to £55,000
- Timeline: 20 to 32 weeks
The Questions to Ask Before You Start
Before you issue an RFP or sign a statement of work, get clear answers to these questions:
1. Who currently owns your Avaya numbers and what is the porting process with that carrier?
2. How many distinct IVR flows do you have, and when were they last documented?
3. Where are your call recordings stored and what are your retention obligations?
4. Which CRM, WFM, and ticketing systems need to integrate with the new platform?
5. What is your compliance framework and who in your organisation signs off on the technical architecture?
6. Do you have internal AWS expertise, or will you need ongoing managed support post-migration?
The answers to these questions will determine your timeline and budget more than any vendor proposal.
Summary
Migrating from Avaya to Amazon Connect is the right move for most UK contact centres. The economics are compelling, the platform is enterprise-grade, and the compliance capabilities are genuinely strong when configured correctly.
But the migration is not a simple lift-and-shift. The organisations that succeed treat it as a platform build, not a technology swap. They start number porting early, design compliance in from day one, and choose implementation partners who have built production systems in regulated environments.
The organisations that struggle treat it as a procurement exercise, underestimate the IVR complexity, and discover their compliance gaps six weeks before go-live.
We have done this in financial services, insurance, and utilities. We build on AWS, we work in regulated environments, and we get to production in 4 to 6 weeks for straightforward deployments.
If you are in the early stages of planning your Avaya migration, the most valuable thing you can do right now is get a clear picture of what your actual migration scope looks like.
Book a discovery callIs your pilot going to reach production?
Fifteen questions, three minutes, no cost. You get a score against the ten checks we run every deployment through, and a straight answer on what is blocking yours.
Find out what is blocking you