Moving Business Numbers to VoIP: Preserving Voice and SMS
Moving business numbers to VoIP allows organisations to modernise their telephone systems without necessarily changing the numbers their customers already use. However, preserving voice and SMS services requires more planning than simply transferring a telephone number to a new provider.
A business number may support incoming calls, outbound caller identification, SMS notifications and two-way messaging. While VoIP providers generally focus on voice connectivity, SMS routing is a separate technical consideration. A successful migration must account for both.
For UK businesses, communications providers and technology platforms, understanding how number porting, SIP interconnect and SMS routing work together can prevent service interruptions and preserve existing communication channels.
Planning a Move to VoIP?
Before moving your business numbers, make sure you've accounted for both voice and SMS. Download our free Voice & SMS Migration Planner to prepare, manage and test your migration.
Record your numbers, existing providers, SMS requirements and connected systems.
Track preparation, provider questions, responsibilities and migration progress.
Record inbound and outbound calls, caller ID, SMS and application tests.
Need Help with Your Migration?
Speak with Stour about your numbering, SIP connectivity and SMS requirements. Our team can discuss the available options before you migrate.
Call Stour: 020 80 400 000Contents
- What Happens When Moving Business Numbers to VoIP?
- Understanding UK Number Porting and VoIP Migration
- Preserving SMS Services When Moving to VoIP
- SIP Interconnect and the Technical Requirements for Voice
- How to Plan a Migration Without Losing Voice or SMS
- Choosing a Provider for Business VoIP and SMS
- Frequently Asked Questions
- Key Takeaways
- Discuss Your Voice and SMS Requirements with Stour
What Happens When Moving Business Numbers to VoIP?
Voice over Internet Protocol (VoIP) carries telephone calls over IP networks rather than relying on traditional analogue telephone connections. Businesses commonly adopt VoIP to support cloud telephone systems, remote working, centralised call management and integration with business software.
When moving business numbers to VoIP, an organisation will typically retain its existing telephone numbers through a process known as number porting.
Number porting allows an existing telephone number to move between communications providers without requiring customers to learn a new number.
For example, a business using a geographical number beginning with 01 or 02 may transfer that number from its existing provider to a VoIP service. Once the port completes, incoming calls are routed through the receiving provider's network.
However, a telephone number can support more than voice calls.
Some organisations also use their existing business numbers to receive text messages, communicate with customers or integrate messaging into their internal systems.
These services may not automatically transfer alongside the voice service.
Why Voice and SMS Need Separate Consideration
Voice and SMS use different network technologies.
VoIP calling commonly uses Session Initiation Protocol (SIP) to establish, manage and terminate telephone calls. The audio itself is generally transported using Real-time Transport Protocol (RTP).
SMS, meanwhile, relies on messaging infrastructure and signalling arrangements that differ from voice connectivity.
For organisations using SMS-enabled business numbers, moving the voice service does not necessarily preserve existing messaging capabilities.
This distinction matters because a successful voice migration can still leave a business unable to receive SMS messages on its established number.
The outcome depends on the number type, the existing service arrangements, the receiving provider and the available SMS routing infrastructure.
Understanding UK Number Porting and VoIP Migration
Number porting is a central part of moving business numbers to VoIP.
In the UK, Ofcom establishes rules governing number portability and the responsibilities of communications providers. These rules support customers' ability to retain eligible telephone numbers when changing providers.
The detailed arrangements vary depending on the type of number and the networks involved.
How Business Number Porting Works
A typical migration involves several stages.
1. Confirm the existing number and service arrangements
The receiving provider needs to establish which numbers are being transferred, who currently provides the service and whether any additional services depend on those numbers.
For businesses operating multiple sites, this may involve reviewing geographical numbers, non-geographical numbers and associated call routing arrangements.
2. Establish number portability
The receiving provider checks whether the numbers can be ported and identifies any technical or administrative requirements.
Geographical numbers, non-geographical numbers and mobile numbers can involve different porting arrangements.
3. Configure the receiving voice service
Before the number moves, the new provider prepares the required SIP connectivity, call routing and telephone system configuration.
This may include inbound routing, outbound calling permissions, failover arrangements and caller identification.
4. Coordinate the transfer
The existing and receiving providers arrange the port according to the applicable industry process.
The agreed migration date and any expected interruption should be communicated to the business in advance.
5. Test the migrated services
Following the transfer, the business should verify incoming and outgoing calls, caller identification and any additional services associated with the number.
Where SMS is required, it must be tested independently.
What Ofcom Says About Number Portability
Ofcom's General Conditions of Entitlement include requirements relating to switching and number portability.
These are intended to protect customers when changing communications providers, including the ability to retain eligible numbers.
However, number portability should not be confused with a guarantee that every additional service associated with a number will continue unchanged.
For example, transferring the voice service associated with a business landline number does not establish that the receiving provider can support SMS on that number.
Businesses should therefore confirm both number portability and service compatibility before proceeding.
For further information, see Ofcom's General Conditions of Entitlement.
Preserving SMS Services When Moving to VoIP
SMS continuity is one of the more easily overlooked aspects of a business telephone migration.
Although SMS is commonly associated with mobile phones, fixed-line telephone numbers can also support messaging where the appropriate network arrangements exist.
Businesses may use these capabilities for appointment reminders, customer enquiries, service notifications or automated communications.
A number that customers already recognise can be particularly valuable. Changing it may require updates to customer records, software integrations, printed materials and established communication processes.
Can a VoIP Number Receive SMS?
Yes, a VoIP number can receive SMS if the number and its provider's messaging arrangements support inbound SMS.
However, SMS support is not an inherent feature of VoIP.
A SIP trunk provides voice connectivity. It does not automatically provide SMS routing, message storage or access to an SMS application programming interface (API).
To receive SMS on an existing business number, the provider must have an appropriate mechanism for routing messages addressed to that number.
The business also needs a way to access those messages, whether through a messaging platform, application or API.
For this reason, organisations should not assume that a number described as VoIP compatible is also SMS compatible.
Why SMS Can Stop Working After Number Porting
Consider a business that uses a geographical telephone number for both customer calls and incoming text messages.
The company decides to migrate its telephone system to a cloud VoIP provider.
Its existing number is successfully ported, and incoming calls begin arriving through the new SIP connection.
However, the receiving provider does not support inbound SMS for that number.
Customers can still call the business, but text messages may no longer reach the intended destination.
The problem is not necessarily a failed number port. The voice migration may have completed correctly while the messaging service remained unsupported or incorrectly routed.
This is why SMS should be included in the migration specification rather than treated as an optional feature to investigate afterwards.
How SMS Routing Can Be Preserved
Depending on the number and provider arrangements, there may be options to maintain messaging functionality alongside VoIP.
These can include:
An SMS-capable receiving provider: A provider that supports the required voice and messaging services for the number.
Separate messaging infrastructure: An arrangement where SMS traffic is handled through a compatible messaging provider, subject to the necessary routing agreements.
SMS API integration: Connecting incoming and outgoing messages to an existing business application.
Dedicated messaging numbers: Where the original number cannot support the required arrangement, a separate SMS-enabled number may provide an alternative.
Not every option is available for every number.
In particular, organisations should establish whether the proposed provider supports SMS on their specific number range, rather than relying on a general statement that SMS is supported.
Stour provides wholesale SMS connectivity, including inbound SMS capabilities on supported fixed-line and mobile numbers. Its messaging infrastructure can form part of a wider communications solution where the required routing and commercial arrangements are in place.
SIP Interconnect and the Technical Requirements for Voice
SIP interconnect is an important component of many VoIP migrations, particularly for communications providers, CPaaS platforms and organisations operating their own telephone infrastructure.
SIP is a signalling protocol used to establish and manage communications sessions.
In a typical deployment, SIP connects a business telephone system or communications platform to a provider capable of routing calls to and from the public telephone network.
How SIP Interconnect Works
A simplified inbound call follows this process:
A customer calls the business's existing telephone number.
The telephone network routes the call towards the provider serving that number.
The receiving provider establishes the appropriate SIP session.
The call reaches the business's telephone platform.
The platform directs the call to the intended user, department or application.
The exact routing depends on the network configuration and interconnect arrangements.
For outbound calls, the process operates in the opposite direction. The business platform sends a call through its SIP connection to a provider that can terminate the call on the destination network.
Technical Considerations Before Migration
A reliable VoIP migration requires more than configuring a SIP endpoint.
Call routing
Incoming numbers must be mapped to the correct destination. This may involve individual extensions, hunt groups, contact centres or automated call handling systems.
Caller identification
The organisation should verify that its existing numbers can be presented correctly on outbound calls, subject to applicable provider policies and regulatory requirements.
Network capacity
Concurrent call requirements should be assessed against available SIP channels, network bandwidth and platform capacity.
Voice quality
Latency, packet loss and jitter can affect call quality. Network design, traffic prioritisation and suitable connectivity all contribute to performance.
Resilience
Businesses should consider how calls will be handled if a SIP connection, telephone platform or internet connection becomes unavailable.
Security
SIP services should be protected through appropriate authentication, access controls, traffic restrictions and monitoring. Encryption should also be assessed according to the supported infrastructure and security requirements.
For wholesale providers, these considerations extend beyond a single business telephone system. Interconnect capacity, network routing and operational support all influence service reliability.
Stour's wholesale voice services include SIP interconnect, inbound and outbound calling, and UK numbering capabilities for communications providers and technology platforms.
How to Plan a Migration Without Losing Voice or SMS
The safest approach to moving business numbers to VoIP is to treat the migration as a coordinated change to several connected services.
The telephone number is only one part of the arrangement.
A business may also depend on call routing, SMS connectivity, software integrations and customer-facing workflows that use the same number.
Step 1: Audit Existing Number Usage
Start by identifying every number that will be affected.
For each number, record its current provider, number type, intended destination and associated services.
This should include any systems that use the number for incoming or outgoing SMS.
For example, a number might support:
Customer service telephone calls
Appointment reminders
Incoming customer text messages
Automated notifications
Contact centre routing
Outbound caller identification
This audit can reveal dependencies that would otherwise become apparent only after the migration.
Step 2: Confirm SMS Compatibility Before Porting
If the number currently supports SMS, ask the receiving provider to confirm exactly what will happen to that service.
The assessment should establish whether inbound SMS, outbound SMS or both are required.
It should also identify how messages will be delivered to the business and whether the existing application integrations can continue operating.
For technically complex migrations, the receiving provider may need to coordinate with an SMS network operator or messaging infrastructure provider.
Do not rely solely on the fact that the number can be ported for voice.
Step 3: Prepare SIP Connectivity and Call Routing
The new voice service should be configured before the transfer wherever the provider's process permits.
This includes preparing SIP endpoints, routing policies, telephone system configuration and resilience arrangements.
Where possible, testing with temporary numbers can help identify configuration problems before the production number is moved.
However, successful testing with a temporary number does not guarantee that all routes associated with the ported number will behave identically.
Step 4: Agree a Migration and Testing Plan
The business and receiving provider should agree the transfer process, expected timing, responsibilities and escalation contacts.
For organisations with critical communications requirements, a documented migration plan should identify how service disruption will be handled.
This may include temporary call forwarding or alternative communication channels where technically available.
SMS testing should be explicitly included in the plan.
Step 5: Validate Both Services After the Transfer
Once the migration completes, test calls and messages from representative networks.
A useful validation process includes:
| Service | Recommended Test |
|---|---|
| Inbound Voice | Call the number from different UK networks |
| Outbound Voice | Verify calls to fixed and mobile destinations |
| Caller Identification | Confirm the correct number appears on outgoing calls |
| Inbound SMS | Send messages from supported originating networks |
| Outbound SMS | Verify delivery through the intended messaging platform |
| Application Integration | Confirm messages reach the correct software or API endpoint |
| Resilience | Test the agreed failure handling arrangements |
Testing should be recorded, particularly where the number supports business-critical communications.
Step 6: Monitor the Service After Migration
A successful initial test does not eliminate the need for monitoring.
Routing issues can sometimes affect particular originating networks or services rather than every call or message.
Businesses should monitor failed calls, message delivery outcomes and customer reports during the period following migration.
Where problems arise, having clear responsibility between the voice provider, messaging provider and network operator can make fault investigation more straightforward.
Choosing a Provider for Business VoIP and SMS
The right provider depends on the organisation's requirements.
A business moving a single telephone number to a hosted VoIP platform will have different needs from a CPaaS provider managing thousands of numbers across multiple networks.
However, the same principle applies to both.
Voice connectivity and SMS compatibility must be evaluated separately, even when both services use the same telephone number.
For businesses, the key questions concern service continuity, number portability, compatibility and support.
For communications providers, the assessment is more technical.
It may involve SIP interconnect, SMS routing, number allocation, network reach, regulatory responsibilities and the ability to integrate services into an existing platform.
The Value of Wholesale Network Infrastructure
Wholesale telecommunications providers supply the underlying connectivity used by business communications platforms, carriers and other service providers.
An independent mobile network operator can provide access to network services and numbering capabilities without requiring every customer-facing platform to establish its own operator infrastructure.
Stour is an independent UK Mobile Network Operator, established in 2006 and regulated by Ofcom.
Its wholesale services cover voice, SMS, numbering and other network connectivity requirements.
For organisations developing VoIP or unified communications services, access to both voice and messaging infrastructure can help address the technical requirements associated with preserving established business numbers.
The precise solution depends on number eligibility, routing arrangements and the capabilities required.
Frequently Asked Questions
Can I move my existing business telephone number to VoIP?
In many cases, yes. Existing UK business telephone numbers can be transferred to a VoIP provider through number porting, provided the number is eligible and the receiving provider supports the relevant porting arrangements.
Before starting, confirm which numbers are included, whether any linked services will be affected and what the receiving provider requires to complete the transfer.
Businesses should also review any contractual obligations associated with their existing service.
Will my business number still receive SMS after moving to VoIP?
Not automatically. A successful voice number port does not guarantee that SMS services will continue.
SMS depends on separate messaging infrastructure and routing arrangements. If the receiving VoIP provider does not support SMS on the number, incoming messages may stop working even though telephone calls operate normally.
Businesses that rely on SMS should confirm compatibility and agree a messaging solution before migrating their numbers.
Can the same business number support VoIP calls and SMS?
Yes, where the relevant providers and network arrangements support both services.
Voice calls may be handled through SIP connectivity, while SMS messages are routed through compatible messaging infrastructure.
The services do not necessarily have to use the same technical platform, but the routing arrangements must be correctly established.
Availability depends on the number type, network capabilities and commercial agreements between providers.
How long does it take to port a business number to VoIP?
Porting times vary according to the number type, provider arrangements and complexity of the migration.
A straightforward transfer may require less coordination than a migration involving multiple numbers, different network providers or complex routing arrangements.
The receiving provider should confirm the applicable process and expected timescale.
Businesses should avoid cancelling their existing service before receiving clear instructions, as premature cancellation can create problems with continuity or porting eligibility.
What is the difference between SIP trunking and SMS connectivity?
SIP trunking provides a connection between a telephone system or communications platform and a voice network.
It is primarily concerned with establishing and managing telephone calls.
SMS connectivity provides the infrastructure required to send and receive text messages.
Although both services may be associated with the same telephone number, they rely on different technical arrangements.
A provider offering SIP trunking does not necessarily provide SMS services on the same number.
Do I need to change my telephone number when moving to VoIP?
Not necessarily. Number portability allows eligible UK telephone numbers to be retained when changing providers.
However, eligibility and service compatibility should be checked before migration.
Where the existing number supports additional services, such as SMS, the organisation should verify whether those services can continue under the proposed arrangements.
Keeping the number for voice does not, by itself, confirm that all associated functionality will be preserved.
Key Takeaways
Moving business numbers to VoIP can provide greater flexibility and support the transition away from traditional telephone infrastructure.
However, preserving existing communications services requires careful coordination between numbering, voice and messaging providers.
The main considerations are straightforward:
Number portability preserves eligible telephone numbers, but does not automatically transfer every associated service.
SIP interconnect supports voice connectivity, while SMS requires separate messaging infrastructure.
SMS compatibility should be confirmed before porting, particularly where an existing number supports customer communications.
Testing should cover voice and messaging independently, including different originating networks and application integrations.
Wholesale network capabilities matter when building communications platforms that need to support both services.
A well-planned migration should preserve the communications services customers already depend on, rather than introducing unexpected changes alongside a new telephone platform.
Discuss Your Voice and SMS Requirements with Stour
Planning to migrate business numbers to VoIP while retaining existing voice and SMS functionality?
Stour provides wholesale voice, SMS and numbering services for communications providers, carriers and technology platforms.
Our team can discuss your existing numbering arrangements, SIP connectivity requirements and options for maintaining SMS services on supported numbers.
Contact Stour to discuss your technical requirements and establish the available options before migration.
