What Migration Actually Feels Like for a Partner

The case for platform migration can be made at a market level, and we have made it. But market-level arguments do not manage customer relationships, handle renewal conversations, or carry responsibility for the quality of a customer's experience on go-live day. Partners do.

This post is about what the migration process looks like from the position of the partner, the commercial dynamics, the operational process, and the ongoing relationship with the platform on the other side of the cutover.

The Commercial Conversation Comes First

For most partners, the migration journey begins at a commercial inflection point: a customer's contract is approaching renewal, the customer is beginning to ask questions about what else is available, or a consolidation opportunity has emerged from an acquisition or estate review.

This is the moment that determines whether the migration is a proactive commercial play or a reactive scramble. Partners who are ahead of that conversation, who have already mapped their customer base against renewal timelines and identified migration candidates, are in a fundamentally different position to those who are responding to a customer who has already started evaluating alternatives.

"The partners who are growing their base through migration are the ones who have shifted how they think about renewal. They are not waiting for the contract date. They are managing a pipeline of migration conversations in the same way they manage a new business pipeline, with cadence, qualification, and a clear commercial proposition. Migration is not a service cost. It is a revenue event."

— Sam Giggle, MD of Channel, Nebula

Nebula's channel team, led by Sam Giggle, works directly with partners through this commercial phase, helping to identify which customers represent the strongest migration candidates, how to frame the proposition, and what the commercial model looks like for the partner on the other side of the move.

The Migration Process: What Partners Experience

Once the commercial conversation is concluded and a migration timeline is agreed, the operational process is structured to place as little burden as possible on the partner and their customers.

The pre-migration assessment establishes a detailed picture of the customer's existing configuration, identifying complexity, flagging non-standard elements, and agreeing go-live criteria. This phase is conducted by Nebula's migration team working in close coordination with the partner, not delegated to the partner to complete independently.

Automated configuration transfer handles the bulk of the technical migration work. For the majority of customers, this means the cutover itself is a contained, planned event rather than an extended period of parallel running and manual reconciliation.

Post-migration, a structured review confirms that the customer's environment is performing as expected and resolves any minor configuration issues before they become customer-facing problems.

The CX Relationship: Ongoing, Not Transactional

Jez Pickering's CX team, the largest team at Nebula, is the primary point of contact for partners once migration is complete. But the relationship is designed to be substantively different from a conventional support function.

"Every query that comes into the CX team is a data point. We are not just resolving individual issues, we are identifying where the platform needs to develop, where the documentation needs to improve, and where the migration process itself can be refined. That analysis feeds directly into the weekly reviews with the product team. The consequence is that partner feedback has a short path from observation to action, and that is only possible because we own the platform."

— Jez Pickering, Head of CX, Nebula

For partners evaluating platforms, this is a meaningful operational distinction. The experience of being a reseller on a third-party platform, where feedback travels through layers of organisational distance before reaching a product team that may not be oriented toward the UK channel, is qualitatively different from working with a provider who can close the loop between partner experience and platform development in a matter of weeks.

What Sits on the Other Side

Partners who have completed migration to CallSwitch One consistently report three commercial improvements: the platform is easier to sell, easier to manage at scale, and generates fewer reactive support interactions.

Easier to sell because the proposition is genuinely differentiated, owned IP, UK-built, actively developed, with a migration track record that no competitor in the market can match. Easier to manage because the administration tooling is designed for MSP workflows, not adapted from an enterprise direct model. And fewer reactive support interactions because the platform's cloud-native architecture and continuous development reduce the surface area for issues that, on legacy platforms, are endemic.

These are not soft benefits. They translate directly into partner profitability and customer retention, the two metrics that determine the long-term value of a reseller's book of business.

Final post next week: Where the platform goes from here, and why owning your technology stack is not a one-time advantage but a continuously compounding one.