WhichVoIP: Compare Telecom Providers in South Africa
GET QUOTES
Call centre • Cloud migration

Migrating your contact centre to the cloud without breaking a shift

Moving a live contact centre is not a software install, it is a cutover. Done in phases it is low-risk and barely noticed; done as a big-bang switch it drops calls. Here is the practical, phased way to do it.

Last verified 05 July 2026
By the WhichVoIP editorial team
8 min read
3 phasesassess, parallel run, cutover
Phasedbeats a big-bang switch
Keepyour existing numbers
POPIAgoverns the call data you move

The short answer

How do you migrate a contact centre to the cloud?

Map your current setup first, then move in phases rather than all at once. Confirm your integrations and port your numbers, run the new cloud platform in parallel with the old one for a slice of traffic, prove it, then cut over fully and decommission. A phased approach is what keeps calls from dropping.

A Modern South African Contact Centre Floor With Agents At Workstations Wearing Headsets
The goal of a good migration is that the floor does not notice it happened. Phasing is how you get there.

What actually moves when you go cloud

A contact centre is not one system, it is a stack. Knowing which parts move, change or stay is what turns a vague project into a plan.

The telephony and call-distribution layer moves entirely: your ACD, queues and IVR are rebuilt in the cloud platform rather than run on hardware on-site. Your numbers stay, because South African number portability lets you carry geographic and non-geographic numbers to a new provider. The integrations are where the real work sits: your CRM or ticketing system, workforce management, and reporting all need to be reconnected to the new platform, not just switched on.

Two things change shape rather than simply moving. Call recording moves to cloud storage, which raises retention and access questions you must answer for POPIA. And reporting usually improves, but the metrics are defined differently, so historical comparisons need care.

✓
Bottom line: the telephony rebuild is the easy part. The integrations and the call-data handling are what make or break the timeline, so scope those first.

The three things that decide whether it goes smoothly

Almost every migration that goes wrong fails on one of these three, and almost always because it was discovered late rather than planned for.

Do this first

Readiness

  • Current-state mapEvery queue, IVR path, integration
  • Number portingList and lead times
  • Data to migrateContacts, recordings, history

Security & compliance

  • POPIARecordings, retention, consent
  • Access controlRole-based, audited
  • Data locationWhere recordings sit

Integration

  • CRM / ticketingScreen pop, logging
  • WFMRostering, adherence
  • ReportingMetric definitions

The three phases of a low-risk migration

1 · Assess Map, scope, plan 2 · Parallel run Prove on a slice of traffic 3 · Cut over Switch fully, decommission

A migration that does not drop calls

Follow the sequence in order. The discipline is in resisting the urge to skip the parallel run because the demo looked fine.

Map the current stateDocument every queue, IVR path, integration and report you use today. You cannot rebuild what you have not written down, and this list is also your test plan.
Confirm the target and its integrationsChoose the platform against your buying criteria, then prove it connects to your CRM, WFM and reporting before you commit, not after.
Plan the number porting and cutover windowList the numbers to port and their lead times, and pick a low-volume window for the switch. Porting is the step with the least room to improvise.
Run in parallel on a slice of trafficRoute one team, one queue or one number through the new platform while the rest stays put. Fix what breaks here, where it is cheap.
Train, cut over, then decommissionTrain agents on the real system, move the rest of the traffic, and only switch off the old platform once the new one has carried a full peak cleanly.
Approach Phased parallel run Big-bang cutover
Risk to live calls Low, contained to a slice High, all-or-nothing
Where faults surface In test traffic, cheaply In production, under load
Rollback Easy, reroute the slice Hard, everything has moved
Speed to finish Slower overall Faster if nothing goes wrong

A contact centre migration is judged on one thing: did the customers notice?

WhichVoIP editorial view

POPIA and your call data during the move

A migration touches every recording and customer record you hold, which puts it squarely inside POPIA. Treat the data move as a compliance step, not an IT afterthought.

Recorded calls are personal information. When they move to a new platform you need to know where they will be stored, who can access them, and how long they are kept, and you need those answers documented before the data moves rather than after. Migrate only what you have a lawful basis to keep, apply role-based access on the new system from day one, and keep an audit trail of the transfer itself.

!
Watch for: silently copying years of recordings to a new cloud store “just in case”. Retention limits still apply, and a bigger unmanaged archive is a bigger POPIA liability, not a safety net.

A Contact Centre Team Leader Reviewing A Migration Plan On A Laptop With Dashboards Behind
The parallel-run phase is where a migration is actually de-risked. Skipping it is the most common way one goes wrong.

Our verdict

Moving a contact centre to the cloud is well-trodden and low-risk when it is run as a phased cutover, and genuinely risky when it is run as a big-bang switch. The platform choice matters less than the migration discipline: map first, prove integrations, port carefully, run in parallel, and only then decommission.

Our recommendation: scope readiness, security and integration before you sign anything, insist on a parallel-run phase in the plan, and handle the call-data move as a POPIA task in its own right.

Planning a move to a cloud contact centre?

Compare cloud contact centre and hosted-PBX options from independent South African providers, and get the migration scoped before you commit.

Compare cloud contact centre quotes
Read the buying guide first

Frequently asked questions

How do you migrate a contact centre to the cloud?
Map your current setup, confirm your integrations and number porting, then move in phases. Run the new cloud platform in parallel with the old one for a slice of traffic, prove it under load, then cut over fully and decommission the old system. Phasing is what stops calls dropping.
Can I keep my existing numbers when I move to the cloud?
Yes. South African number portability lets you carry geographic and non-geographic numbers to a new provider. List every number and its porting lead time early, because porting is the step with the least room to improvise on the day.
Should I do a big-bang cutover or a phased migration?
Phased, for anything live. A phased parallel run contains risk to a slice of traffic, surfaces faults cheaply in test, and rolls back easily. A big-bang cutover is faster only if nothing goes wrong, and everything has already moved when it does.
What are the main risks in a cloud contact centre migration?
The three that catch teams out are readiness (an incomplete current-state map), integration (CRM, WFM and reporting not reconnected in time), and compliance (recorded-call data moved without a POPIA plan). All three are manageable when scoped up front and discovered late when not.
How does POPIA affect migrating call recordings?
Recorded calls are personal information, so before they move you must know where they will be stored, who can access them and how long they are kept. Migrate only what you have a lawful basis to keep, apply role-based access from day one, and keep an audit trail of the transfer.
How long does a contact centre migration take?
It depends on the number of integrations and numbers rather than the platform itself. The parallel-run phase adds time but removes most of the risk, so treat a longer, phased timeline as the cheaper option overall compared with a fast cutover that fails under load.

Keep reading

How to buy the right call centre solution
Setting up a contact centre from scratch
Reduce contact centre operational costs
Inbound vs outbound contact centres

Sources: POPIA and the Information Regulator (recorded-call handling, retention, access); ICASA number portability regime; WhichVoIP editorial. Verified 05 July 2026.

Now hiring Hire your AI receptionist