The Moat Nobody Talks About
Ask a hundred Australian businesses why they have not changed phone provider and you will get two answers. A few will say the price is fine. Almost all of the rest will say some version of: because I do not want to deal with it.
That is not laziness. It is a rational assessment of a real cost. Changing phone system means every person learns new software, every handset gets re-provisioned, every call flow gets rebuilt, the CRM connection gets redone, and there is a morning where the phones might not work properly. None of that appears on a quote, and all of it is real.
Switching cost is the moat around every incumbent phone provider in Australia. It is worth more to them than any feature on their website — and it is the reason your renewal letter is written the way it is.
Here is the thing worth understanding about your current position. That moat is not being defended right now. It is being drained, by the incumbent, on purpose, for their own reasons.
The whole argument, in one paragraph
You are going to pay the switching cost this quarter. New app, new logins, re-provisioned handsets, rebuilt call flows, a cutover morning — you pay all of it whether you stay on the new platform or move to a different provider entirely. The disruption is fixed. Only the destination is variable. Which means the extra cost of choosing your destination consciously, rather than accepting the one assigned to you, is close to nothing. That is a genuinely unusual position and it is temporary.
What Is Actually Happening
The facts, briefly, because the rest of this page is about what to do with them.
In March 2024 Optus announced it had selected RingCentral to power cloud communications for Australian businesses — reported at the time as RingCentral's first global service provider partnership in the Australian market. The resulting product is branded Optus Loop with RingCentral. Optus now runs a dedicated support hub for it, together with a notice headed Optus Loop System Upgrade and a page headed Updated Loop migration information, plus how-to articles on signing in, the new app, call forwarding and work schedules. Existing Loop customers are being migrated across.
One thing we will not do is invent a date
At the time of writing we could not verify a single published switch-off date for the legacy platform applying to every customer, and migrations at this scale are normally run in waves with individual windows. Your date is the one in your own migration notice. If you have not got it in writing — with your wave, your cutover window and a named contact — that is the first phone call to make, ahead of anything else on this page.
It is also worth saying plainly: RingCentral is a large, capable platform used by serious businesses in many countries. Nothing here is an argument that the destination is bad. The argument is about who chose it, what it costs you to get there, and what you can extract from the fact that you are being moved.
What a Migration Really Costs You
You cannot make a good decision without a number, and the number is almost never on the invoice. Here is a model for a fifteen-person business with two sites. Adjust the rates to your own; the structure is what matters.
| Line item | Realistic effort | Who absorbs it |
|---|---|---|
| Staff learning the new app | 1–2 hours each, plus a week of slower handling | Everyone. This is usually the biggest line and it never gets counted |
| Handset re-provisioning | 15–30 minutes per device, more if any need replacing | Whoever is nominated, usually the office manager |
| Rebuilding call flows and menus | Half a day to two days depending on complexity | One person, under time pressure, from memory |
| Re-recording greetings | Half a day, plus the argument about who records them | Reception, again |
| Reconnecting CRM and integrations | Two hours to a day per integration, including testing | IT, or nobody, which is worse |
| Exporting recordings and history | A few hours, and it must happen before cutover | Whoever remembers. Frequently nobody |
| Cutover day | Half a day of attention, plus the risk of missed calls | The business, in revenue terms |
| The fortnight afterwards | Small fixes, forgotten paths, one thing that never worked properly again | Everyone, gradually |
8
Cost lines, one on the invoice
100%
Incurred either way
1
Variable: the destination
0
Extra cost to choose it
Put a dollar figure on that for your business. Whatever it comes to, write it down — and then note that the figure is identical in both columns of your decision. The only line that differs between staying and moving is porting your numbers, which is a standardised industry process your incoming provider runs for you, and which we cover further down.
The mistake to avoid
Do not compare “the hassle of moving providers” against “doing nothing”. Doing nothing is not on the menu. The comparison that reflects reality is “the hassle of migrating to a platform someone chose for me” against “the same hassle, to a platform I chose”. Framed correctly, most businesses reach a different answer than they do when they frame it as effort versus inertia.
The Four-Question Test
Four questions, answered honestly, will tell you which of the three doors to walk through. There is no scoring system; if two or more answers are unhappy ones, that is your signal.
1. In the last two years, how has support actually gone?
Not the marketing promise — your real experience. How long did it take to get a person, and did that person fix it or pass it on? This is the question people most often talk themselves out of. If support has been a source of frustration, note that a migration period is when support queues are at their longest, so the coming months will be the worst version of it, not the best.
2. What does the first renewal after migration cost?
Migration pricing is often attractive, because migration is exactly when customers leave. The renewal after it is where the economics get recovered. Ask for a number or a cap in writing. “It will be reviewed” is a price rise wearing a nicer jumper.
3. Are you paying for capability you never use — or missing capability you need?
Both are common and both are worth money. List what you actually use in a week. Then list the three things you have wanted and not had — AI answering after hours, business SMS from the main number, call recording, a report that tells you how many calls you missed. Most businesses find at least one of those is included elsewhere and tiered where they are.
4. When something breaks, how many companies are involved?
If your network comes from one company and your phone platform from another, a fault that sits between them sits between two vendors. You have possibly already experienced that conversation. It is the single most predictable source of long outages in business telephony, and it is structural rather than anyone's fault.
A fifth question, if you run anything time-critical
Where is your data stored and processed, and where do the people who support you sit? This is a fair question to ask any provider, and a reasonable one to weigh — particularly if you handle health information, financial records or NDIS participant data and have obligations about where personal information goes.
If You Stay: What to Demand
Staying can be the right answer. If it is yours, do not stay passively — a migration is the moment your leverage peaks, and leverage that goes unused simply expires.
- The migration work done for you, not by you. Call flows rebuilt, handsets re-provisioned, integrations reconnected, by their engineers, verified by you. If that is chargeable, get the charge in writing now rather than discovering it later.
- No contract reset. A migration you did not ask for should not restart your term. If it does, that is a material change and you should treat it as one.
- A capped first renewal. A number, or a percentage ceiling, in writing. This is the single most valuable concession available and the one least often requested.
- Your cutover date moved off your peak. Nobody should be cutting over the week before their busiest trading period. Ask for a date and hold them to it in writing.
- Named support contact for the migration window. Not a queue. A person, or at minimum a reference and a priority path for the first fortnight.
- Written confirmation on recordings and history. What is exported, in what format, by when. Then export it yourself anyway.
- Two named administrators on the new account. Single-person access is how a two-hour problem becomes a two-day problem, and it always happens while that person is on leave.
If a provider will not put any of the first three in writing, that is information. It does not mean you should leave — it means you now know how the relationship works, which is exactly what you were trying to find out.
If You Move: The Fortnight Plan
Moving is not harder than migrating. It is the same work with a different logo at the end and one extra process — the port — which your new provider runs. Here is how a fortnight actually looks.
| When | What happens | Your part |
|---|---|---|
| Days 1–2 | Inventory. Every number you hold — main lines, direct dials, 1300/1800, fax, alarm and lift lines. Every handset model. Every integration | The one task nobody can do for you. Two hours, and it prevents most of what goes wrong later |
| Days 2–3 | Exports. Call recordings, call history, voicemail greetings, twelve months of reporting | Do this before anything else changes. It is the asset most commonly lost |
| Days 3–5 | Design. Your call flows drawn out: 9am, 1pm Saturday, Christmas Day, after hours, overflow | Half an hour with whoever actually answers the phone. They know things the diagram does not |
| Days 5–8 | Build and test in parallel. The new system is configured and tested while the old one still runs | Test on your mobile. Ring every path. Use the written script |
| Days 8–10 | Port lodged. Authority signed, account name matched exactly, full number list attached | Sign, and make sure the account name matches the bill character for character |
| Day 12–14 | Cutover, at a scheduled time you choose. Minutes, not days | Be there. Ring every number afterwards. Verify the Triple Zero address per site |
| Week 3 | Snag list. The path nobody thought of, the one greeting that is wrong | Keep a list rather than reporting things one at a time |
The part that surprises people
The new system is built and fully tested before anything is switched. You are not moving into a building site. On cutover day the only thing that changes is which platform the numbers point at — everything behind it has already been running and tested for a week. That is why a well-run cutover is measured in minutes and why choosing the time of day is genuinely yours.
The Numbers Question
The fear that stops most businesses is losing the number that is on the vehicles, the website, the invoices and fifteen years of directory listings. It is worth knowing exactly how much weight that fear deserves, which is: not much.
Porting in Australia runs on an industry framework — the Local Number Portability arrangements set out in the Communications Alliance C540 code, which has governed how providers exchange porting requests since the late 1990s and sets standard hours and activation timeframes. Practically:
| The worry | The reality |
|---|---|
| They can refuse to release my number | No. A losing provider cannot refuse simply because it would prefer to keep you |
| I will be off the air for days | A simple port completes in a defined window and the cutover is minutes, at a time you choose |
| I have to run the paperwork | Your incoming provider raises and manages the port. You sign an authority and supply a recent bill |
| My 1300 is a special case | Inbound numbers port too, and are usually simpler than a large range of direct dials |
| My setup is too complex | Complex ports take longer and need more planning. That is a scheduling fact, not a barrier |
Two things genuinely cause delay: an account name that does not exactly match the porting authority, and an incomplete number list. Both are prevented by the day-one inventory. What actually goes wrong when businesses switch providers covers the rest of the failure modes in detail.
Making Sure This Cannot Happen Again
Step back from this particular migration and look at the mechanism, because the mechanism is general and it will produce another migration notice for someone within a year or two.
When a provider resells a platform built by another company, three things are true, and none of them are anybody's fault:
The roadmap belongs elsewhere
Features arrive, change or are retired on a schedule set by the platform owner. Your provider can ask; it cannot decide. That is why a feature request into a reseller so reliably goes nowhere polite.
The platform underneath can change
Commercial arrangements between two companies get renegotiated, and when they do, customers move. Not because anything was failing — because a contract upstream changed. That is exactly what a Loop customer is living through.
Faults land on a seam
When the network is one company and the platform is another, a problem between them is a problem between two companies. Every business that has waited while two vendors establish whose fault it is knows how long that takes.
The alternative is not a bigger brand. It is a provider that owns and operates what it sells — its own network and its own platform — so the roadmap, the fault resolution and the commercial relationship sit in one place. That is the substance behind owning the network, and it is the specific reason some businesses received a migration notice this year and others did not.
A migration notice is not a service failure. It is a governance outcome. The question worth asking is not “was my service good?” but “who is able to make this decision about my business, and did I mean to give them that power?”
What to Do This Week
Three actions, in order, none of which takes long.
- Get your migration notice in writing — wave, cutover date, window, named contact. If you cannot find one, ring and ask. Everything else depends on knowing your date.
- Do the inventory and the exports. Numbers, handsets, integrations, recordings, greetings, twelve months of reporting. You need all of it regardless of what you decide, so it is never wasted work.
- Get one comparison quote while the disruption is already sunk. Twenty minutes. Either it confirms staying is right — which is a useful thing to know rather than assume — or it does not, and you found out during the only window when acting on it is cheap.
The one sentence to take away
You are paying the switching cost this quarter either way. The only thing still under your control is where you land — and that control expires on your cutover date, quietly, without anyone telling you it has gone.
If you want the wider view before deciding, the 2026 comparison of Australian business phone systems is the neutral starting point, and how the big international platforms compare locally covers the destination you are being pointed at.
Frequently Asked Questions
What is happening to Optus Loop customers?
Optus Loop customers are being migrated onto a platform built by RingCentral and branded Optus Loop with RingCentral. Optus announced in March 2024 that it had selected RingCentral to power cloud communications for Australian businesses, reported at the time as RingCentral's first global service provider partnership in the Australian market, and it now runs a dedicated support hub for the new product alongside a notice headed Optus Loop System Upgrade and a page headed Updated Loop migration information. For a customer that means a different desktop and mobile app, new logins, a new administrator console, handsets that need re-provisioning, call flows and menus that must exist again on the new platform, and integrations that need reconnecting and re-testing. At the time of writing we could not verify a single published switch-off date for the legacy platform applying to every customer, and migrations of this scale are normally run in waves with individual windows, so the date that matters is the one in your own migration notice. If you have not received it in writing with your wave, cutover window and a named contact, that is the first call to make.
Should I stay with Optus or move to another provider?
Both are defensible and the decision turns on four questions. First, how has support actually gone over the last two years — not the promise, your real experience of how long it took to reach a person and whether that person fixed it. Second, what does the first renewal after the migration cost, as a number or a cap in writing, because migration pricing is often attractive precisely because migration is when customers leave, and the renewal afterwards is where the economics are recovered. Third, are you paying for capability you never use, or missing capability you need — list what you actually use in a week, then list the three things you have wanted and not had, because most businesses find at least one of those is standard elsewhere and tiered where they are. Fourth, when something breaks, how many companies are involved, because a fault sitting between a network provider and a separate platform provider sits between two vendors and that is the most predictable cause of long outages in business telephony. If two or more of those answers are unhappy ones, the market review is worth doing properly.
How much does changing business phone system actually cost?
Almost none of it appears on the invoice, which is why it is so consistently underestimated. The real lines are: staff learning the new app, at one to two hours each plus a week of slower call handling, which is usually the largest cost and almost never counted; handset re-provisioning at roughly fifteen to thirty minutes per device; rebuilding call flows and menus, which runs from half a day to two days depending on complexity; re-recording greetings; reconnecting and re-testing each CRM or app integration, at two hours to a day each; exporting call recordings and history before cutover; the cutover morning itself, including the revenue risk of any missed calls; and a fortnight afterwards of small fixes and forgotten paths. The critical point for a business facing a forced migration is that every one of those lines is incurred whether you stay on the new platform or move to a different provider entirely. The disruption is fixed and only the destination is variable, so the extra cost of choosing your destination deliberately is close to nothing.
What should I demand if I stay through the migration?
Seven things, and the first three are where the value is. Ask for the migration work to be done for you rather than by you — call flows rebuilt, handsets re-provisioned, integrations reconnected by their engineers and verified by you, with any charge stated in writing now rather than discovered later. Ask that your contract term does not reset, because a migration you did not request should not restart your commitment. Ask for a capped first renewal, expressed as a number or a percentage ceiling in writing; this is the single most valuable concession available and the one least often requested. Then ask for your cutover date to be moved off your peak trading period, a named support contact for the migration window rather than a general queue, written confirmation of what happens to your call recordings and call history including format and deadline, and two named administrators on the new account so that single-person access does not turn a two-hour problem into a two-day one. If a provider will not put the first three in writing, that is not necessarily a reason to leave — but it is precise information about how the relationship works.
Will I lose my numbers if I move to a different provider?
No. Porting in Australia runs on an industry framework, the Local Number Portability arrangements set out in the Communications Alliance C540 code, which has governed how providers exchange porting requests since the late 1990s and defines standard hours and activation timeframes. A losing provider cannot refuse to release your number simply because it would prefer to keep your business. Your incoming provider raises and manages the port; your part is signing a porting authority and supplying a recent bill. A simple port completes within a defined window and the cutover itself takes minutes at a scheduled time you choose, not days of downtime. Inbound 1300 and 1800 numbers port as well and are typically simpler than a large range of geographic direct dials. Complex ports involving large ranges, multiple carriers or mixed services take longer and need more planning, but that is a scheduling consideration rather than a barrier. The two things that genuinely cause delay are an account name that does not match the porting authority exactly and an incomplete list of numbers, which is why a full inventory including fax, alarm and lift lines is the first task in any move.
How long does moving to a new phone provider take?
About a fortnight for a typical small or medium business, and the sequence matters more than the total. Days one and two are inventory: every number you hold including main lines, direct dials, 1300 and 1800 numbers and the fax, alarm and lift lines nobody thinks about, plus every handset model and every integration. Days two and three are exports — call recordings, call history, voicemail greetings and twelve months of reporting — done before anything else changes, because history is the asset most commonly lost. Days three to five are design: your call flows drawn out for nine in the morning, one on a Saturday, Christmas Day, after hours and overflow, ideally with whoever actually answers the phone in the room. Days five to eight are build and test running in parallel while your existing service continues untouched. Days eight to ten the port is lodged. Cutover happens around day twelve to fourteen at a time you choose, and takes minutes rather than days because everything behind the numbers has already been built and tested. Week three is the snag list. The important structural point is that you are never moving into a building site — the new system is complete before anything is switched.
Why do resold phone platforms get replaced?
Because of how the commercial arrangement is structured, not because of any failure in the service. When a provider resells a platform built by another company, three consequences follow. The roadmap belongs to the platform owner, so features arrive, change or are retired on a schedule the reselling provider can lobby about but cannot set — which is why feature requests into a reseller so reliably go nowhere. The platform underneath can be swapped when commercial arrangements between the two companies are renegotiated, and when that happens customers are migrated, not because anything was broken but because a contract upstream changed. And faults land on a seam: when the network is one company and the platform is another, a problem that sits between them sits between two companies, and that is the most predictable source of long resolution times in business telephony. A provider that owns and operates both its own network and its own platform has the roadmap, the fault resolution and the commercial relationship in one place. That is the concrete reason some businesses received a migration notice this year and others did not.
