
Number porting in South Africa: essentials for business VoIP
SA number porting process: inventories, authority, ICASA steps, PBX prep, testing, and cutover controls for VoIP and Cloud PBX migrations.
Quick answer
Last updated 2026-04-10
- SA number porting process: inventories, authority, ICASA steps, PBX prep, testing, and cutover controls for VoIP and Cloud PBX migrations.
- Your business phone numbers are more than lines on an account. They appear on your website, invoices, signage, email signatures, call tracking, Google Business Profile, customer records, supplier databases, and support processes. Changing them can create confusion and lost calls.
- Who owns each number and who is authorised to approve the port
Number porting in South Africa: why it matters for business
Your business phone numbers are more than lines on an account. They appear on your website, invoices, signage, email signatures, call tracking, Google Business Profile, customer records, supplier databases, and support processes. Changing them can create confusion and lost calls.
Number porting allows a business to move its existing numbers from one provider to another while keeping the numbers customers already know. For companies moving from legacy voice services to VoIP, SIP trunks, or a Cloud PBX, porting is often a key part of the migration plan.
In South Africa, number portability is managed through regulated industry processes, including ICASA-regulated number portability requirements. It is not simply a button in a self-service portal. A port involves the customer, the current provider, the new provider, and the relevant portability process for the number type.
Those checks exist to confirm authority, validate number ranges, and coordinate the move between the losing and gaining networks. They can apply to geographic numbers, non-geographic numbers, 087 numbers, and other business voice numbers, depending on how the service is currently provided.
Why porting is a project, not a tick-box
A small business with one or two numbers may have a straightforward port. A larger company with years of accumulated numbers, departments, branches, direct dials, old fax numbers, alarm lines, after-hours routing, and call queues should treat porting as a managed telecoms project.
The goal is not only to get the port approved. The goal is to make sure calls still reach the right people once the number moves.
A good porting plan covers:
This preparation is especially important when porting numbers into a new VoIP or Cloud PBX environment. A number can port successfully from a network perspective, but the business can still have a poor cutover if the PBX routing, IVR, voicemail, or call queue configuration is wrong.
- Who owns each number and who is authorised to approve the port
- Which provider currently bills for the numbers
- Which numbers are still active and which can be retired
- How each number is used today
- How each number must route after the port
- What must be tested before and after cutover
- Who will communicate with staff, customers, and suppliers if needed
Before you port: quick business checklist
Use this checklist as a practical starting point before you submit a port request or schedule a business VoIP migration in South Africa.
For more complex environments, include your IT team, branch managers, reception team, sales leaders, and support managers early. They often know which numbers customers actually use.
- Confirm the legal account holder for every number.
- Check the latest invoices from the current provider.
- Build a list of main numbers, branch numbers, direct dials, fax numbers, and system numbers.
- Identify whether each number is geographic, non-geographic, 087, or part of another service range.
- Confirm who is authorised to sign porting documents.
- Decide which numbers should be ported and which should be retired.
- Map each number to its destination in the new VoIP, SIP trunking, or Cloud PBX setup.
- Review internet connectivity, firewall rules, LAN, Wi-Fi, and failover requirements.
- Prepare IVR, call queue, voicemail, business-hours, and after-hours routing before cutover.
- Agree who will test calls on porting day.
- Keep the old service active until the port is complete and testing has passed.
What information you should confirm before starting
Before submitting a port request, build a clean number inventory. Do not rely only on memory or on the numbers that staff use every day. Check invoices, PBX records, call routing documents, old contracts, and any systems that still receive calls.
For each number, capture:
This is also the right time to remove clutter. If a number is no longer published, no longer receives useful calls, or belongs to an old campaign, decide whether it should be ported or cancelled separately. Do not port unnecessary numbers by default.
- The full telephone number
- The current service provider or carrier
- The account holder name
- The billing account or reference where available
- The department, branch, team, or person using the number
- The current function, such as reception, sales, support, fax, alarm, intercom, gate, or direct dial
- The required destination after porting
- Any special routing, such as business hours, after-hours, overflow, voicemail, or IVR options
Check authority and ownership early
Many porting delays start with incorrect authority. The person requesting the port must be able to act on behalf of the business, and the details submitted usually need to match the current provider’s records.
Before you begin, confirm:
If your business has changed names, merged entities, moved premises, or consolidated telecoms accounts over time, resolve those mismatches before the port window. Waiting until cutover week can create avoidable delays.
- The legal name of the business on the current account
- The correct account number or service reference
- The authorised signatory or delegated approver
- Whether company documents, resolutions, or proof of authority are required
- Whether any numbers are billed under a different entity, branch, landlord, franchise, or former trading name
Typical number porting risks to plan for
Number porting is a normal telecoms process, but it can become disruptive when businesses underestimate the dependencies. The most common risks are practical rather than technical.
Watch for:
- Incomplete number lists: A missing main number, direct inward dial, or branch number can interrupt customer contact.
- Wrong account details: If the current provider cannot match the request, the port may be rejected or delayed.
- Unclear sign-off: If nobody has authority to approve documents or respond to porting queries, the process stalls.
- Legacy services: Fax, alarm systems, lift phones, card machines, gate intercoms, and old analogue services may not behave like normal voice numbers.
- Poor PBX preparation: Calls may land at the new provider but route to the wrong team, prompt, queue, or voicemail.
- Weak connectivity: VoIP quality depends on reliable business connectivity, suitable network configuration, and sufficient capacity for concurrent calls.
- No communication plan: Staff may not know what to test, what to report, or who to contact during the cutover.
A sensible internal checklist
Treat the port as a controlled business change. Assign one internal owner who can coordinate information, approvals, and testing across departments.
Use this checklist before submitting the port request:
The more complex your environment, the more valuable this checklist becomes. Multi-branch businesses, call centres, sales teams, medical practices, professional services firms, and support desks should be especially careful because calls are often tied directly to revenue or service delivery.
- List each number, owner, location, and business function.
- Confirm the current provider, account holder, and account reference.
- Identify main numbers, published numbers, direct dials, and numbers used by systems.
- Check whether any services are still tied to old analogue lines or legacy ranges.
- Confirm who is authorised to sign porting documentation and approve communications.
- Agree how calls should route in the new VoIP, SIP trunk, or Cloud PBX setup.
- Prepare IVR menus, call queues, ring groups, voicemail, and after-hours rules before cutover.
- Review whether your business fibre or connectivity is suitable for voice traffic.
- Decide who will test inbound and outbound calls once the port completes.
- Create a clear escalation path for issues on the day.
- Communicate internally so staff know what is changing and who to contact.
What to prepare on the VoIP or Cloud PBX side
Porting the number is only one part of the move. The receiving voice platform must be ready to handle calls correctly.
Before cutover, check that your new provider has configured:
Connectivity also matters. A VoIP or Cloud PBX service depends on stable internet access, suitable network configuration, and enough capacity for concurrent calls. If your fibre, LTE failover, firewall, LAN, or Wi-Fi is unreliable, porting your number will not fix the underlying voice quality risk.
If you are moving voice services at the same time, plan the number port alongside your Cloud PBX migration, SIP trunking, and connectivity readiness work. Voice quality, call routing, business continuity, and user training should be treated as part of the same migration.
- SIP trunks or hosted voice services for the required numbers
- Direct inward dial numbers mapped to the correct users or teams
- Main number routing to reception, IVR, call queues, or hunt groups
- Business-hours and after-hours rules
- Voicemail and email notification settings where required
- Outbound caller ID presentation
- Emergency and compliance-related presentation where relevant to your environment
- Failover options if connectivity is unavailable
- Test users, handsets, softphones, or apps
How long does number porting take in South Africa?
Porting timelines can vary depending on the number type, the current provider, the accuracy of documentation, the approval process, and whether the port involves a simple number or a more complex business range. Geographic numbers, non-geographic numbers, and 087 numbers may involve different checks and dependencies.
Businesses should avoid planning around a last-minute port, especially when a lease move, provider cancellation, office relocation, or system go-live depends on it. Even where the port itself is routine, delays can happen if account details do not match, authority is unclear, or the receiving voice platform is not ready.
Start early. Give your team enough time to gather documents, validate numbers, configure the new voice platform, test devices, and resolve queries from the current provider. For planning purposes, ask your gaining provider for the current expected lead time for your specific number type and account scenario.
A sensible approach is to plan the desired cutover date, then work backwards from it with your provider. If the business cannot tolerate disruption during trading hours, discuss the available cutover options and testing plan in advance rather than assuming the timing can be changed at the last moment.
What happens on porting day?
On the cutover day, the number is moved from the current provider’s routing to the new provider’s routing. From the customer’s perspective, the ideal result is uneventful: they dial the same number and reach the same business.
Your internal team should be ready to test:
Keep testing structured. Do not rely on one successful mobile call to confirm the whole environment. Test the numbers and call flows that matter to the business.
- Inbound calls from mobile networks
- Inbound calls from fixed-line networks where practical
- Calls to main numbers and direct dials
- IVR menu options
- Call queues and overflow rules
- Voicemail
- After-hours routing if relevant
- Outbound calls and caller ID presentation
- Any critical numbers used by sales, support, reception, or branch teams
How to reduce disruption during a port
You cannot remove every dependency from a porting process, but you can reduce risk by planning well.
Use these practical controls:
The businesses that experience the smoothest ports are usually not the ones with the simplest phone systems. They are the ones that prepared their data, responsibilities, and testing properly.
- Do not cancel services with the losing provider before the port is complete unless your provider has advised you to do so.
- Keep current services active until the port and post-port testing are confirmed.
- Avoid making unrelated PBX or network changes during the cutover window.
- Have key staff available to test and approve call flows.
- Prepare a temporary call-forwarding or fallback plan where appropriate.
- Keep a written list of issues, numbers affected, times tested, and test results.
- Communicate a single escalation contact to staff.
How InspireTel helps with number porting and voice migration
A strong VoIP partner does more than submit forms. The value is in coordinating the voice migration so that the port, PBX configuration, SIP trunking, connectivity, and user readiness line up.
InspireTel can help South African businesses assess what needs to be ported, prepare the receiving voice environment, and plan the cutover as part of a wider business VoIP, Cloud PBX, or SIP trunking migration.
Your provider should help you:
A smooth number port should feel boring on the day. That usually happens because the detailed work happened before the cutover.
- Understand what information is required for the port request
- Identify obvious gaps in your number inventory
- Prepare the receiving VoIP or Cloud PBX environment
- Configure routing for main numbers, departments, and direct dials
- Review connectivity and voice quality risks before migration
- Plan testing before and after cutover
- Explain realistic timelines and dependencies
- Coordinate technical troubleshooting if something does not route as expected
Questions to ask before choosing a porting partner
When comparing VoIP or Cloud PBX providers, ask practical questions about how they manage number porting and cutovers.
Useful questions include:
The answers should be specific. Avoid any provider that treats number porting as an afterthought while focusing only on handsets or monthly call costs.
- What information do you need from us before submitting a port request?
- Who checks that our PBX routing is ready before cutover?
- How do you handle main numbers, direct dials, IVRs, and call queues?
- What testing do you recommend on the day?
- What happens if the current provider rejects the port request?
- How will we know when the port has completed?
- Who do we contact during the cutover window?
- Can you help review our connectivity and voice quality risks before migration?
FAQ: number porting in South Africa
Final advice for South African business buyers
Number porting is one of the most important parts of moving voice providers because it protects the numbers your customers already use. It is also a good opportunity to clean up your telecoms environment, remove unused numbers, improve call routing, and move to a voice platform that better supports how your teams work.
Start with accurate information, confirm authority early, prepare your VoIP or Cloud PBX configuration, and test properly on the day. With the right planning, your business can move providers without making customers change the way they contact you.
If you are planning to move providers, migrate to VoIP, set up Cloud PBX, deploy SIP trunks, or review business voice continuity, speak to InspireTel before you submit the port request. A short porting assessment can help identify ownership gaps, routing risks, and connectivity issues before they affect customers.
Contact InspireTel to discuss number porting support, VoIP migration, Cloud PBX setup, SIP trunking, or business connectivity for your South African organisation.