Cloud contact centre migrations are expensive. That's not news. What is surprising is how often the final bill lands 40-60% higher than initial estimates, and how many projects end up paused halfway through when the budget runs dry.
Q2 2026 is shaping up to be a busy migration season. Organisations are planning fiscal year budgets, and many are finally moving off legacy on-premise systems that are reaching end-of-life. Yet conversations with UK operations directors reveal a consistent pattern: most cost models for cloud contact centre migration are optimistic by design, and dangerously incomplete.
Here's what actually drives cost overruns, and how to model the real numbers.
The Obvious Costs (That Still Get Underestimated)
Let's start with the basics. Every cloud migration budget includes:
- Licensing fees — per-agent seats, usually annual or multi-year commitments
- Integration work — connecting to CRM, workforce management, quality monitoring
- Data migration — moving historical call records, customer data, agent schedules
- Training — getting agents and supervisors up to speed
Straightforward enough. Yet even these "known" line items routinely blow out. Why?
Licensing is never just licensing. Most cloud platforms have tiered pricing. Basic seats are cheap. But once you add real-time analytics, AI routing, omnichannel support, and compliance recording, you're paying 2-3x the headline price. And because no one wants to launch a contact centre with basic features, you end up on premium tiers from day one.
Integration is where budgets go to die. Every vendor claims their platform has "pre-built connectors" for major CRMs. What they don't say is that those connectors handle basic data sync — not the custom workflows, field mappings, and business logic your operation has relied on for years. Expect 200-400 hours of specialist development work. At £800-1,200 per day, that's £80k-£240k before you've made a single call.
The Hidden Costs No One Mentions
Here's where it gets expensive.
1. Dual Running Costs
You can't switch off your old system on Friday and turn on the new one on Monday. Every migration has a transition period where both systems run in parallel. That means paying for:
- Old system licences (can't cancel early without penalties)
- New system licences (already committed)
- Double the integration maintenance
- Extra telephony costs as you route calls between systems
For a 150-seat contact centre, dual running for three months can add £50k-£80k. For larger operations, it's worse.
2. Bandwidth and Network Upgrades
Legacy on-premise systems ran on your internal network. Cloud platforms stream voice, video, and screen-sharing over the internet. If your office has 100 Mbps symmetric fibre and 200 agents, you're in trouble.
Voice calls need about 100 kbps upload per concurrent call. Video and screen-sharing multiply that by 10-15x. Add AI-powered real-time transcription (which sends audio streams to cloud servers), and suddenly your network is the bottleneck.
Upgrading to 500 Mbps or 1 Gbps fibre, adding SD-WAN for failover, and ensuring QoS for voice traffic can cost £15k-£40k upfront, plus £2k-£5k per month ongoing. No one budgets for this because it's "IT infrastructure", not "contact centre costs". But if your calls drop out, it's your problem.
3. Telephony Number Porting and Compliance
Moving phone numbers between carriers is supposed to be straightforward. In practice, porting 50+ numbers across multiple UK regions takes 4-8 weeks and involves coordination between old carrier, new carrier, Ofcom records, and your cloud platform's telephony provider.
If you need compliance recording (PCI DSS, FCA regulations), the cloud provider's built-in recording might not meet your requirements. Third-party solutions like Verint or NICE add £30-£80 per agent per month. For 200 agents, that's £72k-£192k annually — rarely in the initial quote.
4. Training and Productivity Loss
Your agents are good at the old system. They'll be slow on the new one. Even with excellent training, expect a 20-30% productivity drop for the first 4-6 weeks. For a 150-seat centre handling 8,000 calls per day, that's 1,600-2,400 lost interactions daily.
If you measure cost per contact, that productivity loss has a real £ value. For high-value support (technical assistance, complaints), the impact on customer satisfaction can cost far more.
Capacity Planning: The Expensive Guessing Game
Cloud platforms promise elastic scaling. Pay for what you use. Add seats when you need them.
Reality: most platforms charge for provisioned capacity, not actual usage. If you license 200 agents but only use 150 at peak, you're paying for 200. If you hit 210 during a campaign, the platform won't let you add seats instantly — there's a provisioning delay, often 24-48 hours.
The safe approach is to over-provision by 15-20%. That's expensive. The risky approach is to provision exactly what you need and hope demand doesn't spike. That's more expensive when you lose calls.
Here's what actually works: model your peak demand properly. Don't use average agent count. Use 95th percentile concurrent agents, then add 10% headroom for campaigns, seasonal spikes, and unplanned absences. Factor in time zones if you run a global operation.
For a UK-based operation with 120 average agents, 95th percentile might be 160. Add 10% = 176 provisioned seats. Budget for that, not 120.
The AI Premium (And Why It Might Be Worth It)
Every cloud contact centre vendor now offers AI features:
- AI-powered routing
- Real-time agent assist
- Sentiment analysis
- AI voice agents for tier-1 queries
These are sold as cost-savers. "Reduce headcount by 20%!" "Handle tier-1 queries without human agents!"
The promise is real. The payback period is not what they claim.
AI features are premium add-ons. Expect to pay £40-£100 per agent per month for AI routing and real-time analytics. AI voice agents (autonomous bots handling calls) are typically priced per interaction or per minute — £0.05-£0.15 per minute is common. For a centre handling 200,000 minutes monthly, that's £10k-£30k.
AI requires tuning. Off-the-shelf AI voice agents sound robotic and frustrate customers. To make them useful, you need custom training, script development, and ongoing optimisation. Budget 100-200 hours of specialist work over the first six months.
That said, if your operation handles 50,000+ calls per month with high tier-1 repetition (password resets, order status, appointment booking), AI voice agents can genuinely reduce headcount. Just don't expect immediate ROI. Realistic payback is 12-18 months, not 6.
What a Realistic Budget Looks Like
Let's model a 150-seat UK contact centre migrating to a cloud platform. Mid-tier licensing (omnichannel, analytics, AI routing), standard integrations, compliance recording.
| Line Item | Annual Cost | |-----------|-------------| | Cloud platform licensing (150 seats, mid-tier) | £225,000 | | Compliance recording (third-party) | £90,000 | | Integration development (CRM, WFM, QM) | £120,000 (one-off) | | Data migration and testing | £40,000 (one-off) | | Telephony (SIP trunks, number porting) | £36,000 | | Network upgrades (bandwidth, SD-WAN) | £25,000 (one-off) + £30,000/year | | Training and productivity loss | £60,000 (one-off) | | Dual running costs (3 months) | £65,000 (one-off) | | AI voice agent deployment (20,000 mins/month) | £36,000 | | Contingency (15%) | £63,000 |
Year 1 total: £754,000
Ongoing annual: £417,000
Compare that to the initial vendor quote, which probably said £225k licensing + £50k integration = £275k.
The real number is 2.7x higher.
How to Build a Defensible Cost Model
Here's the approach that actually works:
1. Start with peak capacity, not average. Use 95th percentile concurrent agents, add 10-15% headroom. Budget for that.
2. Include the full platform cost. Don't quote basic tier pricing. Model mid-tier or premium, because that's what you'll actually deploy.
3. Map every integration. CRM, workforce management, quality monitoring, compliance recording, reporting tools, telephony. Each one is 50-100 hours of development work minimum. Budget accordingly.
4. Factor in dual running. Assume 2-3 months of parallel systems. Double your monthly costs for that period.
5. Model network impact. If you're moving 100+ agents to cloud voice, your network will need upgrading. Get a proper assessment from your ISP.
6. Include training and productivity loss. Assume 4-6 weeks of reduced productivity. Quantify the cost per lost interaction and add it to the budget.
7. Add 15% contingency. Not 5%. Not 10%. Fifteen. Because something will go wrong, and you'll need budget to fix it.
When Cloud Migration Makes Financial Sense
Despite all this, cloud contact centre migration often delivers genuine ROI. Here's when it works:
- Your on-premise system is end-of-life. If you're facing a £300k hardware refresh to stay on-premise, cloud migration becomes competitive.
- You need elastic scaling. Seasonal spikes (retail, travel) or campaign-driven demand make cloud economics attractive.
- You're expanding geographically. Opening a second site with on-premise infrastructure is expensive. Cloud scales across locations easily.
- You want modern AI features. Legacy systems don't offer AI voice agents, real-time sentiment analysis, or predictive routing. Cloud platforms do.
The key is honest cost modelling. If your business case assumes £275k and the real number is £750k, the ROI evaporates.
If you model £750k and the payback is still 18-24 months, you've got a solid case.
Final Thought
Cloud contact centre migration is not a technology decision. It's a financial and operational transformation that touches infrastructure, telephony, integration, training, and business process.
The vendors selling you cloud platforms have every incentive to make the numbers look good. Your job is to make them accurate.
Build a cost model that includes dual running, network upgrades, full licensing tiers, integration work, and productivity loss. Add 15% contingency. Then decide if the business case still holds.
If it does, you've got a migration plan that won't blow up halfway through.
If it doesn't, you've just saved your organisation from an expensive mistake.
Need help building a realistic cost model for your cloud contact centre migration? Hostcomm works with UK operations teams to map the real costs, identify hidden expenses, and build defensible business cases. Get in touch to discuss your migration plans.