When I talk to my customers about cloud voice transformations, the conversation often focuses on features, architecture, or migration tooling. But the real story – the story that determines whether an organization succeeds or falters – is about execution at scale. It’s about whether thousands of employees can arrive at work the next day and continue business as usual, completely unaware that anything changed.

That’s why one recent global migration stands out for me, that I’d like to tell you about.

Late last year, a large enterprise transitioned nearly 60,000 users to Microsoft Teams Phone in under 7 months, spanning APAC, EMEA, LATAM, and North America – with zero business disruption. Even in an industry where complexity is expected, this project presented complexity at scale. The outcome wasn’t just about operational excellence; the project delivered more than $2M USD in cost savings, proving that transformation done right can accelerate value, not just reduce risk.

The more I reflect on the project, it’s clear that the real lesson here isn’t just in the numbers. It’s how they were achieved.

On paper, moving from one voice platform to another sounds like a purely technical task. In reality, global migrations require:

• Coordinating distributed environments with regional regulatory requirements
• Aligning multiple stakeholders – including service providers, partners, and customer teams
• Executing all cutovers outside business hours to ensure uninterrupted operations
• Maintaining design consistency across multiple continents, languages, and working practices
• Managing intricate voice routing, gateways, and overlapping legacy infrastructure

Large organizations rarely have a single “migration team.” They typically have many teams – network, voice, operations, project management, security, regional IT – each with different priorities and constraints. Success depends on unifying them.

This project succeeded not because it was simple, but because every element of delivery was engineered to eliminate risk.  This is the VOSS operating model:

For further details, read the case study.
If you would like to discuss your next migration project, please get in touch.

In today’s cloud-first world, Microsoft licensing has become increasingly complex. Enterprises are no longer just buying base license subscriptions such as an E1 or E5; they are navigating a growing array of add-ons, Copilot features, and consumption-based services. With more than $8 billion spent on Microsoft licensing every month, organizations can’t afford to treat license management as purely an administrative exercise.

Yet many companies still rely on the information in the M365 Admin Center – that provides only high-level information on overall license capacity by SKU and consumption. The result? Over-purchasing, mismatched license types, underutilized services, and a lack of agility to respond to changing business needs.

The real opportunity lies not just in controlling costs, but in using license intelligence to drive agility. When you understand how your licenses are used, you can pivot quickly – scaling services, enabling new regions, merging teams, or rolling out new capabilities with confidence.

Moving beyond simple license counts, enterprises are now looking at license performance: how each license contributes to user experience, productivity, and overall business outcomes. This shift requires a new level of visibility and governance, including:

• Allocation controls – Track license positions with granular visibility and alerts to prevent resource starvation.
• Department-level granularity – Manage local requirements while maintaining enterprise-wide oversight.
• Automation – Streamline onboarding and offboarding with standard license templates.
• Analytics – Track adoption, usage, and value across departments to maximize ROI.
• Monitoring and optimization – Identify duplicate, unused, or incorrectly assigned licenses, rationalize applications, and improve productivity.
• Smarter purchasing – Forecast, budget, and plan license requirements at an individual, departmental, or organizational level.

VOSS provides a centralized platform for proactive license governance and planning. Its tooling gives you real-time insights across Microsoft environments, helping IT teams:

Reallocate licenses quickly during organizational changes

Identify underutilized licenses and optimize usage

Rationalize applications and reduce unnecessary costs

Forecast and plan license needs with confidence

With VOSS, you gain the visibility and control needed to turn license management from a complicated task into a strategic enabler. This approach allows you to be agile, responsive, and ready to scale services as business priorities shift.

To harness the full value of Microsoft licensing, I recommend you start with an audit and review of your current position, then invest in tooling and processes that make license management sustainable over the long term. By moving from reactive administration to proactive governance, you can unlock both cost savings and operational agility. Please get in touch to discuss your license concerns.

Microsoft Teams boasts over 320 million active users, yet only 20 million use telephony. Contrast that with the fact that many organizations are still operating on premise telephony (PBX) systems, with a desire to migrate these systems to the cloud, and you can see why there is a pent-up demand for a fast, accurate, and efficient way to facilitate this transition.

One common question we are often asked is how to approach this migration in a way that:

• Maintains the user experience
• Addresses their detailed needs
• Avoids transferring unwanted configurations, and
• Ensures minimal disruption while remaining cost-effective

The answer is bulk automation.

When migrating large groups – for example site-based or regional batches of 5,000 to 15,000 users – a common approach is PowerShell scripting. This method uses a “.TXT/.CSV” input file or similar, containing a list of users and migration details alongside a set of PowerShell commands, all initiated on a local Windows server. While effective in some cases, this comes with significant drawbacks:

• Requires highly skilled Microsoft specialists to execute
• Creates security risks due to elevated permissions on the Microsoft tenant
• Is error prone, due to the number of manual steps involved
• Provides limited logging for audits and diagnostics, and
• Offers minimal feedback during the migration process, making it difficult to monitor progress.

Alternatively, organizations invest in automation, such as bespoke tools or self-built tools around Microsoft Power Automate. This takes time and requires both specialist skills and ongoing support. Importantly, with this method, each user is handled as a single thread, perhaps taking a much as two minutes per user migration. Suddenly a 5,000-user batch migration becomes a 7-day (or more!) marathon … and that’s assuming non-stop processing each day with no errors or dropouts along the way.

Bulk automation provides the answer for migrating large batches of users efficiently and seamlessly. Here’s how the process works, and some key considerations when choosing an automated migration tool:

1. Automated data extraction: Information is extracted from the existing PBX for review
2. Configuration optimization: Usage data is applied to identify and remove unnecessary configurations
3. Batch selection: Users are filtered and selected as part of the migration batch
4. Configuration mapping: Data is mapped from the legacy system (e.g., Cisco) to Microsoft Teams Phone, with non-mappable features flagged for review
5. Controlled loading: The full batch is transferred to Microsoft Teams as an entity, then split into smaller chunks (e.g., 100 users per chunk) for finer control, loading and immediate feedback on the process
6. Respectful migration: Each chunk is processed systematically, including licensing, telephone numbers, voice configurations, and policies. Backoff algorithms prevent tenant overload, while token credentials are refreshed automatically, and retries are initiated during network congestion or failures
7. Comprehensive logging: Every step is logged into an audit trail, ensuring a complete record and identifying errors for correction and replay

At VOSS, we leverage VOSS Migrate to fully automate the steps outlined above, delivering fast, accurate, and efficient migrations without burdening your IT team. What’s more, VOSS Migrate includes an intuitive portal that makes this whole process straightforward and even, dare I say it, enjoyable.

The result? Each user migration typically takes seconds – a significant improvement over the two-minute-per-user timeframe highlighted earlier, and with no errors.

If you’d like to learn more about VOSS, VOSS Migrate, or how to run large-scale migrations to Microsoft Teams Phone, please contact us.

Each VOSS Discover project is delivered by a team of VOSS engineers with a track record in PBX systems and complex migration projects. They’re supported by VOSS Migrate automation tooling that streamlines the entire audit process.

The process itself is non-intrusive and secure, with the analysis conducted on an offline export of the PBX – no need to connect to the live PBX. This reduces the call on your technical and IT resources, freeing these up for higher priority projects and tasks. First results are available in a matter of weeks, to assist with early planning, budgeting, and resourcing.

What to Expect

Each VOSS discovery project provides 5 things:

• A Migration Readiness Report based on data extracted and covering PBX configuration, inventory, and migration ‘gap’ traffic-light analysis
• A Line Usage Report indicating numbers in use or those that can be trimmed to reduce clutter and costs as part of migration planning
• Best practice and advice on approaching migration planning based on experience from recent projects
• A two-hour workshop to review findings
• Support for ad-hoc queries resulting from the review and/or specific business questions

I’ve included two sample reports for your reference: