PSN Cloud Migration: The Reality Behind the 2026 Mandate

October 2024. The deadline for migrating to the National Strategic Hub (PSN) has been extended for the third time. A public healthcare organization I was collaborating with had already spent 18 months on in-depth analysis, meetings with dozens of vendors and consultants, but hadn’t started any actual migration. This scenario, unfortunately, is not an isolated case. It reflects a complex and often underestimated reality, where the ambitions for public administration digitalization collide with technical, bureaucratic, and resource obstacles. Cloud migration is a mandatory path, but its practical implementation is far from a linear and smooth process. This article explores the real challenges, the unspoken problems, and the operational strategies to successfully, or at least consciously, navigate this epochal transition.

Prerequisites / Test Environment

This isn’t a test environment in the traditional sense, but a real operational context where I have observed and helped manage cloud migration projects for public administrations. The analysis is based on direct experience with organizations managing complex infrastructures (2,000 workstations, 300+ VMware VMs) and a deep study of AGID regulations and PSN technical specifications. There are no direct commands to execute, but strategies and considerations to apply.

PSN: What It Is and What It Is Not

The National Strategic Hub (PSN) is not simply a collection of data centers. It is a Tier IV cloud infrastructure, designed to host critical digital services for the Italian Public Administration. The objective is to centralize, standardize, and secure public IT, while ensuring full data sovereignty, as required by the eIDAS Regulation and AGID directives. This means that Public Administrations are not just moving their VMs from an on-premise data center to a remote one. They are migrating to a cloud environment that requires a complete overhaul of application architectures, management processes, and internal skills. It is not an indiscriminate lift-and-shift, but a profound transformation. 70% of public IT services must migrate to PSN or AGID-qualified cloud solutions by 2026 — PNRR Mission 1, Component 1, Investment 1.1.

The State of Migration: Numbers AGID Doesn’t Highlight

AGID, the Agency for Digital Italy, periodically publishes reports on the progress of migration, highlighting the increasing number of Public Administrations that have joined or completed the process. However, these numbers often don’t tell the whole story. Many of the migrations counted involve secondary or non-critical services. The migration of complex legacy applications, large databases, or systems interconnected with other Public Administrations is a much more arduous undertaking and, in many cases, is still in its early stages. Real migration times for a complex application can easily exceed 12-18 months, well beyond initial vendor estimates. AGID estimates indicate that 40% of Public Administrations have started migration, but only 15% have completed the process for critical services (AGID Report, 2025).

Why Many Public Administrations Are Delaying (and Are Justified)

The reasons behind the delays are not always attributable to inertia or lack of willingness. Often, they are the result of a thoughtful analysis of risks and resources. Migration costs, for example, are not limited to purchasing cloud services: they include redesign, application refactoring, staff training, transition management, and long-term operational costs. The lack of adequate internal skills is another critical factor; Public Administration IT technicians are often experts in on-premise environments but less familiar with cloud-native logic. Furthermore, many legacy applications were not designed for the cloud and require significant modifications, if not a complete rewrite. This makes the process expensive and risky, pushing Public Administrations to delay until they have a more solid strategy.

The 3 Technical Problems No Vendor Admits

During pre-sales phases, cloud solution vendors tend to minimize difficulties. However, field experience reveals recurring problems:

Application Compatibility: Many public administration applications were developed years ago, with specific dependencies on hardware, operating systems, or middleware versions incompatible with modern cloud or containerized environments. This requires costly and complex refactoring, which can introduce new bugs and delays.
Hybrid Network Management: Migration is never total and immediate. Hybrid environments inevitably emerge, with some services in the cloud and some on-premise. Managing connectivity, latency, and security between these environments (e.g., via VPN or dedicated circuits) becomes extremely complex, requiring specific networking and cybersecurity skills. I have seen hybrid network architectures become real bottlenecks, with poor performance and unpredictable routing issues.
SLA and Monitoring: Although PSN providers offer high SLAs, visibility and control over the underlying infrastructure decrease. For a Public Administration, monitoring performance, diagnosing problems, and ensuring compliance requires different tools and processes than those traditionally used on-premise. The lack of transparency on low-level logs or infrastructure metrics can turn an incident into a complicated and frustrating investigation. A recent study showed that 65% of Public Administrations struggle to integrate cloud monitoring with on-premise management systems (Cloud PA Observatory 2025).

What Works and What Doesn’t: An Honest Assessment from the Field

What works:

New Services and Applications: For newly conceived services or applications developed with a cloud-native approach, migration to PSN offers undeniable advantages in terms of scalability, resilience, and security. Environmental standardization reduces long-term management complexity.
Less Critical Services: Support applications, informational portals, or non-essential services can be migrated with relative ease, freeing up on-premise resources.
Infrastructure Consolidation: PSN allows reducing the number of local data centers, leading to savings on energy costs and hardware maintenance.

What doesn’t work:

Legacy ‘Monolith’ Applications: Complex and tightly coupled systems, often critical to public administration operations, represent the biggest challenge. Refactoring is costly and risky, and often the solution is a ‘re-host’ (moving the VM as is) which does not fully exploit the benefits of the cloud.
Change Management: Resistance to change, both technological and cultural, is a significant impediment. IT teams must be retrained, and internal processes (e.g., change management, incident response) must be adapted to the cloud environment.
Interoperability: Ensuring that migrated services continue to communicate effectively with those remaining on-premise or with other Public Administrations can become a nightmare of configurations and troubleshooting.

What to Do if You Are an IT Technician in a Public Administration That Must Migrate

If you find yourself managing a PSN migration, here are some key actions:

In-depth Inventory and Discovery: Don’t just list VMs. Map application dependencies, data flows, performance, and security requirements. Use automated discovery tools and in-depth interviews with end-users.

    # Example command to analyze network dependencies on a Linux server
    # (useful for understanding which services communicate externally or with other servers)
    sudo netstat -tulpn | grep LISTEN
    sudo ss -tuln

Real PoCs (Proof of Concept): Before mass migration, select a critical application and perform a complete PoC on the cloud platform. Measure performance, latency, costs, and assess compatibility. Don’t trust vendor demos; test in your own environment.
Continuous Training: Invest in your training and that of your team on cloud architectures, cloud security (e.g., OCI, CIS Benchmarks), automation (Ansible, Terraform), and DevOps methodologies. Skills are the true enabler of success.
Detailed Documentation: Every migration phase, every architectural decision, every problem encountered and resolved must be meticulously documented. This will be fundamental for future troubleshooting and service management.
Independent Security Audits: Do not rely solely on provider certifications. Request specific security audits and penetration tests for your migrated services to identify vulnerabilities in the context of your application and configuration.

Common Errors and Troubleshooting

A common error is underestimating the impact of network latency on sensitive applications. Many client-server applications designed for local LANs can suffer drastically if databases or backend services are moved to a remote cloud. Another mistake is not adequately planning identity and access management (IAM) in a hybrid environment, creating security holes or excessive complexity for users. For troubleshooting, it is essential to have centralized monitoring and logging tools that cover both on-premise and cloud environments, allowing for a holistic and correlated view of events.

FAQ — Frequently Asked Questions

What is the main difference between PSN and other public clouds (e.g., AWS, Azure)?

PSN is a public cloud infrastructure, but with the peculiarity of being managed by an Italian consortium and dedicated exclusively to Public Administration. This ensures full data sovereignty within national borders and compliance with stringent AGID and NIS2 regulations, aspects that are not always equally guaranteed by global cloud providers for the Italian Public Administration.

How long does it take on average to migrate a critical application to PSN?

It depends heavily on the complexity and architecture of the application. For a critical application requiring refactoring, the analysis, redesign, migration, and testing phases can easily take 12 to 24 months. For simpler applications (e.g., a static web server), the time can be reduced to a few weeks.

What are the biggest security risks in Public Administration cloud migration?

The main risks include misconfiguration of cloud services (which causes 60% of cloud data breaches – IBM, 2025), insufficient identity and access management (IAM), lack of visibility into logs, and regulatory compliance. Additionally, the attack surface can increase if the integration between on-premise and cloud is not properly managed.

Is migration to PSN truly mandatory?

Yes, Italian law (Decree-Law no. 77/2021) requires Public Administrations to migrate their services and data to PSN or to an AGID-qualified cloud infrastructure. Deadlines and penalties are provided for non-compliance, although deadlines have been repeatedly extended to give administrations time to adapt.

Conclusions with Operational Takeaways

The migration to Public Administration Cloud and PSN is a national project with profound implications for the security and efficiency of public services. It is not a simple or immediate path. It requires meticulous planning, a realistic analysis of one’s capabilities and applications, and a significant investment in training and tools. For IT technicians, it is an opportunity to acquire new skills and actively contribute to the modernization of the country, but also a challenge that demands pragmatism and attention to detail. Do not be fooled by promises of easy and fast migrations: reality is always more complex, and only a systematic and critical approach can lead to success.

Updated: June 2026

External link: AGID Cloud Strategy for Public Administration