VoIP Phone Keep Your Number: A Complete Guide 2026

You can get the hosted PBX features, the flexible work locations, and the cleaner call handling without throwing away the number customers already trust. That's the main job when a business decides to move to VoIP, keep the number, keep the reputation, and make sure the phones don't go dead in the middle of the switch.

The mistake I see most often is simple. A business owner picks a new phone system, signs the paperwork, then assumes the old number will “just come across”. In Australian practice, that number is often the thing holding the whole business together, because it sits on invoices, vans, signage, websites, Google listings and old-fashioned word of mouth.

Why Keeping Your Number Matters More Than the Technology

The worst call I've seen in a porting job is the one that never comes through. The business had switched systems, the new hosted PBX was live, but the old published number had been cancelled too early. Customers rang, got nowhere, and some of them probably went straight to a competitor without ever telling the owner.

That's why voip phone keep your number isn't a nice-to-have phrase, it's the main requirement. In Australia, the regulatory foundation is number portability, and the ACMA treats local and mobile number portability as established rights in the telecommunications system. Carriers must support transfers so customers can retain their existing numbers when changing providers, which is exactly what lets a business move from legacy voice services to SIP or VoIP without changing the number everyone already knows. ACMA-aligned portability guidance

The number is part of the brand

For a small business, the number is rarely just a technical identifier. It's baked into the customer's memory, into quote forms, into directory listings, into payment reminders, and into every place a lead might try to call you back.

That's why hosted PBX is attractive in the first place. It can centralise call handling, let staff answer from different places, and keep the same published number in front of customers. The Australian Government's teleworking guidance makes the broader point clearly, cloud-based communications let employees work from multiple locations because the service rides over the internet rather than being tied to a single office line. Australian Government teleworking guidance

If the number is the one thing customers already know, don't treat it like an afterthought in the migration plan.

The practical issue is continuity. In Australia, the PSTN era winding down through NBN Co's migration program pushed a lot of businesses to rethink voice platforms, but the businesses that handled it well didn't just “upgrade”. They ported the number, kept the old service alive until cutover, then tested the new hosted PBX before trusting it with real calls. NBN migration context

Which Numbers You Can Actually Port to VoIP

Most advice says “yes, you can keep your number” and stops there. That's too blunt for Australian businesses, because the rules and routing expectations differ depending on whether you've got a geographic number, a mobile number, or an inbound service number.

Start by identifying the number type

Geographic numbers in codes like 02, 03, 07 and 08 are the classic business landline numbers. In Australia, local, national and mobile calls are generally portable, and geographic numbers are commonly moved into hosted PBX systems so the call handling can happen in the cloud. The ACCC's portability overview confirms that these calls are generally portable under the regulated numbering framework. ACCC portability guidance

Mobile numbers starting with 04 are also generally portable. The port works, but the carrier checks still matter, and the business should confirm whether the number is being used as a direct contact line, a two-factor verification line, or a general business mobile before moving it into VoIP routing. That detail matters because some workflows don't belong on the same line as the main inbound office number.

Inbound service numbers such as 1300 and 13 numbers behave differently again. They're not ordinary geographic lines, and the new provider has to support the range and routing setup properly. If the business depends on call queues, overflow routing or location-based distribution, those rules need to be recreated in the hosted PBX rather than assumed to transfer by magic.

Check eligibility before you sign

The number usually needs to be active, and the account details must match the losing carrier's records. The practical rule is simple, if the billing name, service address or account number is off, the port can stall or be rejected. The most common failure point is mismatched account data, which is why porting workflows usually start with the most recent bill and a careful account check. ACMA-aligned porting FAQ

Don't assume a complex legacy setup will survive intact. Hunt groups, special routing and old ISDN dependencies often need re-engineering on the hosted system.

That's the part generic guides miss. The number may port cleanly, but the old service structure around it might not. A number is portable, a badly documented call flow is not.

Paperwork and Authorisation You Need Before the Port

A clean port starts before the order is placed. If you wait until after the install to chase paperwork, the port can end up sitting behind everything else while the business keeps paying for two services and still can't answer calls properly.

Get the matching details right

The core document is the Letter of Authorisation, or LOA, signed by the account holder. The gaining carrier uses that to show the port was properly authorised. You'll usually also need a recent bill from the losing carrier, because it shows the number, the billing name and the service address exactly as the carrier has them.

That exact match matters more than most owners expect. Even a single character difference in the legal entity name can bounce a request. If the bill says one entity name and the LOA says another, the carrier may reject the port rather than guessing who really controls the line.

Add the account PIN or password if the losing carrier uses one. If the business has a security passcode, the gaining carrier will often ask for that too, because the port request has to survive the losing carrier's verification checks.

Who can sign for the business

A sole trader usually signs as the account holder. A company needs the authorised director or someone with explicit authority to act for the company. Trusts need trustee details, and the paperwork should reflect the entity that owns the service, not just the trading name printed on the website.

That's where a lot of small business ports go sideways. The phone service might be in the old trading name, the billing record might be in the company name, and the bank account might be under a different entity again. The carriers don't reconcile that mess for you.

The fastest port I've seen was never the fanciest one. It was the one where the owner produced the bill, the LOA and the exact account details before anyone touched the order.

If you're using a new hosted PBX supplier, hand over the paperwork before you lock in the install date. That way the carrier can check the port while the rest of the setup is still being staged, instead of finding a mismatch on the morning you want to switch.

The Porting Process From Quote to Cutover

A proper port is a managed handover, not a same-day gamble. The business should know who is checking what, when the losing carrier can object, and what gets tested before anyone declares victory.

The sequence that actually works

1. Portability check. The gaining provider checks the specific number and confirms whether it can move into the hosted PBX setup.

2. LOA and order submission. The provider lodges the authorisation and the port request into the carrier process.

3. Carrier verification. The losing carrier checks the customer of record and matches the account details.

4. Scheduled cutover. The number switches during the agreed handover window.

5. Live testing. Inbound and outbound calls are tested straight away.

The ACCC says standard ports can take up to 2 business days once everything matches, which is useful because it keeps the downtime window tight when the paperwork is clean. ACCC number portability guidance

What to expect during the handover

The gaining carrier usually holds the order while the losing carrier verifies the request. In some cases the losing side may contact the customer directly, especially if the account details need confirmation. That's why you don't want the main phone line sitting cancelled, disconnected or half-migrated while the request is still in flight.

For a hosted PBX migration, the handover window should be scheduled with enough time to test routing before the business day gets busy. After the switch, call the number from outside the office, check the outbound Caller ID, listen to voicemail, and make sure the hunt group lands where it should.

The practical lesson is boring but important. Don't treat the port confirmation as the finish line. Treat it as the start of testing.

You can see the mechanics of a business port in Hosted Telecommunications' own explanation of VoIP phone number porting, but the operational reality is the same across providers. The carrier wants clean data, the cutover needs a window, and the business needs to verify every key call path before staff start trusting the new system.

https://www.youtube.com/embed/b4HeJoHLmmM

Costs, Billing and the Trap of Cancelling Too Early

The financial side of a port is usually simpler than people fear, but it gets messy when someone cancels the old line before the transfer is complete. That one mistake is still the easiest way to lose a number.

Who bills what during the move

The existing service normally stays billed by the losing carrier until the port completes. That means the old line stays active, and the new hosted PBX service runs alongside it until cutover. If there's billing overlap, the owner needs to check the pro-rated charges and final invoice timing so the same line isn't being paid twice longer than necessary.

Many hosted PBX providers absorb standard porting fees, but complex numbers, multi-line migrations or rushed requests can attract charges. That's a commercial detail worth confirming before the order goes in, not after the invoice lands.

The real risk is early cancellation

The operational rule is blunt. Keep the old service active until the port is finished. If you cancel too early, you can orphan the number, and then the business is left chasing both providers while calls start missing in real time.

That risk matters even more if the number is tied to something other than standard voice. Fax lines, alarm diallers, lift phones and EFTPOS-related services are the hidden dependencies that often sit on the old service. If one of those services is still in play, the port plan has to include it.

A number parked on a low-cost hosted PBX seat can be a sensible holding pattern when premises change or operations pause. It keeps continuity without forcing a full live line.

For billing clarity, it also helps to compare how other industries handle service cost structures. The breakdown in Dodo Payments Merchant of Record costs is from a different part of the payments world, but the lesson transfers cleanly. Hidden fees and unclear handover terms are where small businesses lose money, not in the headline price they saw first.

The best cash-flow outcome is simple. Confirm the port fee, keep both services active for only as long as necessary, and don't let anyone cancel the losing line until the gaining carrier says the number has landed.

Pitfalls After Cutover and How to Test Properly

A number port can succeed on paper and still fail in the one place that matters, the next inbound customer call. That's why post-cutover testing is essential.

What silently breaks

The most common problems are boring and expensive. Outbound Caller ID can show the wrong number, voicemail-to-email can fail because the mailbox or routing is wrong, and hunt groups can send calls to the wrong extension. Some businesses also discover that fax machines, monitored alarms, EFTPOS lines or lift phones were still wired to the old service.

The Australian Government's cloud communications guidance supports the flexibility angle, staff can answer from multiple locations because calls ride over the internet. That's true, but only once the routing has been verified and the business has checked that the same number reaches the right people from home, branch office or mobile softphone. Teleworking and cloud communications guidance

A simple one-hour test plan

• Call the main number from a mobile. Make sure each hunt group rings in the right order.

• Place an outbound call. Check that Caller ID shows the business number, not a random old line.

• Leave a voicemail. Confirm the message arrives where it should.

• Trigger after-hours routing. Test the night mode or time-based rules.

• Call from an external menu. Use a customer-style path and see whether the IVR lands in the right place.

If your hosted PBX setup includes softphones or remote staff, repeat the test from at least one non-office device. The point is to verify the actual call path, not just the pretty dashboard.

You can also use the simple checks in Hosted Telecommunications' VoIP speed test guidance as a reminder that voice quality depends on the service path as much as the handset itself. Good call flow and good network performance need to line up.

| Common Post-Port Failures and How to Spot Them | | | | Hidden dependency | Symptom | Quick check | | Fax line | Faxes don't send or receive | Send a test page from an external line | | Hunt group | Calls hit the wrong person | Ring the main number and watch the sequence | | Caller ID | Outbound calls show the wrong number | Call a mobile and inspect the displayed number | | Voicemail routing | Messages don't arrive by email | Leave a test voicemail and confirm delivery | | After-hours rule | Calls ring when they should go to voicemail | Call after hours and listen to the greeting |

The main thing is to test before customers find the bug for you.

Your Porting Checklist and Where to Escalate

A clean port is a three-way job. The owner gets the authorisation and account data right, the IT admin prepares the phone system, and the provider handles the port submission and handover.

The hand-off checklist

• Business owner. Sign the LOA, gather the recent bill, and confirm the account details match the losing carrier exactly.

• IT admin. Document the current call flow, prepare the handsets, set up softphones, and plan the cutover testing. Yealink T53, T54W and T57W handsets are common hosted PBX options for businesses that want desk phones alongside softphones.

• New provider. Validate the number range, submit the port, explain the timing clearly, and provide the escalation path if wholesale delays appear.

When something goes wrong, start with the gaining carrier, then raise it with the losing carrier if needed. If neither side resolves it, the Telecommunications Industry Ombudsman, or TIO, is the formal escalation route for Australian telecom disputes, and providers in this space should be members of that scheme.

Hosted Telecommunications is one example of a provider that can port in and host existing numbers on a hosted PBX platform, with Australian-based setup and support. If you're planning a move and want the number to survive it intact, speak with a team that can check the paperwork, stage the port and test the cutover with you. Visit Hosted Telecommunications and start the conversation before you cancel the old line.