Data Center Migration in Italy

What Is a Datacenter Migration in Italy?

Italy's Datacenter Landscape: Where Migrations Happen

• Milan (Caldera Park and environs): The dominant hub. Equinix operates ML1 through ML6 in and around Milan, with ML5 and ML6 at the Caldera Park campus in Settimo Milanese representing the highest-density colocations in Italy. Irideos (formerly MClink and KQ) runs facilities in Milan and connects directly to MIX, the Milan Internet Exchange, which currently peers over 300 autonomous systems. Data4 operates its IT1 campus near Milan. For any organisation needing access to European Internet exchange infrastructure, Milan is the primary landing point.
• Rome: The secondary hub, predominantly serving Italian public administration, media organisations and enterprises with headquarters in the capital. Retelit operates in Rome and provides nationwide dark fibre capacity. Several smaller carrier-neutral providers serve the EUR business district and northern Rome.
• Turin: A growing edge node, historically tied to the Italian manufacturing and automotive sector. Facilities here serve industrial IoT workloads, regional banking and university research networks. Turin is relevant for organisations consolidating satellite offices in northern Italy.
• Power standards: All Italian facilities operate on 230V/50Hz single-phase and 400V/50Hz three-phase. Equipment arriving from North America (120V/60Hz) requires transformer or UPS conversion before installation. Reboot Monkey engineers verify power compatibility as a mandatory pre-migration step.

The Regulatory Context Every Migration Plan Must Address

• GDPR and the Garante Privacy: Italy's data protection authority, the Garante per la protezione dei dati personali, is one of the most active regulators in the EU for GDPR enforcement. Any migration that involves a change of facility also involves a change in the location where personal data is processed and stored. This may require an update to Records of Processing Activities (RoPa), a new Data Processing Agreement with the incoming facility operator, and potentially a Data Protection Impact Assessment if the new facility introduces a change in risk profile. Reboot Monkey does not provide legal advice, but our migration coordinators flag these obligations to your compliance team before execution day.
• NIS2 via D.Lgs 138/2024: Italy transposed the NIS2 Directive into national law through D.Lgs 138/2024, which came into force in late 2024. Organisations classified as essential or important entities under this legislation must maintain documented inventories of their IT infrastructure and notify the competent authority (ACN, the National Cybersecurity Agency) of significant changes to their systems. A datacenter migration qualifies as a significant change for most NIS2-covered entities. Migration planning must include a notification timeline and a risk assessment of the transition window.
• AGCOM: Italy's communications regulator, AGCOM, governs telecommunications infrastructure and interconnection. If your migration involves changing your upstream connectivity provider or transitioning between different BGP peering arrangements at MIX or other Italian exchange points, AGCOM authorisation obligations may apply to the new provider relationship.
• Sector-specific obligations: Italian banking (Banca d'Italia), healthcare (Ministero della Salute) and public administration organisations face additional sector-specific requirements for outsourcing and infrastructure changes. Reboot Monkey migration coordinators have operated inside Italian regulated industries and can align migration window scheduling with change management freeze periods and audit notification requirements.

How Reboot Monkey Executes a Migration in Italy

• Phase 1 — Discovery and inventory: Reboot Monkey engineers conduct a physical audit of the source facility. We photograph every cabinet, document every cable run (power, data and out-of-band management), record every piece of equipment by make, model and serial number, and capture the logical network topology. For migrations inside Equinix ML campuses, we coordinate pre-visit access through Equinix's Smart Hands scheduling portal. For Irideos, Aruba and Retelit, we follow each provider's specific escort and access card procedures. Discovery typically takes one to three days depending on cabinet count.
• Phase 2 — Migration planning: Based on the discovery output, we produce a migration runbook. The runbook sequences every task in dependency order, assigns time estimates to each, identifies the critical path and defines rollback procedures for each high-risk step. Networking changes, particularly BGP session handoffs and IP renumbering, are sequenced to minimise the window during which both the old and new facility are only partially operational. If the migration involves a MIX peering change, the BGP session cutover is planned with enough lead time to pre-establish sessions at the new facility before decommissioning the old ones.
• Phase 3 — Pre-staging at the destination: Before any equipment leaves the source facility, Reboot Monkey engineers pre-stage the destination environment. This means installing empty cabinets, running power whips to the correct PDU specifications (230V/50Hz in all Italian facilities), pre-labelling cable runs and verifying that cross-connects have been provisioned by the destination facility operator. For Equinix ML5 or ML6, cross-connect orders can take 5 to 10 business days, and our project coordinators submit these orders as part of Phase 2 to avoid holding up the execution day.
• Phase 4 — Physical migration execution: Equipment is powered down in reverse dependency order (edge devices first, core switching and storage last), physically removed, transported between facilities (or within campus via cage-to-cage trolley), racked and stacked in the destination cabinets, cabled per the pre-staged plan and powered on. Reboot Monkey engineers perform a power-on sequence verification against the runbook, confirm that all management interfaces are reachable on the out-of-band network, and hand control back to your team for application-layer validation.
• Phase 5 — Decommissioning and sign-off: Once the destination environment has been validated, the source facility is decommissioned. Reboot Monkey removes all cables, blanking panels and equipment from the source cabinets, coordinates the return of facility assets (smart hands kits, PDU accessories, cross-connect terminations) and provides a written sign-off report confirming that the source space is clear and that no data-bearing media has been left behind — a requirement under both GDPR and the internal data disposal policies of most Italian enterprises.

Migration Scenarios: What Triggers an Italian DC Move

• Operator consolidation: An Italian manufacturing group operating separate cage footprints in an Irideos facility in Rome and a Retelit location in Turin consolidates into a single Data4 campus in Milan, chasing better cross-connect pricing and improved proximity to their European cloud on-ramps. The complexity here is the dual-source migration: both source facilities must be emptied in a coordinated sequence while maintaining application availability throughout.
• Equinix campus move: An operator outgrows their initial cage in Equinix ML1 and needs to move to a larger suite in ML5 at Caldera Park. Despite both locations being Equinix facilities, this is a cross-campus physical migration with its own cross-connect reprovisioning, power circuit handoffs and MMR (Meet-Me Room) coordination. Reboot Monkey engineers are familiar with the Equinix Smart Hands portal and the specific cabinet and power circuit documentation requirements at each ML campus.
• Private server room exit: A mid-sized Italian enterprise decommissions its on-premise server room to move into carrier-neutral colocation. This often involves equipment that has not been moved in five to eight years, undocumented cable runs and legacy hardware that requires physical inspection before transport. Our discovery phase is especially critical in this scenario.
• Compliance-driven migration: Following D.Lgs 138/2024 NIS2 transposition, an Italian energy utility must move from a facility operated by a non-EU parent company to a facility with Italian data sovereignty guarantees. The project has a regulatory deadline and requires a migration window that aligns with ACN notification obligations.

Why Third-Party Execution Changes the Risk Profile

Timeline and Pricing: What to Expect

• Small migrations (1-5 cabinets, single facility): Discovery plus execution typically completes in 3 to 7 business days from first contact. Execution windows are typically a single overnight session. Pricing starts from a few thousand euros depending on scope.
• Mid-scale migrations (6-20 cabinets, single or dual facility): Discovery takes 2 to 5 days. Planning and pre-staging add 1 to 3 weeks. Execution spans 1 to 3 overnight windows. Total project timeline is typically 4 to 8 weeks from kick-off.
• Large-scale migrations (20+ cabinets, multi-site, or compliance-driven): These projects require dedicated project management, multi-phase execution plans and often a parallel-running period during which both the source and destination environments are operational. Timelines range from 8 to 20 weeks. Reboot Monkey assigns a named project coordinator who is the single point of contact throughout.
• All pricing is quoted on a time-and-materials or fixed-scope basis depending on discovery confidence. We do not apply a facility surcharge for working inside Equinix, Irideos, Aruba, Retelit or Data4 — our rates reflect the work, not the operator name on the building.

Preparing Your Team: What You Need to Have Ready

• Facility access authorisation: You must authorise Reboot Monkey engineers on the access list at both the source and destination facilities before execution day. For Equinix, this means adding us to the Smart Hands authorisation list. For other Italian providers, the process varies but typically requires a formal letter of authorisation from the facility customer account holder. Your account manager at each facility can confirm the exact procedure.
• IP address and BGP planning: If your migration involves a provider change or a cross-connect change at MIX, IP renumbering or BGP session updates may be necessary. These changes require lead time with your upstream and peering partners. Reboot Monkey engineers will flag dependencies during Phase 2 planning, but the IP and routing changes must be executed by your network team or arranged with your network provider.
• Maintenance window approval: Enterprise change management processes, particularly in NIS2-regulated organisations, require formal approval for maintenance windows. Get the migration window into your change management system as early as possible. Italian banking and insurance organisations often have frozen change windows around quarter-end and year-end that are non-negotiable.
• Application dependency mapping: Know which applications depend on which pieces of hardware. Reboot Monkey will document the physical environment, but application-layer dependencies are your responsibility to map. Without a current application dependency map, the migration sequencing in the runbook cannot account for hidden inter-system dependencies.

Questions About Datacenter Migration in Italy