Migrating from Aspect Dialler to Amazon Connect: What UK Contact Centres Need to Know Before 2026 End of Life

Arkadas Kilic 8 min read · 2026-08-14

The clock is running. Aspect's end-of-life timeline for its legacy dialler platform is pushing UK contact centres into a decision they can no longer defer. If your operation is still running on Aspect for outbound dialling, blended campaigns, or workforce management integrations, you need a migration plan in place well before 2026 support expiry. Waiting until the last quarter means competing for vendor resources, compressing your testing window, and carrying compliance risk on unsupported infrastructure.

This guide covers what UK contact centres actually need to know: the technical realities, the compliance obligations, the timeline, and the concrete steps to get from Aspect to Amazon Connect without disrupting live operations.

Why 2026 Is Not as Far Away as It Looks

Enterprise contact centre migrations take longer than most teams expect. A realistic migration from legacy Aspect to a fully configured, compliance-ready Amazon Connect environment runs 16 to 24 weeks when you factor in:

• Discovery and current-state documentation
• Data mapping and CRM integration work
• Outbound campaign configuration and testing
• Agent and supervisor training
• Parallel running and cutover
• Post-go-live stabilisation

If you start procurement conversations in Q3 2025, you are already in a compressed window. Organisations that start now have the runway to do this properly.

What You Are Actually Replacing

Aspect dialler deployments in UK contact centres typically cover several functions that need direct equivalents in Amazon Connect:

The capability parity is strong. The migration complexity is not in the features; it is in the data, the integrations, and the compliance configuration.

UK Compliance Requirements You Cannot Skip

UK outbound dialling is governed by Ofcom's persistent misuse rules, ICO guidance under UK GDPR, and FCA requirements if you operate in financial services. These obligations do not pause during a migration. They apply on day one of your new platform.

The Migration Path: Phase by Phase

Phase 1: Discovery and Architecture (Weeks 1 to 2)

Document every Aspect workflow in production. This means campaign types, list sources, suppression logic, CRM triggers, screen pop configurations, and reporting outputs. Most organisations discover undocumented workflows during this phase. Every one of them needs a decision: replicate, replace, or retire.

Output from this phase: a signed-off architecture diagram for your Amazon Connect environment, a data migration plan, and a compliance configuration checklist.

Phase 2: AWS Environment Build (Weeks 3 to 6)

This is where the Amazon Connect instance is built, not configured from a console but deployed as infrastructure as code using AWS CDK. Every resource, including Connect instances, contact flows, Lambda functions, S3 buckets, IAM roles, and CloudWatch alarms, is version-controlled and repeatable.

Key build tasks:

• Amazon Connect instance with UK telephony numbers ported or provisioned
• Outbound campaign configuration with Ofcom-compliant dial rates
• TPS/CTPS suppression Lambda with your chosen data provider
• CRM integration (Salesforce, Dynamics, or bespoke) via Lambda or Amazon Connect Wisdom
• Call recording to S3 with correct lifecycle and encryption policies
• Real-time and historical reporting dashboards

Phase 3: Integration and Data Migration (Weeks 5 to 10)

Campaign list migration is the highest-risk phase. Aspect stores list data in proprietary formats. You need ETL pipelines to extract, transform, and load this data into Amazon Connect campaign list structures via S3. Consent metadata must be preserved and mapped correctly.

CRM integrations need end-to-end testing under realistic load. A screen pop that works in UAT but fails under 200 concurrent outbound calls is a production incident waiting to happen.

Phase 4: Parallel Running and Cutover (Weeks 10 to 16)

Run both platforms simultaneously for a defined period, typically 4 to 6 weeks. Start with a low-risk campaign segment on Amazon Connect while Aspect handles primary volume. Validate abandonment rates, compliance scrubbing accuracy, CRM data quality, and recording completeness before expanding.

Cutover should be a non-event. If your parallel running phase has been rigorous, the final switch is a routing change, not a crisis.

Phase 5: Decommission and Optimisation (Weeks 16 to 24)

Once Amazon Connect is carrying full production load and metrics are stable, begin Aspect decommissioning. Retain Aspect in a read-only state for historical reporting access until your Amazon Connect historical data covers your minimum retention window.

Number Porting: The Detail That Derails Timelines

UK number porting to Amazon Connect via BT Wholesale or other carriers takes 4 to 8 weeks for standard geographic numbers and up to 12 weeks for non-geographic numbers (0800, 0345, 03xx ranges). If your outbound CLI numbers are business-critical, start the porting process in parallel with your build phase, not after it.

Amazon Connect supports UK DDI ranges and non-geographic numbers. Confirm your specific number types with AWS before committing to a go-live date.

What Amazon Connect Does Better Than Aspect

This is not a like-for-like replacement. Amazon Connect gives you capabilities that Aspect's legacy architecture cannot match:

Common Migration Mistakes to Avoid

What to Budget

Amazon Connect pricing for UK outbound contact centres typically breaks down as follows:

• Amazon Connect usage: approximately 0.018 USD per minute for outbound calls (subject to AWS pricing updates)
• Contact Lens: approximately 0.015 USD per minute for real-time analysis
• Amazon Connect Campaigns: approximately 0.0025 USD per dial attempt
• Lambda invocations: typically negligible at contact centre scale
• S3 storage for recordings: approximately 0.023 USD per GB per month in eu-west-2 (London)

For a 100-seat outbound contact centre running 8 hours per day, 5 days per week, total AWS infrastructure costs typically land between 15,000 and 35,000 GBP per year depending on call volume and Contact Lens usage. This compares to Aspect licence costs that frequently exceed 200,000 GBP annually for comparable seat counts.

Migration and build costs depend on complexity. A straightforward migration with a single CRM integration and standard outbound campaigns runs 4 to 6 weeks of build time. Complex environments with multiple integrations, bespoke reporting, and phased cutover plans take longer.

Why AWS Native Matters for UK Regulated Industries

Amazon Connect in the eu-west-2 (London) region keeps call data, recordings, and contact metadata within UK borders. For FCA-regulated firms, NHS-contracted organisations, and public sector contact centres, data residency is not negotiable. Building on AWS native services means your compliance posture is grounded in infrastructure that already holds ISO 27001, SOC 2, Cyber Essentials Plus, and NHS DSPT alignment.

We build every Amazon Connect deployment with compliance as a structural property, not a configuration layer added at the end.

Your Next Steps

If you are running Aspect today, here is the minimum you should have in place before the end of Q1 2025:

1. A current-state audit of every Aspect workflow in production

2. A confirmed list of all outbound numbers and their porting timelines

3. A CRM integration specification document

4. A compliance requirements register covering Ofcom, ICO, and any sector-specific obligations

5. A migration partner with Amazon Connect production deployments in regulated UK environments

The organisations that reach 2026 without incident are the ones that started this process 18 months before the deadline, not 6.

We build Amazon Connect environments for UK contact centres in regulated industries. From architecture through to production in 4 to 6 weeks for standard deployments, with compliance built into every layer.