Phone Number Porting Australia: Guide 2026
- stfsweb
- 11 minutes ago
- 14 min read
You've probably already found a phone system that looks better than what you're using now. Lower call costs. Better call handling. Staff can answer from the office, home, or on the road. The part that stops most small businesses is the same every time: “We can't risk losing our main number.”
That fear is understandable. Your number is on your website, your invoices, your vans, your email signatures, and in your customers' phones. Changing systems feels manageable. Changing the number does not.
The good news is that phone number porting in Australia is a normal, regulated process. If the paperwork is right and the cutover is planned properly, you can move your service without giving up the number your business has built around. That matters even more if you're moving to a Hosted PBX, because hosted telecommunications can save time and money and give staff flexible working locations while keeping your incoming calls tied to the number people already know. If mobile retention is part of your plan, it also helps to understand how mobile number portability works in practice.
Keeping Your Number Is Simpler Than You Think
A common scenario looks like this. A business owner is stuck on an old phone setup with patchy forwarding, limited visibility on missed calls, and no clean way for staff to work outside the office. They find a Hosted PBX that fixes those problems, then stall the project because they assume the current telco “owns” the number.
In Australia, that assumption is usually wrong. The practical reality is that your business can generally move providers and keep its number, provided the service is still active and the request is valid. That's exactly why number portability exists.
Why businesses hesitate
The hesitation usually has nothing to do with technology. It comes from business risk.
Customer risk: You don't want customers hearing a dead line or old voicemail.
Operational risk: You don't want reception, sales, or support cut off mid-week.
Admin risk: You don't want a port rejected because a form has the wrong legal name or address.
Those concerns are real. But they're manageable when the port is treated as an admin and coordination job, not a leap of faith.
Keep the existing service active until the new provider confirms completion. Most serious porting problems start when a business cancels too early.
Why a Hosted PBX changes the equation
A modern hosted setup doesn't just replace handsets. It changes how calls flow through the business. Staff can answer from Yealink desk phones, softphones, or mobile devices. Calls can route by time of day, team, or location. Remote staff can work under the same business number instead of using personal mobiles.
That's why many businesses revisit porting only when they can see a clear operational gain. Once the fear of losing the number is removed, the move becomes much easier to justify.
Understanding the Porting Essentials
Porting usually goes wrong before any call routing changes happen. The trouble starts in the paperwork. A business owner submits a request under the trading name, the carrier holds the service under the company name, and the port stalls. Or the verification code goes to a mobile that nobody is watching, and the request expires.
That is why the key terms matter. You do not need telco jargon for its own sake. You need to know which details carriers check, which party does what, and where small admin mistakes cause delays.
The framework behind number portability
Australia's Local Number Portability, or LNP, framework was formally established in 1999 when Comms Alliance defined the ACIF C540 standard, classifying geographic landline numbers as a portable service so customers could change providers and retain their number, according to this overview of Australia's number portability framework.
The practical point is simple. If the request is valid, your current provider is expected to release the number. They can reject a request with incorrect details. They cannot reject it just because you are leaving.
The terms you actually need to know
A few labels show up on almost every port request.
Losing provider: your current telco, the provider the number is leaving
Gaining provider: your new telco or hosted phone provider, the provider submitting the port
Customer Authorisation: the form that gives the gaining provider permission to act for you
Porting category: the classification that affects how much checking and coordination the port needs
The biggest mistake I see is business owners treating porting as a technical job only. It is really an admin and carrier records job first. If the legal entity, service address, or account reference does not line up with what the losing provider has on file, the request often gets rejected without much explanation.
Which numbers you can port
For a small business, the common answer is yes, but the number type affects the process.
Geographic numbers: 02, 03, 07, 08
National numbers: 13, 1300, 1800
Mobile numbers: Australian mobiles can usually be ported as well, including services that still need SMS for verification or customer replies
Hosted Telecommunications can port and host these number types. What changes is the level of checking involved and the documents the gaining provider may ask for. A local landline and a 1300 number do not always follow the same path behind the scenes.
Practical rule: treat the number and the phone system as separate items. You are changing who delivers the service behind the number.
What a valid request usually needs
Most approved ports come down to five checks:
The service is still active
The business or account name matches the carrier record exactly
The registered service address matches the carrier record exactly
The account number or customer reference is correct
The authorisation is current and properly signed
Exact means exact. “Suite 4” versus “Level 1, Suite 4” can be enough to stop a request. The same goes for old ABNs, outdated contact names, or mobiles assigned to ex-staff.
Mobile ports add another trap. The verification SMS often goes to the service being ported. If that handset is in a drawer, with a former employee, or set to forward messages elsewhere, approval can be missed and the request can fail for a reason that looks mysterious until someone checks who receives the code.
Your Step-by-Step Porting Workflow
A typical small business port goes wrong in very ordinary ways. The owner signs the form with the right company name, but the carrier still holds the old trading name. The port date is booked, then nobody sees the mobile verification code because the handset is in a desk drawer or still with a former staff member. Those are the delays that waste days.
The workflow itself is straightforward. What matters is doing each step in the right order and checking the details before the request goes in.
Preparation
Preparation decides whether the port moves cleanly or gets rejected for admin reasons.
Your role: pull the account details from a recent carrier invoice or service confirmation, then match them against what your new provider will submit. Check the legal entity name, service address, account number, and every number being moved. If you have multiple services with the same carrier, confirm you are referencing the right account.
Your new provider's role: check whether the numbers can be ported, identify any extra requirements for the number type, and confirm the target service is ready before the port date is requested.
This is also the point to confirm what is attached to the number. A main number might feed an IVR, hunt group, fax line, lift phone, alarm line, EFTPOS terminal, or an old analogue handset in the warehouse. If any of those still matter, list them now. Porting the number does not automatically rebuild those call flows on the new system.
Businesses moving service numbers should also decide early how they want those calls handled after cutover. If you are porting a 13 or 1300 service, it helps to review how a 1300 phone number works for call routing and national reach before the request is lodged.
Request and authorisation
This is the formal submission stage.
Your role: sign and return the authorisation quickly, using the same business details held by the current carrier. If the account is under a company entity but the bill is sent to a trading name, ask your provider which name must appear on the form. That small mismatch causes a lot of avoidable rejections.
Your new provider's role: lodge the request with the losing carrier, track responses, and tell you exactly what needs fixing if the carrier rejects it.
Do not cancel the old service. Leave it active until the port is complete and tested. I have seen businesses disconnect a line early because they assumed the signed form was enough. Recovering a disconnected number is harder, slower, and sometimes not possible within the timeframe the business expects.
Validation
Validation is where carriers compare the request against their records.
Your role: stay available and answer questions the same day if possible. If your provider asks whether the account is under an old ABN, a previous address, or a different entity, treat that as urgent. A one-line clarification can save a full resubmission.
Your new provider's role: manage carrier queries, correct submission errors, and confirm any action needed from you.
Mobile ports need extra attention. The approval code often goes to the mobile number being ported, not to the office manager who organised the job. If that handset is switched off, lost, shared between staff, or no longer in your control, the request can stall without much explanation. For multi-mobile ports, assign one person to physically check each handset and watch for those codes during the approval window.
The cutover
Cutover is the moment the number starts routing to the new service.
Before cutover, it helps to see the workflow in action:
Your role: keep staff informed, keep the old service active, and be ready to test as soon as the provider confirms the port is complete. Test the number from an external mobile and another landline if possible. If the number is moving to a hosted platform, check where calls should ring before the port window starts.
Your new provider's role: make sure the destination is already configured, monitor the cutover, and confirm when inbound and outbound services are working on the new platform.
Hosted Telecommunications and other hosted providers can port the number and land it on a cloud phone system, but that only helps if the call flow is built before the number moves. Auto attendants, ring groups, voicemail, business hours routing, and failover destinations should be ready in advance. If they are not, the port can complete technically while callers still hit the wrong destination.
Post-port checks
One successful test call is not enough.
Run a short live checklist while the port window is still fresh:
Inbound calls: test from a mobile and a separate external service
Outbound caller ID: confirm the correct business number displays
Main call flow: test hunt groups, auto attendant options, voicemail, and after-hours routing
User devices: check desk phones, softphones, and mobile apps
SMS on mobiles: confirm messages send and receive if mobile services were ported
Business dependencies: test any service that may still rely on the number, such as alarms, lift phones, fax-to-email, or merchant terminals
This final pass is where businesses catch the issues that generic porting guides skip. The carrier may mark the port complete, but your job is only finished when customers can call, staff can answer, and nothing important is still pointing at the old service.
Porting Timelines and Special Number Types
Timelines are where expectations often drift away from reality. Carriers work to formal standards, but the number type, the size of the order, and the quality of the information you submit all affect what happens in practice.
Under current industry codes, 90% of validated port requests must be finalised within 3 hours, and 99% within 2 business days, but practical timing still varies. Mobile ports can take roughly 3 hours to 1 week, local numbers generally take 3 to 7 business days, and large blocks can stretch to up to 4 weeks, as summarised in RingCentral's explanation of Australian number porting timeframes.
Estimated phone number porting times in Australia
Number Type | Typical Timeframe |
|---|---|
Mobile numbers | 3 hours to 1 week |
Local geographic numbers | 3 to 7 business days |
13, 1300 and 1800 numbers | 3 to 14 business days |
Large blocks or complex ports | Up to 4 weeks |
What changes the timeline
The headline timeframe is only part of the story. In day-to-day porting work, a few factors matter more than people expect.
Mobile numbers
Mobile ports often move quickly, but they can also stall if the verification step isn't handled promptly. If your staff carry business mobiles and you want to keep the same numbers, plan that step in advance instead of assuming it will just happen in the background.
For businesses moving users from separate handsets onto a more unified setup, it's worth planning how voice and messaging will be handled after cutover. If part of your migration also involves device changes, a practical guide on the steps to transfer your eSIM can help avoid confusion on the handset side while your business number arrangements are being finalised.
Geographic numbers
Single-site businesses often port a main office number first. Multi-site businesses may combine several office numbers into one hosted platform so calls can route to the right team regardless of physical location. That doesn't always make the port itself harder, but it does make pre-cutover configuration more important.
1300 and 1800 numbers
These need a little more preparation because ownership evidence matters. Porting 1300 and 1800 numbers into hosted PBX systems typically takes 3 to 14 business days after acceptance by the losing carrier, and a recent invoice not older than 3 months is required to verify ownership, according to this guide to porting business service numbers.
If you're reviewing whether to keep a service number or move one into a hosted environment, this overview of a 1300 phone number for business use gives useful context on how those numbers fit broader call routing.
Give yourself buffer time. Don't schedule a major campaign, office move, or peak trading event right on top of a planned port date.
How to Avoid Common Porting Disasters
A common small business porting failure looks like this. The forms are signed, the new phones are ready, and the owner assumes the hard part is done. Then the port is rejected because the account name is slightly different on the carrier record, or a staff member misses the mobile verification code while serving customers.
That is how ports get delayed. Not by some obscure technical fault, but by small admin mistakes that are easy to miss if nobody checks the carrier record before lodging the request.
The problem I see most often is confidence replacing verification. Owners often rely on memory for the account name, service address, or billing number, and that is enough to trigger a rejection.
The detail mismatch problem
The Porting Authority form has to match the losing carrier's records. Close is not good enough. If the service is billed to a company name with Pty Ltd included, use that. If the carrier still has your old office address on file, use that address until the port is complete.
“Service address” catches people out all the time. It is not always your current trading address. It is the address sitting in the carrier's system, which may be from a previous tenancy, a bookkeeper's setup years ago, or a legacy fixed-line account that nobody has touched since NBN was installed.
Use this check before anything is submitted:
Name check: Copy the account holder name exactly from the latest bill or carrier portal.
Address check: Use the recorded service address, even if the business has moved.
Account number check: Pull it from a current invoice, not an old email trail or someone's memory.
Authorisation check: Make sure the person signing is authorised on the account.
The mobile code trap
Mobile ports often stall because the person organising the move is not the person holding the handset.
For many business mobile ports, the gaining provider will trigger a verification SMS or code step that has to be completed promptly. If five staff members have five different mobiles, each person needs to know what to expect and when to respond. I have seen well-prepared ports miss their slot because one salesperson was on the road, ignored the message, and the whole batch had to be resubmitted.
If you want to reduce that risk, appoint one coordinator, brief every handset user in advance, and avoid lodging on a day when half the team is in meetings or on site visits.
The bundled service problem
Another regular mistake is porting a number that sits inside a bundle without checking what else is attached to it.
A business might assume it is only moving the phone number, then discover the old provider has linked that service to internet, EFTPOS backup, fax-to-email, or a legacy hunt group. The port can still go ahead, but the question to ask first is simple. What stops, what stays active, and what needs to be replaced before cutover?
Do not cancel the old service early. Do not ask the losing carrier to disconnect anything until the number has landed and inbound calls are working where they should.
A simple disaster-prevention routine
This is the checklist I give small businesses before any port is lodged:
Pull a current bill and copy the account details exactly
Confirm who has authority to approve the port
Check whether the number is tied to internet or other bundled services
Warn every mobile user about verification messages
Make sure call routing, handsets, and users are already configured on the new system
Leave buffer time around the port date in case a carrier rejects the first submission
If you are moving numbers into a hosted system, a provider with a defined port-in process on its hosted PBX network can catch many of these issues before the request reaches the carrier.
Most porting disasters are preventable. The businesses that get through with the least pain are usually not the most technical. They are the ones that check the account record, brief their staff properly, and do not assume the paperwork is “close enough.”
How Hosted Telecommunications Simplifies Your Port
Porting usually feels hard because it combines paperwork, carrier coordination, and cutover planning. Small businesses rarely struggle with just one of those. They struggle with all three landing at once while the team is still trying to answer customers and keep the day moving.
One practical option is Hosted Telecommunications porting on its hosted PBX network. The service supports porting and hosting for 02, 03, 07, 08, 13, 1300, 1800 and Australian mobile numbers, including use cases where businesses want mobiles and landlines on one hosted platform while retaining SMS capability on mobile services.
What matters most in any provider relationship is process discipline. The useful questions are straightforward:
Will they check your account details before lodging the port?
Will they explain what you need to sign and when?
Will they configure the hosted service before cutover?
Will they support Yealink desk phones, softphones, and routing changes after the number lands?
If the answer is yes, the port becomes much less risky. You're not removing the need for paperwork. You're removing unnecessary guesswork from the business side.
Frequently Asked Questions About Number Porting
A common small business scenario goes like this. The new phone system is ready, the team expects the number to move today, and then the port stalls because the account name does not match the losing carrier's record or the mobile verification SMS goes to a staff member who is in a meeting. Those are the practical problems that slow ports down far more often than the technical side.
Will I have downtime during the port
Usually, any disruption is brief if the cutover is planned properly. The bigger risk is not outage. It is calls still hitting the old service while your team has already switched handsets or softphones.
Keep the old service active until the new provider confirms the port has completed. Test inbound and outbound calling straight after cutover, and check hunt groups, auto attendants, voicemail, and any fax or alarm line that still depends on the number.
What if my number is bundled with internet
Check this before you sign anything. Some providers package voice and internet on one account, and porting the number can trigger changes to the broadband service or the contract term.
Ask the current provider a direct question in writing: if this number leaves, what happens to the internet service on the same account? That one step prevents a lot of avoidable cleanup later.
Can I port a disconnected number
In many cases, no. If the service has already been cancelled, there may be nothing active for the new provider to transfer.
The safer approach is simple. Leave the existing service live until the port is finished and confirmed. If the service has only just been disconnected, ask the current provider whether it can be reactivated before you lodge anything else.
Why do mobile ports fail so often
Missed verification is a big reason. Australian mobile ports often rely on a one-time code sent to the active SIM, and delays happen when the code goes to the wrong staff member, the handset is switched off, or the SIM has already been removed.
For business fleets, nominate one person to control the handsets and watch for the code during the port window. If your team is also changing devices, review the steps to transfer your eSIM before port day so you do not confuse a SIM move with the number port itself.
If you want to move to a Hosted PBX without risking your business number, talk to Hosted Telecommunications. Their Australian-based team can help you port existing 02, 03, 07, 08, 13, 1300, 1800 and mobile numbers onto a hosted phone system, coordinate the paperwork, and make sure the cutover is planned properly before anything changes.
Comments