Modernisation of IT infrastructure in a small company - case study

In short: starting point, scope and result

Area	State before work	Scope made by NexaIT
Users and systems	7 workstations, printers, an ERP system on an ordinary office computer with a single drive and a single power supply	Inventory of dependencies and organisation of the network layer
Internet	A connection reaching around 1-5 Mb/s according to the documentation and dropping regularly, with no fibre in the town	A new 5G link with an external unit, chosen after on-site measurements
Cabling	Unlabelled cables, devices on a windowsill above a radiator	New structured cabling, terminations, port descriptions, patch panel and 19-inch RACK cabinet
Local network	Old devices, some no longer receiving manufacturer updates, no central management and no documentation	UniFi network gateway, managed PoE switch, i.e. powered via a network cable, and central management
Wi-Fi	No business wireless network	3 Wi-Fi 7 access points, i.e. devices that distribute the wireless network; coverage in the building and in the yard
Traffic separation	All devices on one network	VLANs, i.e. logical segments for office, management and server, monitoring, IoT and guests
Power supply and operating conditions	Lack of consistent infrastructure security	A UPS plus temperature and humidity sensors in the cabinet
CCTV	No cameras	6 4K cameras, local recording in UniFi Protect on a 12 TB drive

The scope described in this case study covers the network infrastructure and CCTV. The server for the ERP system, backups and ongoing support are the next stage, which has not yet been implemented, so we do not present them as completed. You will also find a short description of this project on the page modernising IT infrastructure from the ground up.

“It works somehow” as a description of the existing state

This state looks like an extreme case, but such setups rarely result from a single bad installation. Most often they build up over years. Someone adds a new router, someone else extends a cable, another device goes wherever there happens to be a free socket, and the knowledge of the connections stays only in one person's memory.

From the outside you see a mess. From the business's perspective the problem was more serious, because day-to-day work depended on this infrastructure:

• seven workstations used the internet and the ERP system,
• the printers needed constant network access,
• the ERP system ran on an ordinary office computer with a single drive and a single power supply,
• there was no confirmed, tested backup,
• the connection was slow and dropped regularly, and there was no fibre in the town,
• the company did not have a consistent network Wi-Fi,
• some devices were no longer receiving manufacturer updates,
• there was no CCTV,
• lacked central management, port descriptions and up-to-date documentation.

So the devices sitting on a windowsill above a radiator were not the biggest risk. The biggest risk was not knowing what would happen if one of the cables were unplugged, and how quickly work could be restored.

If similar symptoms occur in your business, there may be several causes. We have described how to sort them out in the guide why the corporate network is slow and where to start diagnosing.

Why didn't we start by replacing the router

A new router would not have fixed unlabelled cables, created network points in the rooms or answered the question of where the computer running the ERP system was connected. Nor would it have provided power protection, documentation or Wi-Fi coverage across the whole site.

The first task was therefore an inventory of the existing state. We checked the devices, connections, the layout of workstations, how the internet came in and the dependencies that mattered for the business's work. At the same time we analysed the available connection options, because at this location the traditional solution did not provide the expected performance.

Only after this analysis could the order of work be planned. The project covered the passive layer, active devices, the wireless network, backup power, sensors in the cabinet and the camera system. The result was a single managed infrastructure with clearly defined functions instead of yet another element bolted on to the old setup.

How the IT infrastructure was modernised in a small company

1. New structured cabling and one distribution point

We ran new structured cabling to the workstations and devices covered by the project. We terminated the runs in a patch panel, labelled them at both ends and organised them in a 20U 19-inch rack cabinet. The cabinet houses the network devices, backup power and environmental sensors.

We tested every installed run for continuity. We deliberately do not call this a cabling certification test, because such a test requires the appropriate procedure, a certifier and a report with transmission parameters. This distinction matters when the installation is signed off.

The choice of cabinet was not about looks either. It needed space for the devices, cable routing, ventilation, service access and spare capacity for future expansion. We describe more practical criteria in the material how to choose a RACK cabinet for a small company.

2. New 5G connection instead of continuing to patch the old access

In the initial documentation we recorded a throughput of around 1-5 Mb/s and repeated connection drops. There was no fibre in range, so we compared satellite internet and 5G, checked the signal on site and then set up a 5G link with an external receiving unit.

The external unit was not a random choice. On mobile networks, the result is determined by the conditions at the specific location, the signal level and quality, the load on the base station and the correct positioning of the device. That is why 5G should not be chosen solely on the basis of a coverage map or the speed claimed in the carrier's offer.

We do not publish a speed test result after the deployment, because we do not have an approved measurement intended for a public “before and after” comparison. We can, however, confirm that the analysis was carried out, the solution was selected and the new link was set up as part of the target architecture.

3. Centrally managed network UniFi and three access points Wi-Fi 7

We deployed a centrally managed UniFi network comprising a UDM-Pro gateway, a 24-port PoE switch and three Wi-Fi 7 access points: two in the building and one outdoors for the yard.

The gateway handles routing, the firewall and management of the environment. The switch powers PoE-compatible devices, so the access points and some of the cameras do not need separate power supplies. We chose the access points to suit the layout of the site and the required zones, with the number of users as one of the criteria. The manufacturer publishes a detailed U7 Pro access point specifications, but the quality of a deployment depends on placement, configuration and radio conditions.

Central management gives the administrator a shared view of devices, clients, ports and events. It does not eliminate failures, but it changes how they are diagnosed: instead of checking several independent devices with no history, you can start from a consistent topology and the current state of the network.

4. Dividing traffic into zones

We implemented a logical division into VLANs, separating office traffic, the server and management devices, CCTV, IoT and the guest network. A camera or a guest's phone does not sit on the same network as computers holding company data, and access rules can be built according to the function of each device.

Segmentation alone does not provide security. Its effectiveness depends on firewall rules, account management, updates and testing of communication between segments. This project created the zone architecture and a basis for further hardening of the configuration. A full cybersecurity audit was not within the scope of this stage.

5. UPS and control of conditions in the cabinet

We put the network devices and the recorder on UPS backup power. We also added temperature and humidity sensors so that the conditions inside the cabinet are visible.

A UPS lets you ride out short outages, limits the effects of voltage fluctuations and gives time for a controlled shutdown of devices; it does not replace a generator or redundant power. The sensors make it possible to spot a rise in temperature before the problem starts to show as unstable hardware.

6. Six 4K cameras with local recording

The last part of the scope was setting up UniFi Protect CCTV. We installed six 4K cameras: two in the building and four outdoors and in the warehouse. Recordings are stored locally on a 12 TB drive designed for continuous operation.

Local recording means that the footage does not automatically have a copy off site. The manufacturer states that UniFi Protect recordings remain locally on the UniFi console. If the business needs an additional copy, longer retention or a procedure for exporting footage after an incident, this has to be planned separately and confirmed with a test.

What actually changed after implementation

The most important result is the move from infrastructure that nobody could fully describe to an environment that can be managed and developed further. The neatly laid cables in the photo are only a side effect.

Before modernisation	After executing the range NexaIT
Devices on the windowsill above the radiator	One distribution point in a RACK cabinet
Unlabelled cables	Marked tracks, ports and as-built documentation
Old, independent devices	One centrally managed network platform
No corporate Wi-Fi	Three Wi-Fi 7 access points in the building and in the yard
Everything in one network	Separate VLANs by function and trust level
No consistent power protection	UPS and environmental sensors in the cabinet
No cameras	Six 4K cameras with 12 TB local storage
Diagnosis based on guesswork	Central view of devices, ports and clients

We do not publish a percentage improvement in availability, a number of failures avoided or time savings, because the project had no earlier measurement baseline that would allow such metrics to be calculated honestly. The result can, however, be assessed operationally: it is known which elements make up the network, where they are connected, how they are powered, which devices belong to which segment and who has administrative access.

What we have prepared beyond devices

Equipment without documentation can, after a few years, lead back to the same starting point. That is why the handover package also included the information needed for later maintenance:

• list of devices and their roles,
• description of network segments,
• port and logical point designations,
• information about configuration and administrative access,
• as-built documentation,
• scope of tests performed and list of elements requiring further work.

Documentation should allow the environment to be looked after even by someone who was not involved in the installation. That is why we treat acceptance protocol and as-built documentation of the network as part of the deployment.

What we do not consciously add to this case study

A good project description also shows the limits of responsibility. In this case we do not claim that:

• we set up a server for the ERP system; that is the next stage, which has not yet been implemented, and until then ERP on an office computer remains a risk,
• we implemented and tested backups or put the business on ongoing support; both belong to the same future stage,
• the cabling has a certification report; we tested the runs for continuity, which is not the same as a certification test,
• we carried out a full cybersecurity audit and complete hardening of the environment,
• a specific connection speed, recording retention or UPS runtime was achieved; we do not publish these values without a documented test,
• local camera recordings are a backup; an off-site copy is a separate decision.

These reservations do not detract from the modernisation performed. They show which risks have been closed and which require another task, budget and acceptance criteria.

What you can check in your own business from this project

You do not have to wait for a total failure to assess the state of your infrastructure. It is enough to answer a few questions:

1. Do you know where each wire goes to at the main network point?
2. Do active devices have current support and a single configuration owner?
3. Are the guest network, monitoring, IoT devices and employee computers logically separated?
4. After a power outage, do you know how long the router, switches and recorder work?
5. Is there a current network diagram and a list of administrative accesses belonging to the company?
6. What hardware does the ERP system run on, and has its backup ever been restored in a controlled test?
7. Can a connection failure be told apart from a Wi-Fi problem or a problem with a specific switch port?

If the answer to most of these questions is “I don't know”, the problem goes beyond the look of the cabling. The business has no control over the system its day-to-day work depends on.

Frequently asked questions about a similar modernisation

Does a business with seven workstations really need a managed network?

The number of computers is only one of the criteria. This environment also included printers, the ERP system, cameras, access points and technical devices. Management becomes necessary when the business wants to see the state of its infrastructure, separate traffic, control access and diagnose problems faster.

Can 5G be the main internet connection in the company?

It can, if it is preceded by measurements at the specific location, the right choice of device and an assessment of stability. 5G availability on a map is not enough on its own. In businesses that depend heavily on the internet, consider a second connection and automatic failover separately.

Does Wi-Fi 7 solve the range problem?

The standard alone will not do it. A newer standard provides certain technical capabilities, but coverage and connection quality depend on the placement of access points, the building's construction, interference, configuration and the capabilities of client devices. In this project, what mattered was three properly placed access points, including an outdoor unit.

Are local camera recordings a backup?

No. The disk in the recorder is the basic place for storing recordings. The loss of a device, disk, or entire object may mean loss of material, so additional copy requirements must be determined separately.

Where to start a similar project?

With an inventory and diagnosis. First you need to establish the business dependencies, the state of the cabling, critical devices, connection problems and the expected coverage. Only then can you choose the architecture, devices, order of work and acceptance criteria, and finally the shopping list.

Predictable infrastructure in a small business

In a small business, one badly labelled plug can disconnect a printer, workstations or the ERP system. That is why modernisation covers cabling, power, logical network segmentation, monitoring, documentation and handing control over to the owner of the infrastructure, and replacing a device is only one of its elements.

We design, build and maintain corporate networks, combining the cabling layer, active devices, Wi-Fi and documentation into one scope. If you want to check whether your network is managed, let's start with free IT review.

How this case study was created

We prepared this description from the initial documentation, the inventory, the as-built documentation, the list of completed work and corrections from the person leading the project at NexaIT. We removed the client name, address and any details that could identify the site.

We have not used estimated figures as results of the deployment. Where there was no approved measurement or a given stage was not carried out, we say so plainly.

Sources

• Ubiquiti, U7 Pro, technical specification, https://techspecs.ui.com/unifi/wifi/u7-pro (accessed 02/10/2026)
• Ubiquiti, UniFi Physical Security, https://ui.com/physical-security (accessed 02/10/2026)

As of 2 October 2026.