Cloud & TelephonyPublished on · 17 min read· Author: WSV Redaktion· Reviewed on

Cloud Phone Systems for Businesses: Features, Costs, Migration

What a cloud phone system really costs a small business, where its drawbacks lie, and how to switch without gaps in availability – with a worked cost example, selection criteria and a step-by-step plan from a service provider that sets these systems up and supports them.

Cover image: Cloud phone systems for businesses – features, costs, migration

A cloud phone system for small businesses always sounds the same in the brochure: cheap per month, flexible, reachable anywhere. What the price lists rarely show are the items next to it – devices, setup, contract term, the internet line – and the situations where a cloud solution is genuinely worse than the old box in the basement. That is what this guide is about: honest total costs and honest drawbacks, from the perspective of an IT service provider that doesn't just sell phone systems but sets them up and supports them day to day.

Anyone who needs to be reachable at the office, at home and on the road quickly notices how rigid traditional phone systems have become. A cloud phone system isn't a fashionable answer to that, but a practical one – as long as it fits the way your company actually works.

The short answer: is a cloud phone system worth it for a small business?

For most small and mid-sized businesses: yes – on three conditions. Your internet connection has to be stable with enough headroom, there needs to be a plan for when that line goes down, and your availability rules (who answers when, where calls are forwarded) must be settled before you switch. If those boxes are ticked, you gain location independence, a system that grows with your team, and predictable monthly costs instead of a large hardware investment.

Our cloud phone system starts at €5.90 net per extension per month. Depending on your needs, devices and a one-time basic setup come on top – we work through a complete example below. If you'd like to know straight away what that means for your business, you can book a free initial consultation. We'll also check whether a cloud solution is the right choice for you in the first place.

What is a cloud phone system?

A cloud phone system is a PBX that no longer sits as hardware in your server room but runs as software in a provider's data center. Your desk phones, smartphones and PCs connect to it over the internet. You manage extensions, call groups, queues and announcements centrally, no matter where your staff happen to be working.

VoIP or cloud phone system: what's the difference?

The two terms are often used interchangeably, but they describe different things. VoIP (Voice over IP) is only the transmission technology: speech is turned into data packets and sent over the internet protocol rather than classic phone lines. A cloud phone system builds on that technology and additionally moves the central PBX functions – extensions, call groups, queues, administration – into a data center.

That distinction shapes the decision. VoIP also works with an on-premises system that stays in your own server room and still places calls over IP. That can make sense for companies with very specific interfaces to line-of-business software, heavily customized call-center functions, or modern infrastructure run by their own admin team.

So the question isn't "VoIP or not" – there's no way around VoIP anymore. What matters is whether the PBX function itself runs on site or in the cloud. That depends less on enthusiasm for technology than on your operational requirements.

Why this matters for small businesses right now

Three developments are converging for smaller companies. First, ISDN has been switched off in Germany; anyone still running an old PBX through adapters often has a stopgap that nobody fully understands any more. What that means for fax, alarm systems or door intercoms is covered in our guide Cloud telephony or ISDN replacement.

Second, teams are more distributed. Part-time work, home offices, field staff and multiple sites are normal even in a ten-person business. A system that ties availability to a single desk no longer fits.

Third, many installed systems are ageing. When spare parts are hard to find, extensions get expensive or administration depends on one single technician, that's a clear signal to look at alternatives – before the system fails on a Monday morning.

Features: what a cloud phone system changes day to day

In daily business, buzzwords don't count – noticeable relief does. We see the main effects in the same places again and again.

Reachable on the familiar number. Every employee calls with their own landline extension – from a PC or laptop with a headset, from a smartphone or from a desk phone. Calls no longer go unanswered just because someone is working from home at short notice.

Call groups, forwarding and announcements. Extensions, call forwarding, voicemail and announcements are configured to your specifications. Customer inquiries reach the right person faster, and outside business hours callers hear a suitable message instead of endless ringing.

Growth without rebuilding. When a new colleague joins, you add an extension – no new hardware in the server room, no new cabling. That's more economical than a system that is already too small, or needlessly oversized, today.

Optional AI call handling. On request, our cloud phone system can be equipped with the AI phone assistant Nia FrontDesk. It answers calls around the clock, handles standard questions such as opening hours or address, and forwards callers based on availability. To be honest: it doesn't replace a full receptionist for complex matters. It does take routine calls off your team's plate, especially outside business hours.

Types of phone systems: which option fits?

Before comparing price plans, step back for a moment. It's not just "cloud or old", but several options with their own strengths.

Cloud phone system (hosted). The system runs in a data center and you rent extensions monthly. Strengths: no PBX hardware of your own, location-independent, easy to expand. Weakness: no internet, no calls through the system. This is the right option for most small businesses – our cloud phone system belongs in this category.

On-premises IP PBX. The system sits on site but places calls over IP. This makes sense when many analog or DECT devices need to keep working, special interfaces are required, or the company is considerably larger. One example is the Mitel MiVoice Office 400, which can also run as a virtual appliance on your own server infrastructure.

Telephony in Microsoft Teams. If your company already works entirely in Teams, telephony can be integrated there. Whether that's sensible depends heavily on licensing and working style; we plan such setups as part of our phone systems & cloud telephony service.

Add-ons instead of a new system. Sometimes the problem isn't the PBX but the workplace around it. A CTI solution like estos ProCall links telephony with the PC, presence status and caller identification from your CRM or Outlook, and connects to cloud and on-premises systems alike. Professional greetings and hold messages are available as phone announcements recorded by real voice artists or – if they change often – as AI announcement scripts.

What does a cloud phone system cost? A realistic calculation

"From €5.90 a month" is true – but it's only part of the bill. The figures below come from our product page (as of 16 August 2026); all prices are net plus statutory VAT.

Item Monthly One-time
User Basic €5.90 €0.00
User Professional €9.90 €39.00
Desk phone €6.50 €169.00
Cordless phone €5.00 €149.00
Wireless headset €5.00 €159.00
DECT base station €8.00 €329.00
Basic system setup – €699.00

Key for your budget: the minimum contract term for all packages is 36 months. Amounts are collected monthly in advance by SEPA direct debit. Travel costs may be added.

Worked example with assumed figures

Assumed example: an office with ten employees. Eight use a Basic extension, two use Professional. Six desks get a desk phone, two employees get a wireless headset; the rest call via smartphone or a softphone on their laptop.

  • Monthly: 8 × €5.90 + 2 × €9.90 + 6 × €6.50 + 2 × €5.00 = €116.00
  • One-time: 2 × €39.00 + 6 × €169.00 + 2 × €159.00 + €699.00 = €2,109.00
  • Over the 36-month minimum term: 36 × €116.00 + €2,109.00 = €6,285.00 net, plus any travel costs and VAT

That works out at roughly €52 per workstation per year for the system and devices – but only if you calculate over the full term and include the one-time costs. That's exactly what pure monthly-price comparisons leave out.

What no monthly fee includes

An honest total also needs a few items that don't appear on the phone system's price list:

  • The internet connection. It's the lifeline of cloud telephony. If the line isn't good enough or there's no backup, a better connection or a second line adds cost. Our network provider consulting helps you choose.
  • The internal network. Old switches, an overloaded Wi-Fi or a firewall that doesn't pass voice traffic cleanly cost call quality. Sometimes this needs fixing before telephony moves.
  • Call and number charges. Check in the offer how calls to landlines and mobile networks and additional numbers are billed. According to the Bundesnetzagentur, porting your number itself may no longer be charged for since December 2021.
  • Options. Availability and pricing of the Nia FrontDesk AI assistant depend on the license package – we check this case by case. Professionally recorded announcements are a separate product.
  • Internal effort. Someone on your team has to define availability rules, accompany test calls and brief colleagues. Those hours are real, even if they never show up on an invoice.

Drawbacks of a cloud phone system – and how to handle them

Every provider lists advantages. Here are the drawbacks we actually see in practice, and what you can do about them.

No internet, no phone system

This is the most common objection, and it's justified. If the line fails, the desk phone in the office can't call through the cloud system. The system itself keeps running, though – and you can use that: forwarding to smartphones reachable via mobile network, an emergency announcement, or automatic failover to a second line. Staff with a softphone or app keep calling from home anyway. How to prepare such scenarios for your whole IT is covered in our guide to the IT emergency plan.

Call quality depends on the network

For audio calls, the platform vendor NFON specifies around 100 kbit/s per simultaneous call, plus latency below 100 ms and packet loss well below 1%. Bandwidth is rarely the issue: six simultaneous calls need roughly 600 kbit/s in each direction. More critical are unstable connections and networks where voice competes with backups and video meetings for the same line. The fix is prioritization (Quality of Service), for example a dedicated VLAN for telephony, and measuring under load before the switch. The basics are in our guide planning office network solutions.

Lock-in through contract term and platform

Our packages run for at least 36 months. That keeps costs predictable, but it also means you're committing. At the same time, you depend on the platform operator – its features, its data center and its pricing. Mitigate this by defining requirements carefully up front, having numbers and configuration documented, and asking how data can be exported. A later switch is then work, but plannable work.

Emergency calls from home and on the road

With a classic line, a caller's location is fixed. When someone uses the office extension on a softphone at home, things get more complicated. The Bundesnetzagentur sets the technical requirements for emergency connections in its Technical Guideline on Emergency Calls (TR Notruf). What matters for you in practice: clarify before switching which location data is transmitted with emergency calls, and tell employees to place emergency calls from their mobile phone if in doubt.

Special cases don't always fit

Fax machines, alarm systems, lift emergency phones, door intercoms or franking machines are often still attached to the old system. Not all of them can move to the cloud one to one. These devices belong in the inventory phase, not in the week after cutover.

Number porting isn't a button press

Existing numbers can usually be ported. But we can't guarantee a completely uninterrupted switch across the board, because the losing provider is involved. According to the Bundesnetzagentur, service may be interrupted on the day of the switch, and the number must be activated no later than the following working day. So schedule the cutover outside peak times and set up forwarding for the transition.

Who it suits – and who it doesn't

A cloud phone system is especially worthwhile for companies that work flexibly and don't want to tie communication to one location. That applies to trade businesses with an office and field staff just as much as to law firms, medical practices, agencies or retailers with several teams.

A pure cloud solution is less suitable if a site permanently lacks a stable connection, if many analog special devices must keep working, or if highly specialized software requires a local interface. In those cases you need a careful review rather than a quick decision – which is exactly where vendor-neutral advice pays off.

Selection criteria instead of a provider ranking

"Which is the best cloud phone system?" has no general answer. The best system is the one that reflects your workflows and has someone looking after it when things go wrong. Check offers against these criteria:

  1. Total cost over the term: add up monthly price, one-time costs, devices, setup and minimum term – don't just compare the entry price.
  2. Setup included or self-service: who configures extensions, call groups and announcements? Is there a fine-tuning round after the first weeks? With us, a one-time configuration adjustment after 30 days is included.
  3. Number porting: who handles it and coordinates the date with your current provider?
  4. Devices and working style: desk phone, DECT, headset, softphone or app – and on how many devices per person? Our package installs the phone solution on up to two devices per employee.
  5. Network check before signing: does the provider check your line, firewall and internal network – or do you only find out after the switch that something's off?
  6. Failover plan: which forwarding rules, announcements and backup lines are planned?
  7. Data protection: where is data processed, is there a data processing agreement, and who can access configuration and voicemail?
  8. Contact person in operation: who do you call when telephony isn't working – a hotline or someone who knows your environment?

Security and data protection

As soon as communication runs over external platforms, security rightly gets a closer look. In its IT-Grundschutz module NET.4.2 VoIP, Germany's Federal Office for Information Security (BSI) points out that unencrypted VoIP calls can in principle be intercepted and that misconfiguration can take down the entire phone system. Its recommendation: all VoIP data packets leaving the secured company network should be protected by suitable mechanisms.

In concrete terms, that means encrypted connections, secured user access, a clear permission model for administration, and a firewall that specifically allows telephony instead of opening every port. An often overlooked point is voicemail sent as an audio file by email – it contains confidential information too.

From a data protection perspective, the system provider processes connection data and possibly voicemail on your behalf. Under Art. 28 GDPR, you need a data processing agreement with a provider that offers sufficient guarantees for technical and organizational measures. Ask for that agreement before you start. If staff make calls from home, secure the devices there as well – see our guide setting up a secure home office.

Switching step by step

Moving to new telephony doesn't have to be complicated if it's planned properly. What matters is that the technical changeover and day-to-day operations mesh. In practice, a six-step process works well:

  1. Inventory: record all numbers, extensions, devices, contracts, special lines and existing forwarding rules. Plan fax machines, alarm systems or door intercoms on the old system separately.
  2. Availability concept: define opening hours, queues, cover arrangements, announcements and responsibilities.
  3. Assess the network: check internet connection, firewall, switches and Wi-Fi for quality and resilience.
  4. Choose solution and devices: decide on desk phones, softphones or smartphone apps based on how each team works.
  5. Port numbers and configure: request number porting in good time – the Bundesnetzagentur recommends starting a provider switch about three months before your contract ends – and fully configure the system before cutover.
  6. Test and train: run through test calls, forwarding and emergency procedures before the old telephony is switched off.

Testing the system before switching and avoiding outages

A quick test call over office Wi-Fi says little about how the system behaves when video meetings are running, backups are syncing or several colleagues are on the phone at once. A solid test covers several layers:

  • Bandwidth under load: how does call quality hold up while typical business applications run in parallel – not just on an idle network?
  • Quality of Service: are voice packets prioritized so a large download doesn't cause dropouts mid-call?
  • Redundancy: does a second connection or mobile backup kick in automatically if the line fails?
  • Different times and sites: tests in the morning, at midday and in the afternoon show whether peak loads affect calls.
  • Failure and emergency behavior: are calls rerouted automatically during an interruption, and does the emergency-call setup still work then?

Checking these points before the switch rather than after avoids the typical teething problems: choppy calls, delayed pickup, or telephony that drops out during network peaks. A test period with clear acceptance criteria belongs in every project, not just the critical ones.

Best practices from day-to-day operations

From looking after more than 1,500 endpoints and more than 300 servers, we know where telephony tends to snag. These habits have proven themselves:

  • One person is responsible. Even when the platform runs externally, someone internal needs to bundle changes and maintain availability rules.
  • Emergency forwarding is ready. Forwarding to mobiles or the emergency announcement is configured in advance, not built during an outage.
  • Announcements are current. A summer holiday message still playing in November looks sloppier than any hold music.
  • Fine-tune after 30 days. The first weeks reveal which call group is too large and which forwarding rule nobody needs. Feed that back into the configuration.
  • Leavers are removed properly. Extension, app access and forwarding belong on every offboarding checklist.

Common mistakes when deciding

Many problems aren't caused by the cloud phone system itself but by false expectations.

Comparing only the monthly price. Looking only at the base fee per extension ignores setup, devices, term and support quality. Cheap to start doesn't mean cheap to run.

Copying old structures one to one. If cover arrangements were unclear or call groups badly organized, those weaknesses simply move with you. The switch is a good chance to organize availability more cleanly.

Checking the network after the switch. If data traffic and telephony get in each other's way, even the best platform won't help. Network analysis belongs before signing.

No plan for a line outage. "Our internet never goes down" holds until the first excavator cuts a cable.

No ownership in operation. Without a fixed contact person, a flexible solution quickly becomes a collection of individual wishes with no clear direction.

Service provider instead of a self-service plan: what difference it makes

Many platforms can be booked online and set up yourself. That can work for very small teams with technical know-how. But once number porting, network, firewall, devices and availability rules all have to fit together, the work simply shifts to you.

With us, setting up your existing numbers and extensions, installing the solution on your employees' devices, configuring forwarding, voicemail and announcements, and an adjustment after 30 days are all part of the cloud phone system. And because our team of 20 also looks after networks, security and cloud solutions, we don't just look at telephony but at the environment it has to run in.

One Google review (February 2020) describes how customers experience our advice – quoted here in the original German:

„Sehr kompetente und freundliche Beratung. Hier wird nichts auf Biegen und Brechen verkauft, sondern auf die Wünsche und Bedürfnisse auch kleiner Unternehmen wert gelegt.“

In short: competent, friendly advice that focuses on what small businesses actually need rather than pushing a sale. You can find more feedback in our Google reviews.

FAQ on cloud phone systems

What does a cloud phone system cost for a small business?

With us, it starts at €5.90 net per extension per month. A realistic calculation adds devices, the one-time basic setup of €699.00 and the 36-month minimum term. In the example above, ten workstations come to around €6,285 net over the full term.

What are the drawbacks of a cloud phone system?

It depends on a stable internet connection, call quality depends on the network, and you commit to a contract term and platform. Special cases like fax or alarm systems and emergency calls from mobile workplaces add to that. Forwarding rules, a backup line, network prioritization and a thorough inventory take care of most of these drawbacks.

How much bandwidth does a cloud phone system need?

A guide value is about 100 kbit/s per simultaneous call in each direction. Stable latency, low packet loss and enough headroom for other traffic matter at least as much. We check these requirements before the switch.

Can we keep our phone numbers?

Usually yes. Existing numbers are ported, and familiar extensions are set up according to the technical options. There may be a short interruption on the day of the switch, so we plan the date and a temporary forwarding rule together with you.

Which is the best cloud phone system?

There is no universal ranking. What counts is total cost over the term, included setup, the failover plan, data protection and a reachable contact person. The selection criteria above help you make offers comparable.

Conclusion: a good solution when the surroundings are right

For most small businesses, a cloud phone system is the up-to-date choice: location-independent, expandable and with predictable costs. Calculated honestly, though, the €5.90 per extension comes with devices, setup, a 36-month term and an internet line that can carry it all. If you know the drawbacks and deal with them up front – failover plan, network check, thorough inventory – you get telephony that simply works day to day.

Want to know what the numbers look like for your business and whether your line and network are ready? Book a free initial consultation

Sources

Updated on

WhatsAppRequest adviceGet support

Get in touch

Privacy settings

We use cookies and other technologies on our website. Some of them are essential, while others help us improve this website and your experience. Personal data may be processed (e.g. IP addresses), for example for personalized ads and content or ad and content measurement.

There is no obligation to consent to the processing of your data in order to use this offer. You can withdraw or adjust your selection at any time under settings. Please note that due to individual settings, not all functions of the website may be available.

We use technically necessary storage for operating this website. Optional services (statistics, marketing, external media) are only loaded after your consent.

Privacy settings