What Actually Happened in 2026
A short, factual map. Figures reported publicly and worth checking against your own notices, because reported numbers for the same transaction sometimes differ depending on what is being counted.
| Event | What was reported | Who it touches |
|---|---|---|
| Aussie Broadband acquires AGL's telco business | Announced February 2026, consideration reported as around $115 million in new shares, completed mid-2026. Reported service counts vary with what is included — around 218,000 services in the announcement, with reporting of roughly 350,000 broadband and mobile connections across AGL and Southern Phone and about 46,000 voice services. Customers were moved onto the acquirer's network from July 2026, with migration expected to complete around the end of August. AGL continues to market telco products under its own brand, with the acquirer supplying the service. Southern Phone continues as a standalone brand. | Small business and residential customers of AGL and Southern Phone, including voice services. |
| Vocus acquires TPG's enterprise, government and wholesale business | A binding agreement entered in October 2024 with a reported transaction value in the billions, cleared by the ACCC and subsequently given government approval, including TPG's residential wholesale broadband business. | Enterprise, government and wholesale customers, and any business buying services that ride on those fibre assets. |
| Mid-tier takeover activity | Including a reported takeover offer of around $467 million by Aussie Broadband for Superloop, alongside earlier acquisitions of smaller brands and the retirement of others. | Customers of mid-sized and challenger providers, where ownership can change more than once in a few years. |
| Optus Loop replaced by a RingCentral-built platform | A small-business voice product being rebuilt on a partner's technology, with customers moved to the new platform. | Small and medium business voice customers. Covered in the Optus Loop migration piece. |
| Telstra small business product retirements | A set of legacy small-business voice products with published stop-sell and end-of-service dates, sourced from industry reporting and integrator communications rather than one consolidated release. | Anyone still on a legacy Telstra small business voice product. Dates and caveats in the retirement dates article. |
| 3CX licensing and support changes | Commercial terms altering for customers and partners without any change to the technology itself. | Businesses running 3CX, and the partners who support them. See the 3CX partner analysis. |
On the reported figures
You will see different service counts for the same deal in different places, and both are usually correct — one counts the services in the transaction perimeter, another counts total connections including brands acquired earlier. Do not use a media figure to work out what applies to you. Your own account notice is the only document that tells you which services and which dates are yours, and it is the one to file rather than the press release.
Four Events, One Email
This is the distinction that determines everything you should do. Work out which one you have.
| What is actually happening | Technical risk to you | What it requires | |
|---|---|---|---|
| 1. Acquisition | Somebody bought your provider. The service, the platform and the network are unchanged on day one. | Low, immediately. The risks are commercial and arrive later. | File the notice. Diarise your renewal. Verify number registration once. |
| 2. Platform migration | Your service is being moved onto different technology, possibly a different network, possibly a different vendor's software. | High. Call quality, features, admin interface, integrations and recordings can all change, and some will. | Active work. Test before and after. Export first. Do not assume feature parity. |
| 3. Product retirement | What you are on is being switched off on published dates. Stop-sell first, end of service later. | High, with a hard deadline. Doing nothing eventually means no service. | A decision and a project, sequenced to the published end-of-service date. |
| 4. Commercial or licensing change | Terms, pricing, licensing model or support arrangements change. Nothing technical happens. | None technically. Substantial commercially. | Read the new terms and re-run the arithmetic. Nothing needs installing. |
The trap is that events combine
An acquisition is frequently followed, twelve to twenty-four months later, by a platform migration — because consolidating platforms is a large part of why the acquisition made financial sense. So an email that correctly says nothing is changing today is entirely compatible with a migration next year. Treat an acquisition notice as advance warning of a type 2 event rather than as the end of the matter, and use the quiet period to do the preparation that is easy now and awkward under a deadline.
Why Consolidation Is Happening
Not commentary for its own sake — the drivers tell you what to expect next, which is the practically useful part.
Thin margins on resale
Reselling a wholesale service on price is a difficult business, and scale is one of the few defences. That pushes the mid-tier towards either acquiring or being acquired, and it is why brands in that band change hands repeatedly.
Infrastructure is where the value sits
Fibre, spectrum and data centres are durable assets; a customer base on somebody else's network is not. Hence enterprise fibre and wholesale assets moving between carriers rather than staying put.
Adjacent industries exiting
Energy retailers and others that added telco as a bundling play have been reassessing whether they want to operate one. That produces clean sales of customer bases, and it is why your provider can change without your service changing.
Platform costs favour one platform
Running two voice platforms costs roughly twice as much as running one and delivers no more revenue. Every acquisition therefore contains an implicit future migration, whether or not it has been announced.
What follows from those four: expect more mid-tier consolidation, expect platform rationalisation to follow acquisitions by a year or two, and expect legacy products to keep being retired. None of that is alarming — but it does mean the question "who will operate my phone service in three years, and on what" deserves an answer at purchase time rather than at notification time.
What Survives a Change of Ownership
General principles, and your own contract governs. Read it rather than relying on a summary, including this one.
| Item | Usual position | What to verify |
|---|---|---|
| Your contract | Transfers with the business. Assignment or novation clauses are standard in supply agreements, and the acquirer generally steps into the seller's position. | Whether there is a change-of-control clause, and whether it gives you any right — sometimes there is a termination right that is worth knowing about while it is live. |
| Your term and pricing | Continue to the end of the current term. | The exact end date, the notice period, and whether the term auto-renews. Auto-renewal after an acquisition is how businesses end up locked into a platform they did not choose. |
| Your numbers | Stay yours if the rights of use are recorded in your name. Otherwise they move with the provider's asset base. | The registration itself, in writing. This is the single highest-value verification in this article. |
| Consumer protections | Regulatory obligations attach to the carriage service provider, so they follow the service to the new owner. | Nothing much, though it is worth knowing that a complaint escalation path exists regardless of who owns the company. |
| Your service levels | Whatever is written in the agreement continues to apply. | Whether they were ever written down. Many small-business services have no contractual service level at all, in which case there is nothing to inherit. |
What Changes in Practice
The contract can survive intact while the experience changes considerably. These are the things customers actually notice, in the order they tend to notice them.
| What changes | Typical timeline | What to do about it |
|---|---|---|
| Support — different queue, different people, different hours, different escalation. | Weeks to months. | Get the new escalation path in writing and test it once with a low-stakes ticket. Do not discover it during an outage. |
| Your account manager | Often immediately. | Ask who owns the account now. An unowned account is one that gets a default renewal offer rather than a negotiated one. |
| The roadmap | Three to twelve months. | Ask directly which platform is strategic and which is being maintained. You are entitled to ask, and the answer shapes your planning. |
| Integrations | At migration. | List every integration you rely on — CRM, practice software, dialler, reporting — and get each confirmed on the destination platform by name. |
| Price | At renewal. | This is where the commercial effect of consolidation lands. Diarise renewal minus 90 days and treat it as a decision point rather than an administrative event. |
| The platform itself | Twelve to twenty-four months, frequently. | Everything in the migration section below. |
One thing worth saying in fairness: consolidation is not automatically bad for customers. A larger acquirer can bring better-funded support, a more capable platform, national coverage a small provider could not offer, and investment a struggling business could not fund. Several of 2026's transactions plausibly improve things for the customers involved. The problem is not the direction of change — it is being passive through it, because passivity is what turns a neutral event into an unfavourable renewal.
Platform Migrations: The Risky One
Of the four events, this is the one that can genuinely damage your operations, because your service is being rebuilt on different technology and something almost always differs.
| What to check | Why it bites |
|---|---|
| Feature parity, itemised | "All your features are supported" is a summary, not a list. Write out your own list — queues, hunt groups, after-hours rules, call recording, voicemail-to-email, paging, hot-desking, presence, wallboards — and get each one confirmed individually. |
| Call recordings and history | Frequently the biggest loss. Recordings may not migrate at all, and call history often does not. If you have retention obligations, this is a compliance matter rather than a convenience one. Export before, not after. |
| Handsets | Some handsets do not carry across, or require reprovisioning that resets local settings. Ask for a supported-model list against your actual inventory. See which SIP handsets are supported where. |
| Numbers and presentation | Confirm each number arrives and presents correctly outbound. A migration is a common cause of calls suddenly presenting the wrong CLI, which then fails silently on some networks — see why calls get blocked or flagged. |
| Emergency call addresses | Address records do not always carry across cleanly. Verify per site, per number, after migration. This is the check with the worst consequences if skipped. |
| The continuity path | Your diversion rules for an internet or power outage are configuration, and configuration is what migrations lose. Re-test after cutover rather than assuming. |
| Admin access | New interface, new permissions, sometimes fewer of them. Confirm you can still make the changes you currently make yourself. |
The sequencing rule for a migration you did not choose
Export everything you can before the cutover date, not after. Recordings, call history, contact directories, and a written record of your configuration — hours, queues, routing, greetings. Once a legacy platform is decommissioned, "can you retrieve that for us" stops having a good answer, and nobody is being obstructive; the system is simply gone. An afternoon of exporting is the cheapest insurance in this entire article.
Product Retirements: The Deadline One
A retirement is the easiest of the four to plan for and the most expensive to ignore, because the date is published and does not move for you.
| Stage | What it means | What to do |
|---|---|---|
| Closed to new customers | Existing services continue. Nothing changes for you yet. | Note it. A product closed to new customers is a product with a finite life, whatever the current messaging says. |
| Stop-sell | No new services or, often, no changes to existing ones. This is where it starts to hurt operationally — you may not be able to add a line or a site. | Start the replacement decision now. Being unable to add capacity is a business constraint, not just a technical one. |
| End of service | The service stops. | Be off it well before, with numbers ported and tested. Work backwards from the date with real lead times, and add margin. |
The lesson from the ISDN wind-down is worth carrying: Telstra ISDN ceased sale in June 2018, disconnections began in September 2019, and it was fully decommissioned by 31 May 2022. Businesses that planned early moved on their own terms and their own budget cycle. Businesses that waited moved in the last few months, at whatever price and lead time were available. The dynamics are identical every time.
The Number Risk
Of the three real risks, this is the one that can be irreversible, and it is the one nobody checks until it matters.
Australian numbers are administered under a national framework: providers hold rights of use over ranges and allocate numbers from them to customers. Whoever is recorded as holding the rights over a number decides its fate. A business can advertise a number for a decade, pay for it monthly, print it on vehicles and signage, and still find that the registration sits with the provider.
| Situation | Why an acquisition makes it worse |
|---|---|
| Numbers registered to the provider rather than you | They form part of the asset base being transferred, and your ability to leave depends on the new owner's policy rather than on your contract. |
| Numbers registered to an entity that no longer trades | Common after your own restructures and acquisitions. A port then needs authority from a company that cannot give it, and untangling that takes months you will not have under a retirement deadline. |
| 1300 and 1800 numbers | These carry their own arrangements and are frequently the most valuable numbers a business has, because they are the ones in every advertisement. See who owns your 1300 number. |
Two sentences to send this week
"Please confirm in writing that the rights of use for the numbers on our account are registered in our business name." And: "Please confirm that on written request you will port these numbers to another provider." Send it whether or not anything is currently changing. The answer takes a provider minutes and it determines whether every other decision you make about your phone service is reversible.
The Configuration Risk
Your dial plan is a business process that happens to live inside a vendor's software: which numbers ring where, what happens at 5:31pm, who covers the on-call phone at Easter, the escalation after three rings, the queue that goes to a mobile after ninety seconds. It was built up over years by several people, most of whom have left, and it exists nowhere else.
A migration or a retirement threatens it in a way nobody plans for, because it is not perceived as an asset. Write it down — two pages is usually enough — covering numbers and where each terminates, hours and holiday behaviour, queues and their overflow rules, greetings and who recorded them, after-hours and on-call paths, and every integration by name. That document is what turns a rebuild from a discovery exercise into a configuration task, and it is useful even if nothing ever changes.
The Renewal Risk
This is where consolidation actually reaches most customers, and it is the quietest of the three.
| The pattern | What to do instead |
|---|---|
| An acquisition notice says nothing is changing, so the account is not reviewed. | Diarise renewal minus 90 days on receipt of the notice. The notice is the trigger for the review, not a reason to skip it. |
| The account has no owner during integration, so renewal arrives as a default offer. | Ask who owns the account and get a name. Unowned accounts get list pricing. |
| Auto-renewal rolls the term before anyone looks. | Find the auto-renewal clause and the notice period today. This is the single most common way businesses become locked to a platform they did not choose. |
| Market pricing has moved and nobody tested it. | Get one comparison quote at renewal. Not necessarily to move — to know. A provider who values the account will respond to a real alternative. |
The Ninety-Day Checklist
Run this whichever of the four events you have received. Most of it is an afternoon's work and all of it is useful regardless.
| Week | Task |
|---|---|
| Week 1 | Identify which of the four events this is, from the notice itself rather than from media coverage. Find and read the actual contract — term end date, notice period, auto-renewal, change-of-control and assignment clauses. |
| Week 1 | Send the two number-registration sentences above and get written answers. This is the highest-value item on the list. |
| Week 2 | Export what exists: call recordings within your retention requirement, call history, contact directories. Store it somewhere that is not the platform. |
| Week 2 | Write the two-page configuration record. Numbers, hours, queues, overflow, greetings, after-hours, integrations by name. |
| Week 3 | Get the new support and escalation path in writing, and test it once with a low-stakes ticket to see what actually happens. |
| Week 3 | Ask the roadmap question plainly: is this platform strategic, and if a migration is planned, when and to what? A straight answer is valuable and so is an evasive one. |
| Week 4 | Verify emergency service addresses per site and per number. Do it again after any migration. |
| Week 4 | Diarise renewal minus 90 days, with a named owner. |
| Weeks 5–8 | If a migration is coming: build the itemised feature list and get each item confirmed. Confirm handset models. Confirm integrations by name. |
| Weeks 9–12 | Get one comparison quote so you know the market. Then decide deliberately: stay, migrate, or move. |
When to Stay, When to Move
Staying is frequently the right answer and this article is not an argument for churn. The question is whether you are choosing it.
| Reasonable to stay when | Worth moving when |
|---|---|
| The acquirer is investing in the platform you are on, and says so specifically. | Your platform is being maintained rather than developed, and nobody will say what happens after the current term. |
| Your numbers are properly registered to you, so the decision stays reversible. | Your numbers are not registered to you and the provider will not confirm portability in writing. |
| Support has held up, and the escalation path you tested worked. | Support degraded through the integration and has not recovered after two quarters. |
| The migration was completed with real feature parity and your integrations still work. | The migration lost features or integrations you depend on and there is no committed date to restore them. |
| Renewal pricing is competitive when actually tested against the market. | Renewal pricing has moved materially with no corresponding change in what you receive. |
| You have been through one migration and would rather not do two. | You are facing a second migration in three years, in which case moving once to somewhere stable is the smaller disruption. |
The mechanics of moving, if you decide to, are in changing provider without losing calls and the porting guide.
Where We Sit in This
It would be convenient to present ourselves as immune to a market-wide trend, which nobody is. What we can describe is our position and what we will put in writing.
We are Australian owned, and we operate our own network and platform rather than reselling somebody else's — which is the difference between a fault we can investigate and a fault we can only escalate. Numbers we allocate are registered with rights of use in your name, and we will confirm that in writing and confirm that we will port them out on written request. There is no separate legacy platform we are quietly maintaining while we develop something else, because there is one platform. And we will tell you, if you ask, which components in an AI or integration path are not ours — the distinction we set out in not all providers are equal.
What we will not claim is that ownership structures never change or that scale is inherently virtuous. The useful position for a customer is not to find a provider who promises permanence. It is to hold the two things that make any change survivable: numbers registered in your own name, and a written record of your own configuration. With those, a migration email is an administrative task. Without them, it is a negotiation from a weak position.
The summary
Four different events arrive as the same reassuring email. An acquisition changes ownership and little else immediately; a platform migration rebuilds your service on different technology and carries the real operational risk; a product retirement has a published deadline that does not move; a licensing change alters terms with no technical work at all. Contracts, terms and pricing usually survive an acquisition; support, roadmap, integrations and renewal pricing usually do not. Expect a migration to follow an acquisition by a year or two, because platform consolidation is generally part of the rationale. Three risks matter: numbers not registered in your name, configuration that exists only inside the platform being replaced, and a renewal accepted by inertia. Fix all three in an afternoon: get number registration confirmed in writing, export your recordings and history, write two pages describing your configuration, and diarise renewal minus ninety days.
Related reading: the Optus Loop migration, Telstra small business retirement dates, changing provider without losing calls, who owns your 1300 number, and the money side of Australian telco.