Back to blog

ISP acquisition: how to integrate the inherited CPEs

By IXC ACS Team

Published in November 19, 2026

8 min to read

After an ISP acquisition, the inherited CPE fleet is where integration tends to stall. Learn how to inventory and repoint devices remotely.

Brasil TecPar closed the purchase of Ligga's broadband operation, with more than 350,000 connections in over 400 Brazilian cities, on November 16, 2026, paying R$561.73 million (Brazilian reais) after a price adjustment, according to Teletime. It was the most visible deal in a week when ISP acquisitions dominated Brazil's telecom news. The company has made 60 acquisitions in 31 years, as TeleSíntese reported.

The carrier TIM said it has R$5 billion in cash and has practically finished evaluating several broadband assets. At the other end of the size range, a R$70 million receivables fund (FIDC) for small ISPs, set up by Desenvolve SP, the São Paulo state development agency, together with Möbius, also covers M&A deals. The market is still fragmented, with 10,054 providers reporting a subscriber base in September 2026, according to access data from Anatel, Brazil's telecom regulator.

In our piece on how much an ISP is worth, we covered what buyers look at before signing. This one is about the day after, and in particular the routers and ONUs that came along with the subscriber base, the part of the integration that tends to be underestimated the most.

What should you integrate first after buying an ISP?

The order that usually works is billing and ERP, then customer support, then the network and, last, the CPE fleet, which is where technical integration stalls most often. The savings that justified the price only show up once both operations run as one. As long as the acquired ISP keeps its own NOC, its own support system and its own way of configuring equipment, you are paying for two companies and still managing one more legal entity.

The CPEs almost never get a plan. The buyer learns how big the problem is in the first wave of tickets from the acquired base, when an agent searches for the subscriber's device in the ACS and can't find it, because that router still talks to the previous owner's server, or to no server at all. From then on, even changing a Wi-Fi password means a truck roll.

That's why we argue the fleet survey belongs in due diligence, before signing. Ownership of equipment loaned to subscribers and access to the seller's systems after closing are matters for your legal team, but the list of what to ask for has to come from your technical team.

How do you find out what's in the inherited CPE fleet?

A reliable inventory comes from the devices themselves, because the seller's records usually have wrong models, missing serial numbers and routers swapped in the field that were never logged.

For each group of devices, you need the model with its hardware and firmware versions, where it points and what your ACS can do with it. The ACS address lives in the CPE's ManagementServer.URL parameter, which may hold a domain, a fixed IP or nothing at all if the previous owner never used an ACS.

That last question is the most misleading one. Every CPE pointed at the server shows up with manufacturer, model, serial number and uptime, because that information already comes in the inform. Changing a Wi-Fi password or reading optical power depends on parameters each manufacturer keeps in its own branches of the TR-069 data model. In IXC ACS, the device Capabilities screen shows whether the model has been validated (homologated) for the platform and which functions are available for that firmware version. If an inherited model isn't validated, the request goes to support, as long as one unit is pointed at the ACS and online.

If the base had no ACS, the bulk ACS pointing tool has a discovery mode that scans IP ranges and tests web access credentials without writing anything to the devices. What comes out is already an inventory, with manufacturer, model and the password that opens each one.

Can you switch the acquired base's ACS without truck rolls?

Yes, for most of the fleet, as long as the old ACS is still running when you start. If the devices point to a domain that came under your control in the deal, you only need to point that domain to your server's IP and the fleet comes back on its own, as the server migration guide in the IXC ACS Help Center describes. The expensive case is a fleet pointed at a fixed IP.

In that case the old ACS, while it's still up, can push a new ACS URL to each CPE over TR-069. Use a domain you own, so the next server change is just a DNS update. The change reaches each device at its next inform and anything powered off gets left behind, so this step starts days before the cutover. If the acquired base already ran IXC ACS, IXC Soft's support team handles it with a bulk parameter change. If it ran another tool, the procedure is the same, carried out on the source ACS. This is why access to the seller's server during the transition has to be agreed before closing. If someone shuts down the old ACS the week the deal is signed, every device the network can't reach turns into a truck roll.

Without the old server, or in a base that never had one, bulk pointing is what's left. The ACS logs into each CPE's web interface with a username and password and writes the server URL there, which requires your server to reach the devices over the network and the credentials to actually open the interface. The feature is flagged as beta, so start with a small range. The report separates the devices that were pointed from the ones that failed because of the password, an incompatible model or a timeout, and only that remainder goes to the field team.

How to standardize the acquired base without dropping subscribers

Standardization starts with tagging the devices that came with the acquisition, so you can filter them in any operation and measure that base on its own, without mixing it with yours in the first batch.

Firmware is the scariest part, and for good reason. Bulk firmware update in IXC ACS recommends starting with three devices and stops by itself when failures reach 30% of the batch, for batches of 10 devices or more. None of these safeguards removes the need to check that the image matches the exact model and hardware version, which we covered in our post on bulk ONT firmware updates.

A 90-day plan for the technical integration

The plan counts from the signing date, assumes the seller's ACS stays reachable and should be adjusted to the size of the base.

  • Week 1: confirm access to the seller's ACS and find out which ACS URL most of the fleet uses.
  • Week 1: if the fleet points to a domain, lower the DNS record's TTL and set the cutover date.
  • Month 1: if it points to an IP, repoint the devices to a domain you own, in batches, through the old ACS, tracking which ones were powered off.
  • Month 1: tag the acquired base and run discovery mode on the ranges with no ACS before pointing them in small batches.
  • Month 1: cross-check the real inventory against the ERP records and request validation for the models with volume.
  • Month 3: update firmware by model and hardware version, always starting with three units.
  • Month 3: list what is still unmanaged and use field visits that are already scheduled to replace those devices.
  • Month 3: shut down the old ACS only after the fleet has stabilized on the new one.

Frequently asked questions

Do subscribers lose internet when the fleet moves to a new ACS? No. TR-069 is the CPE's management channel, and subscriber traffic doesn't go through the ACS. During the switch, only remote management of that device is unavailable, until it registers with the new server.

How long does the fleet take to show up in the new ACS? Each device reappears at its next periodic inform. In IXC ACS, with no value configured, the interval is 1,200 seconds (20 minutes), and the recommendation is to wait at least two intervals before concluding something went wrong. A device that is powered off only shows up once it's turned back on.

What should you ask the seller for before signing an ISP purchase? The URL and admin access to the ACS, if there is one, with a commitment to keep it running during the transition, plus control of the domain the devices point to. Also ask for the CPE inventory with serial number, model and firmware, and the web access passwords for the devices. How this goes into the contract is up to your legal team.

What if the inherited model isn't validated for my ACS? It shows up with the basic information from the inform and works for whatever the manufacturer implemented according to the TR-069 standard. For the rest, the validation request goes to support with manufacturer, model, hardware and firmware versions and the serial number of one unit that is pointed at the ACS and online.

Before you sign the next deal

The state of the CPE fleet changes the cost of integration, and that cost can be part of the negotiation. A base pointed by domain, with a reachable ACS and validated models, tends to join your operation within weeks and with few truck rolls. A base pointed by IP, with the old server shut down and unknown passwords, can take months of field visits, and that has to show up in the price or the schedule from the start.

If you want to assess how the fleet of a base you're buying would come into IXC ACS, click the button below and talk to our team.

Let's elevate your client experience togheter?

With IXC ACS, you manage devices, run diagnostics, and perform mass operations remotely. Offer an agile and efficient support experience for your customers while saving time and resources.

    ISP acquisition: how to integrate the inherited CPEs