The Nine, Ranked
Ranked by consequence rather than frequency, because the two do not correlate — the most common failures are the mildest, and the worst one is rare enough that most businesses have never seen it happen.
| # | Failure | Consequence | Reversible? |
|---|---|---|---|
| 1 | Someone cancels the old service in order to move it | The number is permanently lost | ✗ No |
| 2 | A monitored alarm or medical alert stops reporting | Silent, and discovered when it is needed | ~ Yes, but the gap already happened |
| 3 | Port rejected on entity name mismatch | Date slips, sometimes past a hard deadline | ✓ Yes |
| 4 | Number range cannot be partially split | Plan rebuilt late, some numbers stranded | ✓ Yes, expensively |
| 5 | Early termination charge discovered afterwards | An invoice nobody budgeted for | ✗ Not really |
| 6 | Cutover scheduled on a Friday | Any problem gets 65 hours to run | ✓ Yes, on Monday |
| 7 | Call flow rules never documented before replacement | Calls quietly go to the wrong place for months | ✓ Yes, once noticed |
| 8 | Staff never shown the new system | Workarounds harden into permanent habits | ✓ Yes, harder later |
| 9 | Old service cancelled before the new one was verified | No fallback when something is wrong | ✗ No |
The pattern across all nine
Not one of them is a technical problem. Every single failure on this list is a process or communication failure — something not asked, not written down, not walked, or not said to the right person. That is genuinely good news, because it means none of them requires expertise to prevent. It requires a list and someone using it.
Failure 1: The Helpful Cancellation
This is the one that matters, so it comes first and it is short.
To move a number to a new provider, you sign an authority and the new provider arranges everything with the old one. You never contact the old provider. You never cancel anything.
What goes wrong: the losing provider rings the business — often accounts, often someone with no involvement in the project — and asks whether they would like to close the account. The person says yes, because that seems like the tidy and correct answer. Cancelling the service releases the number. A released number goes into quarantine and is no longer yours. There is no appeal, no escalation, and no technical fix. The number that is on your vehicles, your signage and fifteen years of Google results is gone.
Send this email before you start
To everyone who might answer a call from your current provider: “We are moving our phone service. If [provider] contacts you about closing, cancelling or disconnecting any service, the answer is no and please forward it to me. Do not agree to anything, including anything described as routine.” Ninety seconds of work. It prevents the only genuinely irreversible outcome in this entire process, and the people who cause it are invariably trying to be helpful.
The related version of the same mistake is failure 9: cancelling the old service too soon after cutover. Keep it alive but idle for a few weeks. One month of line rental is the cheapest insurance in the project, and it is the only thing standing between you and a very bad week if something turns out to be wrong.
Failure 2: The Alarm That Stopped Reporting
The second worst, and the one that produces the actual incident.
An Australian business phone line is rarely carrying only phone calls. When the service changes, the other things on that line can stop working — and critically, they stop working silently. The device continues to behave normally at your end. Nothing arrives at the other end. Nobody finds out until the day it is needed.
| Device | What you see | What is actually happening |
|---|---|---|
| Back-to-base alarm | Arms, beeps, lights up normally | The monitoring centre is receiving nothing |
| Medical alert pendant | Pendant works, base unit responds | No signal leaving the building |
| Fire panel dialler | Panel appears healthy | Not reporting — a compliance and insurance problem as well as a safety one |
| Lift emergency phone | Nothing visible at all | The button in a stuck lift now does nothing |
| EFTPOS on a line | Declines or fails to settle | At least this one announces itself immediately |
| Gate and door intercom | Visitors cannot get in | Discovered at the worst possible moment, always |
| Fax | Appears to send, does not arrive | Still genuinely used in legal, medical and freight |
The prevention is unglamorous and it works:
- Walk every building with your feet, not from a list. Look behind reception, in comms cupboards, in ceiling spaces, in the lift motor room. Anything plugged into a phone socket goes on the inventory.
- Identify the contractor for each device. Alarm, medical alert, fire and lift are four separate companies with four separate lead times.
- Contact them before you choose a cutover date. Fire and lift usually have the longest lead times, which makes them the critical path — their availability sets your date, not the reverse.
- Get a written signal test per device after cutover. A test and a record of it, not a verbal assurance from someone who did not check.
If you do one thing from this page
Do the walk. Every genuinely serious changeover failure involves a monitored device that stopped reporting and was not noticed. Everything else on this list produces an awkward afternoon or an unbudgeted invoice. This is the one that produces a real incident, and it takes an hour to prevent.
Failures 3 and 4: Ports That Do Not Complete
Two different problems that present the same way — a date that keeps moving.
Failure 3 · The entity name
The port authority must match the losing provider's records exactly — legal entity, address and account number as they hold them, not as you would write them today. A trading name where the records show the company entity is the single most common rejection. Ask your current provider what name the account is in, in writing, before you lodge anything.
Failure 4 · The range
If you hold a block of numbers, taking part of it and leaving the rest is often not possible. A business that plans to move its main number and a few directs, leaving the rest behind, can find the whole plan needs rebuilding. Confirm the scope of the range in the first week, before dates are set or announced.
Both are avoided by the same discipline: lodge early enough to absorb one rejection. A port that has four weeks of slack in it survives a name mismatch without drama. A port lodged with three days to spare does not, and if a product retirement date is behind the timing, there is no slack at all to be had later.
Failure 5: The Charge Nobody Asked About
The most common surprise, and it is financial rather than technical.
Two facts that are frequently misunderstood together. Porting a number away does not cancel your contract, and it does not extinguish an early termination charge — the port moves the number, and the contract continues to exist until it is separately dealt with. And most businesses do not have one contract; they have several services signed at different times with different end dates.
| Ask for, in writing, per service | Because |
|---|---|
| The contract end date | There is rarely a single one. Lines, internet and mobiles usually differ |
| The early termination charge | Typically remaining months of service charge, sometimes plus unamortised hardware |
| The notice period | 30 days is common. If it runs past your cutover you pay twice for a period — which may be the right call, but should be a decision |
| Bundle and hardware effects | Removing one service can reprice the others, and leased handsets usually must be returned or bought out |
Consumer protections in this area were being strengthened during 2026 as the regulator moved to replace the industry code with a directly enforceable standard, including clearer obligations around contract information and switching — covered in what direct regulation of telco rules changes. It does not make a termination charge disappear, but it does mean it is entirely reasonable to insist on the numbers in writing, quickly.
Failure 6: The Friday
The cheapest mistake on the list to avoid, because avoiding it costs nothing at all.
Cut over on Tuesday or Wednesday morning. That gives any problem three full business days with contractors reachable and providers staffed. A Friday afternoon cutover hands a silent alarm failure a 65-hour head start and puts you into Monday with a backlog and a weekend of missed calls behind you.
Every provider knows this. Very few clients ask which day is best, and a surprising number push for Friday because it feels lower risk — the reasoning being that the weekend is quiet. The weekend is exactly the problem: quiet means nobody notices, and nobody is available to fix it.
While you are choosing the date, avoid your own peak periods too. End of financial year for accountants, the first week of term for schools, the pre-Christmas run for retail and hospitality. There is no such thing as a good week to have phone trouble, but there are definitely worse ones.
Failures 7 to 9: The Slow Ones
These three do not ruin a day. They quietly degrade a business for months, which in aggregate is often more expensive.
7 · Rules nobody wrote down
The old system had time-of-day routing, overflow rules, a holiday message, and a rule sending one client's calls straight to a particular person. Nobody documented any of it. The new system is built to what people remember, and calls go to the wrong place for months before someone notices.
8 · Staff never shown
Twenty minutes of training would have covered transfers, voicemail, the app and the queue. Without it, people invent workarounds — writing down mobile numbers, taking calls on personal phones — and those workarounds become permanent within a fortnight.
9 · Old service killed too early
Cancelled the week after cutover to save a month's rental. Then something turned out to be wrong and there was nothing to fall back to. Keep it alive and idle for a few weeks.
Failure 7 has a specific and easy prevention: before anything is built, screenshot or export every existing rule. Menu structure, hours, holidays, diverts, hunt groups, voicemail boxes and who they belong to. Twenty minutes of capture prevents six months of calls arriving in the wrong place, and it is the artefact you will want anyway the next time anything changes.
Failure 7 also has a detection method worth building in: after cutover, compare call volume against the report from your old provider. If Tuesday used to bring ninety calls and now brings sixty, something is not arriving. Get that report before you give notice — it is much harder to obtain afterwards.
How Number Portability Actually Works
Worth understanding properly, because it is the mechanism behind failures 1, 3 and 4.
Your number is not your provider's property. It is allocated under national numbering arrangements and is portable between providers. The movement runs under an industry Local Number Portability framework that defines the procedures between providers, including standard hours of operation and activation timeframes. You sign an authority with the gaining provider; they do the rest.
| Simple port | Complex port | |
|---|---|---|
| What it is | A single standalone number | A number range, multiple services, or legacy technology such as ISDN |
| Timeframe | Days, sometimes same-day | Weeks — plan on several |
| Who is in it | Small businesses with one line | Most businesses with a main number plus direct numbers, whether they think so or not |
1300 and 1800 numbers are different again. They are inbound services rather than geographic numbers, they move by a different path, and they should be run as a separate workstream from day one. There is a real upside to this: where an inbound number terminates is a configuration setting, so it can be redirected quickly once the new service is proven. If your advertised number is a 1300, you have a fast, reversible safety net that a business advertising a geographic number does not — point it at the old service through cutover, then move it in one change when you are satisfied. Background in the 1300 and 1800 number guide.
The Prevention Checklist
One page, mapped to the nine failures. If this is the only thing that survives from this article, it is enough.
| Do this | Prevents | When |
|---|---|---|
| Email everyone: agree to no cancellation from the current provider, forward all such calls | 1, 9 | Before anything starts |
| Walk every building; list every device on a phone socket; get contractor lead times | 2 | Week 1 |
| Ask your current provider, in writing, for the exact legal entity name on the account | 3 | Week 1 |
| Confirm whether the whole number range must move | 4 | Week 1 |
| Get end date, termination charge, notice period and bundle effects in writing, per service | 5 | Week 1 |
| Obtain a call volume report from the current provider | 7 | Before giving notice |
| Screenshot or export every existing routing rule, menu, divert and voicemail box | 7 | Before the new build |
| Book cutover for a Tuesday or Wednesday morning, outside your peak season | 6 | When dates are set |
| Twenty minutes of training for everyone who answers a phone | 8 | Week before cutover |
| Written signal test for every monitored device after cutover | 2 | Day after |
| Compare a week of call volume against the old report before closing anything | 7, 9 | Week after |
9
Failure modes
1
That is irreversible
0
That are technical
Tue
The correct day
The encouraging conclusion: none of this requires technical knowledge. It requires someone to walk a building, send an email, ask for four numbers in writing, and pick a Tuesday. Businesses that do those four things have changeovers nobody talks about afterwards, which is the entire objective.
If you are still at the choosing stage rather than the moving stage, the comparison of business phone systems and what a phone system actually costs cover that, and zero-touch handset provisioning covers why the desk phone part is usually the least eventful step in the whole project.
Frequently Asked Questions
Can I lose my business phone number when switching providers?
There is exactly one way, and it is the most important thing on this page. To move a number you sign an authority and the new provider arranges everything with the old one — you never contact the losing provider and you never cancel anything. What goes wrong is that the losing provider rings the business, often reaching someone in accounts with no involvement in the project, and asks whether they would like to close the account. The person says yes because that seems like the tidy answer. Cancelling the service releases the number, a released number goes into quarantine, and at that point it is no longer yours. There is no appeal, no escalation and no technical fix — the number on your vehicles, your signage and fifteen years of search results is simply gone. The prevention takes ninety seconds: email everyone who might take a call from your current provider and tell them that if that provider contacts them about closing, cancelling or disconnecting anything, the answer is no and the call should be forwarded to you, including anything described as routine. The people who cause this failure are invariably trying to be helpful.
What actually breaks during a phone changeover?
Almost never the phones. What breaks is everything else sharing those lines, and the dangerous property they share is that they fail silently — the device continues to look completely normal at your end while nothing arrives at the other. A back-to-base alarm arms, beeps and lights up as usual while the monitoring centre receives nothing, and this is discovered during a break-in. A medical alert pendant behaves identically. A fire panel appears healthy while not reporting, which is a compliance and insurance problem as well as a safety one. A lift emergency phone gives no visible sign at all until someone presses the button in a stuck lift. EFTPOS on a line at least announces itself by declining. Gate and door intercoms stop letting visitors in, always at the worst moment. Fax appears to send and does not arrive, and it is still genuinely used in legal, medical and freight. The prevention is to walk every building with your feet rather than working from a list, list everything plugged into a phone socket including in ceiling spaces and lift motor rooms, identify the separate contractor for each, contact them before choosing a cutover date because their lead times set your date, and get a written signal test per device afterwards.
Why do port requests get rejected?
Most commonly on a legal entity mismatch. The port authority has to match the losing provider's records exactly — legal entity name, address and account number as they hold them, not as you would naturally write them today. A trading name where the records show the company entity is the single most frequent cause. The fix is to ask your current provider, in writing, for the exact name the account is held in, before you lodge anything. The second cause is the number range: if you hold a block of numbers, taking part of it and leaving the rest is often not possible, so a business planning to move its main number and a few directs while leaving the rest behind can find the whole plan has to be rebuilt. Confirm the scope of the range in the first week, before dates are set or announced to anyone. Both problems are absorbed by the same discipline — lodge early enough to survive one rejection. A port with four weeks of slack survives a name mismatch without drama, whereas one lodged with three days to spare does not, and if a product retirement date is driving the timing there is no slack available later.
Does porting my number end my contract with the old provider?
No, and this is the most common financial surprise in a changeover. Porting moves the number; the contract and any early termination charge continue to exist until they are separately dealt with. Compounding it, most businesses do not have one contract — they have several services signed at different times with different end dates, typically lines, internet and mobiles. Before committing to anything, get four things in writing for each service: the contract end date, the early termination charge, the notice period, and any bundling or hardware effects. Termination charges are usually the remaining months of the service charge and sometimes unamortised hardware. Thirty days notice is common, and if it runs past your intended cutover you will pay for both services for a period, which is often the right decision but should be a choice rather than a discovery. Removing one service from a bundle can reprice the others, and leased handsets generally have to be returned or bought out. Consumer protections in this area were strengthened during 2026 as the regulator moved to replace the industry code with a directly enforceable standard, which does not make a charge disappear but does make it entirely reasonable to insist on the figures quickly and in writing.
When is the best day to cut over?
Tuesday or Wednesday morning, and this is the cheapest mistake on the whole list to avoid because changing the date costs nothing. It gives any problem three full business days with contractors reachable and providers properly staffed. A Friday afternoon cutover hands a silent alarm failure a 65-hour head start and delivers you into Monday with a weekend of missed calls behind you. Every provider knows this and very few clients ask, and a surprising number actively push for Friday on the reasoning that the weekend is quiet — but quiet is exactly the problem, because it means nobody notices and nobody is available to fix it. While choosing the date, also avoid your own peak periods: end of financial year for accountants, the first week of term for schools, the pre-Christmas run for retail and hospitality. There is no good week to have phone trouble but there are definitely worse ones.
How do 1300 and 1800 numbers fit into a changeover?
They are inbound services rather than geographic numbers, they move by a different path, and they should be run as a separate workstream from day one rather than assumed to ride along with your landline numbers. There is a significant upside to that difference. Where an inbound number terminates is a configuration setting rather than physical wiring, so it can be redirected quickly once the new service is proven. That gives you a fast, reversible safety net: point the advertised 1300 number at the old service through cutover, satisfy yourself the new arrangement is working, then move it in a single change. A business whose advertised contact number is a 1300 has materially lower changeover risk than one advertising a geographic number. Two things to handle deliberately: the routing rules that travel with the number — state-based routing, time-of-day rules, overflow behaviour — need documenting before anything changes because nobody remembers them afterwards, and memorable or word-based smart numbers may sit under separate arrangements, so check ownership and rights of use early rather than at cutover.
What are the slow failures that do not show up on cutover day?
Three, and in aggregate they often cost more than the dramatic ones. The first is routing rules nobody wrote down: the old system had time-of-day routing, overflow rules, a holiday message and a rule sending one particular client straight through to a specific person, none of it documented, so the new system gets built to what people remember and calls go to the wrong place for months. Prevent it by screenshotting or exporting every existing rule, menu, divert, hunt group and voicemail box before anything new is built — twenty minutes of capture, and it is the artefact you will want next time anything changes anyway. Detect it by comparing a week of call volume against a report from the old provider; if Tuesday used to bring ninety calls and now brings sixty, something is not arriving. Get that report before you give notice, because it is much harder to obtain afterwards. The second is staff never being shown the system — twenty minutes covering transfers, voicemail, the app and the queue prevents workarounds like writing down mobile numbers and taking calls on personal phones, which harden into permanent habits within a fortnight. The third is cancelling the old service too early to save a month's rental, leaving nothing to fall back on. Keep it alive but idle for a few weeks; it is the cheapest insurance in the project.
