Cloud Migration – Success Factors for the Transformation
13. Nov 2025 | 3 min.
13. Nov 2025 | 3 min.
I have been supporting customer projects in the field of collaboration for over ten years – mostly with Cisco and Microsoft technologies. During this time, one thing has become pretty clear: cloud migration is not purely a technical issue, but rather a combination of strategy, architecture and change.
Our customers often start with a classic on-premises telephone system – developed over many years, with their own servers, maintenance contracts and a variety of additional solutions. In most cases, the switch to the cloud is not a spontaneous decision, but the result of careful consideration.
An important driver for cloud migration is the reduction of the data centre landscape. Many companies want to streamline their infrastructure, reduce maintenance costs and decrease their dependence on physical hardware. At the same time, many are following a single-client strategy to centrally provide and manage communication tools. Licensing models and costs also play a major role.
When I talk to customers about the right platform, it’s rarely just about features. The decision on which manufacturer to go with is often already made by management. Sometimes it’s based on conviction, sometimes on experience. My job as a consultant is to question this decision. Does it really fit the requirements, processes, and existing infrastructure?
The market has changed, particularly due to the removal of Microsoft Teams from Enterprise Agreements. On the other hand, there are companies that have invested heavily in Cisco and want to continue to benefit from this investment protection. Last but not least, data protection remains a crucial factor, which is assessed differently by both manufacturers.
From a technical perspective, both providers have their strengths. Microsoft has caught up significantly in recent years and offers very close integration with the Office world. Cisco, on the other hand, impresses with an open ecosystem, stable hardware integration and a well-thought-out licensing model that already covers many features. Cisco has also made great progress in data protection in recent years – with BSI certifications and European data storage.
Ultimately, it all comes down to the strategy pursued by the company and the actual requirements for collaboration and communication.
A migration project almost always begins with a detailed inventory. Which systems are in use? Which phone numbers, end devices and special functions are there? And which third-party systems are still connected to the old system? Especially in complex environments, this analysis phase can take more time than the actual technical implementation.
The next step is to set up the new environment – usually initially in parallel with the existing system to enable testing and gradual migration. A key element here is the session border controller, which serves as an interface between the local infrastructure and the cloud. Depending on the architecture, telephony can then be connected via local gateways, certified providers or directly via the manufacturer. The last option is functionally possible, but in practice it is often the most expensive option.
However, the actual success of a migration rarely depends on the technology. Switching to softphones, eliminating fax servers or integrating contact centre solutions – all of these things affect daily work processes. If key users are not involved at an early stage, even a technically correct project can encounter acceptance problems. Open change management and transparent communication are therefore just as important as a proper architecture.
After working on many projects, one thing is clear to me: not everything that is technically possible should be adopted. Migration always presents an opportunity to let go of legacy issues and consolidate systems. Instead of continuing to use every special solution, it is worth rethinking and simplifying processes.
It is equally important to clarify regulatory and data protection issues at an early stage, especially in international projects. Different emergency call regulations or number porting can quickly become stumbling blocks if they are only considered once the project is already running.
Cloud migration in the area of collaboration is much more than a technical upgrade. It is a transformation process that affects strategy, organisation and people alike. Whether Cisco or Microsoft – the key factor is that the solution fits the company and not the other way around.