The first conversation about moving calling to the cloud usually happens before anyone has counted anything. Six things decide what the project looks like and what it costs. All six can be gathered inside your own organization, and gathering them first is what makes the quotes you get afterward comparable to each other.
What to count before you ask anyone for a quote
Every item below changes the price. Two of them change the design. None of them needs a vendor in the room.
- Sites. How many buildings, and which of them have to keep dial tone when the circuit into the building fails. A site with that requirement needs hardware designed in on site, and it is cheaper to say so at the start.
- Users, split by type. A headcount does not answer this. Count how many people need a desk phone, how many need only a software client, how many need both, and how many extensions belong to a room instead of a person. Licensing is priced against that split.
- Analog devices. Elevator phones, fire and burglar alarm dialers, fax machines, gate and door intercoms, overhead paging. They appear in no user count, most of them are owned by facilities rather than IT, and none of them migrates. This is the item that moves budgets, and it has an article of its own.
- Call flows. Every published number and whatever answers it: auto attendants, hunt groups, after-hours routing, the number printed on the back of a badge. Each one needs a named owner who can confirm it is still correct.
- Carrier contract end dates. Per account, not per company. An organization that has acquired anything usually holds numbers across more accounts than anyone remembers, and the term commitment on each account decides whether those numbers can move on your schedule.
- What you are running today. The call control platform, the version it is on, and the support dates attached to it. That last date is usually the reason somebody asked for this in the first place.
Anyone who prices this work before those six answers exist is estimating from assumptions, and that includes us. We will give you a budgetary number if the funding cycle demands one, and it will move once discovery is done. The item that moves it is almost always the analog list.
Once the count exists, the next question is what order the work happens in, which is set out in the migration sequence. If you are moving off on-premises call control specifically, what that project actually involves covers the tooling, the endpoint rules and the licensing decisions in detail.