How Long Does Number Porting Take in Australia

Mobile number ports in Australia typically take 1 to 3 business days, while most standard local-number ports finish within 8 business days. Complex or multi-service ports can stretch to several weeks, so a hosted PBX cutover needs more planning than choosing a go-live date.

You're probably asking because the office is ready to move, the new handsets are configured, and someone has suggested that keeping your existing numbers will be straightforward. It usually is, but the number itself determines the timetable. A mobile, a standard geographic number, a 1300 number, and a group of numbers tied to an older PBX all travel through different checks.

The practical mistake is planning around the new provider's sales promise. Plan around the most complicated number in the batch, keep the old service active, and build a buffer for rejected requests or carrier questions.

The Short Answer and Why It Depends on Your Number Type

Your hosted PBX go-live date should follow the number category, not the sales estimate. Use these planning bands:

• Mobile numbers: typically 1 to 3 business days, with many completing in about 3 hours. The Australian Communications and Media Authority explains the regulated number-portability framework.

• Standard local geographic numbers: often 5 to 8 business days when account details and service configuration are correct. Australian porting guidance outlines the usual timeline for local numbers.

• 1300 and 1800 numbers: usually need separate coordination and can take several business days to two weeks. Australian guidance on 1300 and 1800 transfers explains why these numbers need different handling.

• Complex multi-service ports: can take several weeks. Cross-technology transfers, multiple numbers, and services tied to older platforms require more checks. Allow 15 to 20 business days or more where the request is complex, in line with the portability expectations described by ACMA.

Check the number type, the losing carrier's account record, and every service attached to the number before booking go-live. A single geographic number on a standard business account is relatively predictable. A number block linked to ISDN, fax, line hunting, call queues, or multiple sites needs a longer cutover plan.

Planning rule: Schedule the hosted PBX go-live around the slowest number and the strictest realistic window. Keep the old service active until testing confirms the new routing works.

Hosted PBX removes on-site PBX hardware and specialist maintenance, while letting staff use the same extension from the office, home, or another approved internet connection. Australian hosted PBX guidance compares traditional and hosted system costs, while cloud PBX information for Australian users explains remote connectivity.

What Number Porting Actually Means

Number porting is like changing electricity suppliers while staying at the same address. The wiring into the premises remains, the address remains, and the service continues, but the company responsible for supplying and billing the service changes.

With a phone number, the number stays the same while the losing carrier releases it and the new hosted PBX provider takes responsibility for routing it. Your customers still dial the familiar number, so you don't need to reprint every invoice, update every website, or tell regular callers to use a replacement contact.

The number is the identity being transferred. The phone system attached to it is a separate matter.

What moves and what doesn't

The port request transfers the right to use the phone number. It doesn't automatically transfer:

• Voicemail messages, greetings, or old call recordings.

• Desk phones or PBX hardware supplied by the previous carrier.

• Call queues, IVRs, hunt groups, and time-based routing unless the new provider builds them separately.

• Fax, alarm, or other linked services that may depend on the old carrier's configuration.

That distinction matters during a hosted PBX migration. You may port the main number while separately creating extensions for staff, configuring a digital receptionist, assigning direct numbers, and setting call routes. The number transfer preserves the dialling identity, but it doesn't reproduce the old system's behaviour.

A business can therefore have a successful port and still experience a poor cutover if the new PBX hasn't been configured. The number may arrive at the new network, but calls could reach the wrong extension, bypass a queue, or fail to follow the intended after-hours route.

Keep the workstreams separate. Treat porting as the carrier-to-carrier transfer, and treat PBX provisioning as the design and configuration of how calls behave after activation. Your go-live date is safe only when both are ready.

The Three Stages Every Port Goes Through

Every business port follows three stages. The number category and service complexity set the overall schedule, while accurate customer information determines how quickly the order can move. For a hosted PBX cutover, plan the PBX build alongside the port, not after it.

1. Request

The new hosted PBX provider prepares and lodges the port request with the losing carrier. The order usually requires a signed Letter of Authorisation, current account details, and a precise list of the numbers being transferred.

This should be ready on the first business day. Supply the latest invoice, copy the account holder's legal name exactly, and confirm every number included in the order. Keep the old service active until the port completes. The carriers need an active service to validate and release the numbers.

Your number category affects what happens next. A straightforward mobile or local number generally needs less coordination than a 1300 or 1800 service, a number block, or a multi-service arrangement. Give the new provider the full service context at request stage.

2. Validation

The losing carrier compares the request with its records. It may check the account name, account number, service address, number ownership, and features attached to the service.

A clean order can move through validation quickly, but mismatched details and complex services create delays. Old invoices, incomplete account information, multiple numbers, fax services, alarm diallers, rotary services, line hunting, ISDN, and inbound-only arrangements all deserve careful checking before submission.

Respond to carrier notifications immediately and correct errors through the new provider. Do not rely on details remembered from an old bill. Once the carrier accepts the request, scheduling and technical coordination become the main tasks.

3. Activation

Activation is the final cutover. The number is redirected from the losing carrier to the new hosted PBX network during an agreed window, usually outside the busiest office period.

The network switch is often quicker than the administration around it. A scheduled activation window may last 1 to 4 hours, depending on the carriers, number type, and PBX configuration. During that window, the provider should check registration, inbound routing, outbound caller identity, queues, and after-hours call paths.

You can speed up request and validation by being organised, but you cannot force carrier approval to happen instantly. Schedule hosted PBX go-live only when the configuration, testing, and activation plan are ready together.

Realistic Timelines by Number Category

Number type sets the first usable estimate. Plan the hosted PBX go-live around the realistic window, not the carrier's fastest possible result. The table assumes a clean request and should guide scheduling, not serve as a guarantee.

Number Category	Typical Timeline	Best Case	Worst Case	Key Variables
Mobile	1 to 3 business days	About 3 hours	Several business days	Account match, mobile account details, carrier confirmation
Standard local geographic, 02, 03, 07, 08	5 to 8 business days	Faster after approval	Up to 15 business days under the broader framework	Billing data, service type, number ownership, carrier handling
1300 and 1800	Several business days to two weeks	Several business days	Two weeks or longer	Smartnumber coordination, carriage service, routing configuration
Complex multi-service or multi-number	2 to 4 weeks for planning, potentially longer	About two weeks	30 business days or several weeks	ISDN, DIDs, number blocks, fax, line hunting, cross-technology migration

Mobile numbers

Mobile ports usually move fastest. Allow 1 to 3 business days, although a correctly matched request can complete in around 3 hours. Businesses can use this Australian guide to mobile number portability when preparing a mobile migration.

Do not schedule a same-day hosted PBX launch solely because the number might transfer quickly. Confirm the user, extension, voicemail, outbound caller identity, and call flow first. Set go-live after those checks are complete, with enough time to respond if carrier confirmation takes longer.

Standard local numbers

A clean geographic number generally needs more carrier validation than a mobile. Schedule 5 to 8 business days for an ordinary local number. For a firm operational deadline, allow the broader framework of 8 business days for 80% of local ports and 15 business days for 98%.

Book the PBX cutover after approval and configuration testing, not at the start of the request. Local service details, number ownership, and billing records can change the practical date even when the number appears straightforward.

1300 and 1800 numbers

1300 and 1800 numbers need their own plan because smartnumber and carriage-service coordination can add time. Allow several business days to two weeks, with two weeks or longer possible for routing work or provider coordination.

Configure the hosted PBX destination before the port date. Keep the existing service available until the new inbound route has been tested and the cutover window is confirmed.

Complex services

Multi-number orders linked to ISDN, inbound-only services, number blocks, fax, or line hunting belong in the longer planning bracket. Allow 2 to 4 weeks for planning, with 15 to 20 business days or more possible for the port itself. Bundled complex ports can require 8 to 12 weeks, so schedule the hosted PBX go-live only after service dependencies, routing, and testing have been mapped. The Australian Category A and Category C comparison shows why complex ports need a longer runway.

What Slows a Port Down and What Speeds It Up

A port can be technically ready and still miss its cutover window. The usual causes are inaccurate carrier records, an incomplete service inventory, or a number attached to services that cannot be separated cleanly. Treat these checks as schedule controls, not paperwork.

Red flags to remove before lodgement

• Account-name mismatch: Copy the exact legal or trading name from the latest invoice. A shortened name, previous company name, or changed punctuation can trigger rejection.

• Incorrect account number or stale invoice: Use the newest bill and check every digit before submission.

• Unresolved linked services: Identify fax, alarm diallers, MessageBank, line hunting, rotary groups, and other features before requesting the port.

• Hidden dependencies: Review DID blocks and ISDN-linked services properly. Do not rely on a handset label or partial number list.

• Billing or contract matters: Resolve balances, pending changes, and minimum-term questions before validation begins.

• Missed carrier notifications: Read and answer CAT-A or CAT-B notices promptly. An unanswered request can hold the port while the planned date passes.

• Multi-site routing clashes: Confirm the point of interconnection and destination for each site where offices share a number plan.

Actions that protect the schedule

Give the new provider one accurate source of truth and nominate an account holder who will answer validation questions. Port related numbers in one coordinated batch where possible. Scattered requests create dependencies and make fault isolation harder.

Build the hosted PBX before the carrier confirms the cutover. Preconfigure the extension map, IVR, queue membership, business-hours routing, and voicemail-to-email settings. Then test inbound calls, failover, and user destinations before go-live, rather than trying to configure the system during activation.

For mobile, local, 1300/1800, and complex multi-service ports, use the timeline for that number category to set the PBX cutover window. Do not book go-live against an optimistic approval date.

The controllable risk: Give the new provider accurate records, complete the service inventory, and respond quickly to every validation question.

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

Documents and Details to Have Ready Before You Start

A port request can stall before the carrier sets a cutover window. Give the new provider records that match the losing carrier's account exactly, then prepare the hosted PBX configuration around the number category and planned go-live.

Keep this pack ready:

• Latest Tax Invoice: Include the losing carrier, account-holder name, account number, billing address, and complete number list.

• Business identity: Provide the ABN or ACN so the provider can confirm the legal entity.

• Signed authority: Supply a Letter of Authorisation or Port Authority when the new hosted PBX provider submits the request.

• Service history: Record the losing carrier, original activation date where available, and any remaining contract term.

• Feature inventory: List fax, alarm, hunt-group, ISDN, inbound-only, and multi-site dependencies. These features need separate checking before the PBX cutover.

Mobile ports require the carrier's exact mobile records. Have the SIM serial, account holder's date of birth, and mobile account details ready.

For a local geographic number, confirm the service address and account name. For 1300/1800 numbers, include every associated service and routing feature. Complex multi-service ports need a site-by-site service list, so the provider can stage the PBX without leaving a branch, fax, or alarm disconnected.

Why accuracy matters

Copy the account name exactly. Use the company name if that is how the losing carrier records the service, not a director's or store manager's name. Check the billing address against the invoice, rather than relying on the physical installation address.

Submit a complete pack on day one. The provider can then lodge a coherent request and build the PBX against the intended activation window. Missing details trigger clarification emails, rejected orders, and a later go-live, especially where several services must move together.

Porting Without Losing Calls During the Cutover

At 8:30 am on cutover day, the office manager checks the port order, confirms the staff list, and keeps the old service active. The hosted PBX should already be provisioned, the SIP trunk registered, and each employee briefed on the correct handset or softphone. Go-live should follow this readiness check, not precede it.

Before the activation window, confirm the temporary diversion plan. Route the main number to a mobile or controlled destination that keeps the business reachable while the carrier completes the handoff. Do not assume the old carrier will forward calls automatically. Once the number activates, routing responsibility changes and the previous forwarding arrangement may stop applying.

The test sequence

During the window, complete these checks in order:

1. Call the main number from an external mobile.

2. Confirm delivery to the receptionist, queue, or IVR.

3. Test an extension transfer.

4. Check the after-hours or fallback route included in the launch.

5. Make an outbound call and verify the intended business caller identity.

6. Repeat the inbound test from another network.

Agree the working window with the provider before the port date. The operational handoff may occur between 9 am and 5 pm AEST, depending on the carrier process and order. Schedule staff coverage for the full window, particularly for a local, 1300/1800, or multi-service port where routing checks may take longer.

If an inbound call fails, stop changing PBX settings without evidence. Record the calling number, time, destination, and result, then contact the new provider's porting support. The old carrier can retain part of the routing briefly after cutover, so support should monitor the issue rather than declare success after one test.

Keep connectivity stable throughout the handoff. If the PBX relies on business internet, confirm the connection and failover plan before activation. Review business internet plans for Australian offices as part of that assessment, and do not schedule go-live until the destination system and its fallback path are ready.

Practical Steps to Keep Your Port on Schedule

Start with the losing carrier's latest invoice. Copy the account name, service address, account number, and authorised contact exactly. Small differences can trigger validation queries and push back the hosted PBX go-live date.

Before lodging the request:

1. Clear outstanding balances: Resolve unpaid charges, hardware arrangements, or early-termination matters.

2. Record linked features: Identify MessageBank, fax, alarm diallers, line hunting, and other services, then agree how each will work after cutover.

3. List every number: Include the main number, direct numbers, full ranges, and all 1300 or 1800 services.

4. Set a workable date: Book the cutover with the new provider at least 5 business days ahead. Allow longer for local, 1300/1800, or multi-service ports.

5. Keep the old service active: Cancel it only after inbound and outbound testing passes on the new PBX.

6. Let the new provider lodge the request: They should manage the Losing Carrier process, authority trail, and responses to validation questions.

Do not schedule staff leave on the cutover day. Keep someone available to approve corrections, test calls, and confirm the go-live decision. Use this guide to migrate a phone number for the wider preparation sequence.

Hosted Telecommunications can assess your number categories, prepare the hosted PBX, lodge port authority, and coordinate cutover. Discuss your Australian business numbers, remote staff, multi-site routing, and go-live schedule with Hosted Telecommunications.