Migrate Phone Number: 7-Step Hosted PBX Guide

Your office phones are ringing, but the system behind them's getting in the way. Calls land on mobiles, the desk phone at reception drops out, and every time you think about moving to a smarter setup, the number itself feels like the risky part. That's where a migrate phone number project stops being a simple admin task and becomes the cleanest way to replace the old PBX without throwing away the number customers already know.

For most Australian small businesses, the issue isn't whether a new phone system can do more. It's whether the business can keep the published number, keep inbound calls flowing, and make the change without a messy reprint cycle or a week of lost leads. Number portability is what makes that possible, because carriers must support keeping the same number when you change providers, and that portability is the foundation for hosted PBX migrations in Australia (FCC consumer guidance on keeping your number when you change providers).

Why Australian Small Businesses Are Moving to Hosted PBX

A lot of business owners reach this point the same way. One staff member is on the road, another's working from home, reception's buried under calls, and the old phone setup can't flex without more hardware and more pain. The company doesn't need more lines for the sake of it, it needs a system that follows people, routes calls properly, and keeps the main number intact.

That's where hosted PBX earns its place. It gives small teams flexible working locations, a digital receptionist, call queues, voicemail to email, and multi-site transfers on a single system. Instead of tying business calls to one room or one cabinet, the service sits in the cloud and lets staff answer from the office, home, or another site with the same business identity.

Practical rule: if your customers already know the number, don't treat it like a disposable line. Treat it like a business asset.

If you're still trying to work out what a published main number is in switchboard terms, what is a switchboard number is a handy reference point because it frames the number as the front door of the business, not just a handset label. That matters when you're planning a hosted PBX migration, because the point isn't to change how people reach you. It's to change everything behind the scenes while keeping the same inbound entry point.

The key Australian reality is that portability is a standard telecom function, not a special favour from a carrier. That's why replacing a legacy PBX with hosted telephony is usually operationally low-risk for SMEs, provided the port is planned properly and the old service stays alive until the transfer is confirmed (ACMA guidance on keeping or porting your phone number).

Paperwork and Authorisation Requirements for Porting

The port jobs that fail most often in the field usually fail on paperwork. A business will assume the number belongs to it, then the carrier checks the file and finds a different legal entity, an old billing address, or a service still tied to a bundle that nobody has cleaned up.

Match the account exactly

The gaining provider will ask for details that line up with the losing account. For Australian business ports, that normally means the legal entity name, the Billing Telephone Number, the service address, and the account PIN or password have to match exactly. If the account sits under the wrong entity name, or the billing address differs from what the old carrier has on file, the request can bounce before anyone touches the line.

Pull the current invoice and the account profile from the losing carrier, then check every field character by character. If a company trades under one name but bills under another, fix that before you submit anything. Multi-line accounts need extra care too, because you have to identify which number is the primary service and which numbers sit underneath it. Grouped accounts can hide the central control point, and that causes avoidable delays.

Gather the authorisation before you submit

The usual authorisation set is straightforward, but it has to be complete. A signed Form of Authority, a recent bill or invoice, and, where business names sit under a different structure, a Letter of Authority can all come into play. The new provider needs enough evidence to show the request is properly authorised.

Don't cancel the old service first. Keep it active until the port is confirmed, because the source account is what gives the transfer somewhere to land.

If you want a plain-language refresher on the account details carriers ask for, mobile number portability is a useful benchmark. Business accounts usually need more care than a simple personal mobile transfer, especially when the account has more than one number or a reception line tied to the main billing record. That extra care saves you from failed submissions and the back-and-forth that follows.

Watch for multi-line and inactive line traps

Business ports get messy when there are pending orders, inactive lines, or services bundled with internet or voice. A number can look portable on paper and still stall if the carrier has an active change order sitting on the account. Ask for a current service status summary before you lodge anything.

Use this as your prep list:

• Confirm the legal entity: Make sure the account name matches the registered business or trust exactly, not just the trading name.

• Check the billing telephone number: Identify which number the losing carrier uses as the account anchor.

• Verify the service address: Use the address on the current service, not the new office address.

• Collect the account PIN or password: Get the exact security details the carrier requires for release.

• List every number on the account: Mark whether each line is active, bundled, or sitting under a main service.

• Clear pending orders first: Cancel or complete changes before you submit the port.

• Ask about inactive numbers: Some carriers treat them differently from live services.

The admin work feels dull, but this is the part that prevents downtime. Clean account data gives the port request a much better chance of going through without follow-up calls, rejected forms, or a cutover that gets delayed at the last minute.

Porting Timelines and Number Type Differences

A port that works for a mobile service can still bog down on a fixed line or an inbound 1300 service. Carriers handle each number class through different queues and handoff rules, so the issue is usually timing, not the request itself. Business owners get caught when they expect every number to move on the same schedule.

Mobile numbers are usually the fastest

Mobile ports in Australia sit under the ACMA's Mobile Number Portability rules. The cleanest path is still the same, keep the losing service active, give the gaining provider the exact account details, and only cancel the old service after the port has been confirmed (ACMA phone number porting guidance).

Most failed mobile ports come back to the same causes, the account name does not match the billing record, the billing address is off, or the account PIN is wrong. I've seen plenty of jobs stall over one typo or a trading name being used where the legal entity was expected.

Fixed-line and inbound numbers need more planning

Geographic fixed-line numbers and inbound services like 1300 and 1800 usually involve more carrier back-and-forth, especially where the numbers sit under a business account with multiple services. Timelines are variable rather than fixed, and a transfer can take several business days depending on the number type and how quickly both carriers clear the paperwork (migration guidance on phone number transfers).

That delay matters more than most consumer guides admit. If the service is tied to a main billing record, or if there are bundled lines and inactive numbers in the mix, the port can sit waiting while the carriers sort out which service is being moved. For 1300 and 1800 services, it also pays to check the number itself, because inbound call handling can be part of a broader setup rather than a simple one-line transfer. For background on how these services are structured, see 1300 phone number basics.

Schedule the cutover around your call flow

Book the switch for a quiet period, not the first hour of the day when reception is already under pressure. Tell staff what the cutover window is, keep the old system available until the new one is live, and have someone ready to answer test calls as soon as the port completes. For businesses with multiple lines, that simple discipline avoids missed bookings, dead air, and the scramble that follows when no one can tell whether the port has landed.

A broader portability benchmark from Ukraine shows how quickly people use number portability once the process is reliable, with mobile porting activity rising sharply there in the cited period (Ukraine portability benchmark). Australia's process already does the heavy lifting, so the practical job is choosing a realistic cutover window and keeping the business reachable while the carriers do their part.

Pre-Cutover Configuration and Device Setup

A clean port starts before the number moves. If the hosted PBX is not ready, the number lands in a system that still needs provisioning, testing, and call-flow design. That creates avoidable delays, because the port itself can succeed while the phone environment is still not ready to handle real calls.

Build the new system before the old one closes

Set up the hosted PBX first, then point devices and users at it. Create the SIP trunk, provision the handsets, load the extensions, and check that the digital receptionist, call queues, time-based routing, and night mode work the way the business expects. For remote staff, install the softphone app and log it in before cutover so they are not learning it while calls are already waiting.

Yealink devices are a common fit for this kind of job, especially the T53, T54W, and T57W. If you are moving from a legacy desk setup, Yealink phones connect seamlessly to a hosted PBX is a useful internal reference on how those handsets slot into a hosted environment. In the field, the main advantage is consistency. When the phones are provisioned properly, staff do not need to care which site they are in.

Use temporary routing during the transition

I always recommend a temporary forwarding plan during the cutover window. If the port lands after business hours, or if a carrier stalls the confirmation, you need a clean way to push calls to a known mobile or backup number. That keeps inbound traffic from disappearing into a gap while the number is in transit.

Before you touch the port date, get the paperwork and the platform side lined up. Confirm the legal entity on the account matches the service records, check that every line in a multi-line setup is accounted for, and make sure any old hunt groups or direct-dial numbers are mapped to the right destination. If those details are off, the handover can still happen, but the business can lose call logic, voicemail access, or a clean routing path for some users.

Here is the pre-cutover checklist that saves pain:

• Gather credentials early: Make sure admin logins, SIP credentials, and handset details are ready before you touch the port date.

• Provision every handset: Load the Yealink devices and confirm each extension registers properly.

• Test internal calls: Check that one desk can reach another, including remote users.

• Verify voicemail to email: Send a test message and confirm the email lands where it should.

• Check hot desking: Make sure staff can log in and out cleanly if they share devices.

• Set fallback routing: Put a temporary forward or overflow destination in place.

• Confirm after-hours behaviour: Make sure night mode or time-based routing does not send calls somewhere unexpected.

If the new PBX cannot handle the call flow before the port, the port date is too early.

I have seen businesses rush this part because the number is the main thing. It is not. The number is only the key. The phone system has to be ready to catch it.

If the handsets are being replaced as part of the move, set them up in advance and confirm the provisioning profile before staff ever pick them up. A few minutes spent checking the desk phones, softphones, and failover routing saves a lot of noise when the port goes live.

Cutover Day: What Transfers and What Stays Behind

Cutover day looks straightforward from the office floor. The old number rings on the new platform, staff keep answering calls, and everyone hopes the handover is quiet. The part that gets missed is the paperwork and the data trail behind the live line.

The number moves, the records usually stay put

A port changes the live call path. It does not automatically move call recordings, voicemails, contacts, analytics, or historical messaging into the new hosted PBX. If those records matter to the business, export them before the cutover, along with anything else the old system holds that the team still needs. If you also need to move your data the easy way, treat that as a separate migration job, not something the number port will cover for you.

That split catches out a lot of business ports. The number is what people notice, but the old platform can still hold the operating history of the business, and sometimes the only copy of it. Once the port completes, that material may stay behind with the losing carrier or sit in a separate archive, so it is safer to back it up first and confirm who owns what before the cutover window opens.

Test the live service as soon as the port lands

As soon as the port is active, call the number from outside the office. Check inbound ringing, outbound calls, caller ID presentation, and the way the queue answers. Then test after-hours routing as well, because a number can look fine during the day and still fail once a time rule or night profile takes over.

A proper cutover check covers the parts that break in real offices:

• Inbound call test: Ring the ported number from an external mobile.

• Outbound call test: Confirm staff can place calls and present the right caller ID.

• Queue behaviour: Make sure overflow, wait messages, and ring groups work.

• After-hours routing: Check the night profile or time-based rule.

• Voicemail delivery: Confirm message alerts and email notifications.

• Remote user login: Test a softphone or off-site extension if the team uses one.

If one of those checks fails, fix it while the old service details are still fresh and the cutover window is open. The common mistake is calling the port complete the moment the number starts ringing. A port only counts when the business can keep trading on it.

Common Migration Blockers and How to Resolve Them

Most blocked ports don't need drama, they need diagnosis. The losing carrier usually has a reason, and once you know the reason, the fix is often administrative rather than technical. The hard part is getting the account clean enough for the carrier to stop arguing with it.

Start with the obvious blockers

Pending orders are a classic hold-up. If there's a change order, cancellation, or bundle adjustment sitting on the account, the port request can stall until that work is cleared. Bundled services cause the same headache, because the number may be attached to internet, fax, or voice services that need to be separated before release.

Another frequent problem is ownership ambiguity across multiple business entities. One office may pay the bill, another entity may trade under the name, and the carrier records might show something else entirely. When that happens, the port request needs the legal relationship documented before it can move forward.

Resolve the blocker, don't just resubmit

A resubmission with the same bad data just burns time. Fix the mismatch, clear the pending order, or unbundle the service, then lodge again with the corrected details. If the losing carrier has placed a porting bar or disputes ownership, ask for the reason in writing and work from that rather than guessing.

For teams worried about moving their files and records while the number is being transferred, move your data the easy way is a useful reminder that number migration and data migration are separate jobs. That's the point many businesses miss, the phone number can move while the operational history needs its own backup plan.

If the matter escalates, the Telecommunications Industry Ombudsman scheme exists for disputes that don't get resolved through normal carrier support. I don't like seeing a port go there, because it means the clean path failed, but it's the right escalation route when the carrier won't release a number that should be portable. The practical lesson is simple. Clean the account, document the authority, and keep the old service alive until the issue is settled.

Office Relocation Tips and Rollback Planning

A hosted PBX makes an office move much less painful than the old on-premise setups ever did. You can move the phones to the new site, plug them into the internet there, and keep the business number and extensions working across any location with connectivity. For a moving day checklist that addresses the physical side of the relocation, office move checklist Sydney is a handy companion while you coordinate the telecoms separately.

The telecoms tip is this. Don't treat the office move as a separate event from the number port if the new office is part of the same transition. Make sure the new site has internet live, the handsets are packed with labels, and the forwarding path is documented before anyone starts unplugging gear. Hosted PBX shines here because staff can keep using the same extensions across sites, which keeps customer contact simple.

Rollback planning matters too. Keep the old service active until the port is fully confirmed, maintain a temporary forwarding number, and write down the exact steps needed to reverse the move if a critical problem appears. That includes who calls the losing carrier, who updates the hosted PBX portal, and who tells reception what number to use while the issue is fixed.

One clean rollback plan is better than three frantic phone calls after a failed cutover. If you've got the old service live, the backup route tested, and the new system configured but not yet trusted, you can protect the business from a bad port without losing calls.

---

If you're planning to migrate phone number services into a hosted PBX and want it handled by a local team that knows the Australian porting process, Hosted Telecommunications can set up the new system, port the number, and keep the transition practical. Visit Hosted Telecommunications to talk through your existing lines, your office move, or your cutover plan before you book the port.