Datacenter Migration Services in Brazil

Datacenter migration refers to the physical relocation of computing infrastructure from one facility to another. In Brazil, this typically means moving equipment between carriers, between operators, or between campuses within the same metro area. The scope ranges from a single cage exit to a full building-level decommission and rebuild. This page covers full facility migration: the coordinated, phased movement of an organization's entire datacenter footprint from a source facility to one or more destination facilities. That is distinct from individual server relocation, which is covered on the <a href="/en/server-migration/brazil/">server migration Brazil</a> page. In a full facility migration, server-level moves are one component of a larger logistics and project management engagement. The physical scope of a datacenter migration in Brazil can include: - Cage-level exits from operators such as Equinix SP1, TIVIT, or Odata in the Sao Paulo metro - Suite-to-suite moves within the same campus - Cross-operator migrations from telco-owned facilities (such as Vivo Datacenter) to carrier-neutral alternatives - Rio-to-Sao Paulo consolidations, where organizations centralize distributed footprints into a single primary hub - Full building-level decommissioning followed by deployment in a destination facility Reboot Monkey does not provide cloud migration or virtual infrastructure services. All work is physical: racks, servers, cabling, power distribution, and the hands that touch them inside the datacenter. Customers bring their own cloud strategy. We move the hardware. A full datacenter migration in Brazil is a project management engagement as much as it is a physical execution task. Site assessments, power audits, cross-connect scheduling, operator coordination, phased cutover windows, and rollback plans are all part of the scope. Reboot Monkey assigns a dedicated project lead to each engagement, who serves as the single point of contact from planning through post-migration support.

Brazil's datacenter environment introduces regulatory, electrical, and logistical factors that directly affect migration planning. Understanding these before the first rack moves is not optional. <strong>Power infrastructure: 220V/60Hz</strong> Brazil operates on 220V at 60Hz in most commercial and datacenter environments. This is relevant during migrations where equipment sourced from or destined for North American facilities (typically 120V/60Hz) may require PDU replacement or reconfiguration. European equipment (220V/50Hz) will operate at the correct voltage but the 60Hz frequency difference can affect sensitive timing hardware. Power compatibility must be verified for every equipment category before the migration window opens. <strong>LGPD compliance and data residency</strong> Brazil's Lei Geral de Protecao de Dados (LGPD), established under Lei 13.709/2018, requires organizations handling personal data to maintain accountability for where data is processed and stored. The Autoridade Nacional de Protecao de Dados (ANPD) has issued Resolution CD/ANPD No. 2/2022, which sets a 3 business day notification window for confirmed data incidents. During a datacenter migration, the period when equipment is in transit or powered down represents a window of elevated risk for data handling accountability. LGPD-conscious migration planning therefore requires: - Pre-migration data mapping to confirm which workloads contain personal data - Encryption verification for storage devices in transit - Chain-of-custody documentation for all equipment movements - Post-migration confirmation that data is accessible and intact before ANPD notification obligations could be triggered Reboot Monkey is a physical infrastructure provider, not a data processor under LGPD definitions. However, customers operating under LGPD have used our documentation and chain-of-custody practices as part of their own compliance evidence. <strong>BACEN CMN Resolution 4.658/2018</strong> For Brazilian financial institutions regulated by the Banco Central do Brasil, CMN Resolution 4.658/2018 governs requirements around data processing and cloud service outsourcing. This regulation affects how banks and payment institutions must document their technology infrastructure arrangements. Physical datacenter migrations for regulated financial entities require migration planning that satisfies the continuity and resilience documentation standards the resolution imposes on their outsourced processing environments. <strong>Operator access and scheduling</strong> In Brazil's primary hubs, datacenter operators have formal access management requirements. Equinix SP1 and SP2, Ascenty, and TIVIT all require pre-scheduled access windows with named engineer lists and escort procedures. Reboot Monkey coordinates directly with facility operations teams to schedule access windows, avoiding conflicts with other tenant activities and ensuring that our field engineers hold valid access credentials before any migration window opens. <contact note inline>For complex multi-facility migrations requiring LGPD documentation support, <a href="/en/contact/">contact the Reboot Monkey team</a> early in your planning cycle. Lead times for coordinating access windows across multiple Sao Paulo operators can extend to 3-4 weeks.</contact note inline>

Reboot Monkey is a third-party datacenter services provider, independent from every facility operator in Brazil. We are not affiliated with Equinix, Ascenty, TIVIT, Odata, or Scala. That independence means we can execute migrations across any combination of operators without a conflict of interest in where the destination equipment lands. Every full datacenter migration engagement follows a phased execution model: <strong>Phase 1: Discovery and site assessment</strong> Before any equipment moves, the project lead conducts a site assessment at both the source and destination facilities. This covers power capacity at the destination (cabinet density, PDU specifications, circuit availability), cross-connect availability and lead times, physical access constraints, loading dock and freight elevator availability, and equipment inventory verification against the customer's asset register. Brazil's larger facilities in Sao Paulo often have complex sub-metering arrangements that require pre-migration confirmation. <strong>Phase 2: Migration planning and cutover design</strong> The project lead produces a migration runbook: a sequenced, time-stamped plan covering every equipment category, cutover window, and dependency. For facilities with production workloads, the runbook defines the order of migration to minimize concurrent downtime exposure. Network cutover sequences are designed in coordination with the customer's network team, with cross-connect port pre-provisioning at the destination before the primary migration window. <strong>Phase 3: Phased physical execution</strong> Reboot Monkey field engineers execute the physical migration according to the runbook. Services drawn on during execution include <a href="/en/rack-and-stack/brazil/">rack and stack at the destination</a> (mounting, cabling, and labelling all equipment in the new facility), <a href="/en/server-migration/brazil/">individual server relocations</a> as components of the larger move, and <a href="/en/smart-hands/brazil/">smart hands support</a> for tasks requiring configuration judgment (firmware checks, cable management, power sequencing). Each phase of physical work is logged against the runbook, with timestamped sign-off from the project lead. Reboot Monkey's field engineers are vendor-neutral and certified across Dell, HP/HPE, Cisco, Juniper, Arista, Supermicro, and Lenovo equipment. That breadth matters in Brazilian enterprise migrations, where mixed-vendor environments are common. <strong>Phase 4: Post-migration validation</strong> After physical migration, the project lead coordinates a validation pass covering power-on sequencing, network connectivity confirmation, and an updated asset register for the destination facility. The customer's operations team receives a post-migration report documenting every equipment movement, access event, and discrepancy found during execution. <strong>24/7 NOC monitoring and 4-hour incident response</strong> For the duration of the migration window and the 48-hour stabilization period after, Reboot Monkey maintains 24/7 NOC monitoring with a 4-hour on-site incident response SLA. The 4-hour response covers physical incidents: hardware failures, cabling faults, power discrepancies. It is a separate commitment from rollback activation, which has its own defined trigger criteria in the runbook. Reboot Monkey operates with a team of 5 core staff coordinating a global network of field engineers. For Brazilian migrations, field engineers are sourced from our Sao Paulo and Rio de Janeiro coverage pools. The project lead is always a named individual, not a rotating service desk contact.

The operational risk of a datacenter migration in Brazil is concentrated in two windows: the cutover itself, and the 48-72 hours after power-on at the destination when integration failures surface. Business continuity planning for a migration is not a contingency; it is a design input. Reboot Monkey's migration runbooks include explicit rollback criteria defined before the migration window opens. A rollback is triggered by specific technical conditions, not by a general sense that something has gone wrong. Examples include: failure to establish network connectivity at the destination within the defined timeout, discovery of hardware incompatibility that cannot be resolved on-site, or facility-side power incidents at the destination. Rollback capability is maintained by keeping the source facility infrastructure intact and powered through the primary migration window. Equipment at the source is not decommissioned, cabling is not removed, and power is not surrendered until the destination has been validated. This approach extends the overlap period (where both facilities carry cost) but eliminates the scenario where a migration failure leaves the customer with no operational environment. For customers with zero-downtime requirements, Reboot Monkey designs parallel-run phases where both source and destination environments carry live workloads during the transition. This is more complex to execute but eliminates the binary cutover risk. The approach requires pre-provisioned cross-connects between source and destination facilities, which must be ordered well in advance of the migration window. For organizations moving from TIVIT or telco-owned facilities in Rio de Janeiro to carrier-neutral facilities in Sao Paulo, the geographic separation between source and destination creates additional logistics considerations. Equipment in transit between Rio and Sao Paulo (approximately 430 km) must be handled under chain-of-custody procedures with temperature-controlled transport for sensitive hardware. Reboot Monkey coordinates logistics providers with datacenter equipment handling experience, not general freight. Post-migration, Reboot Monkey provides <a href="/en/remote-hands/brazil/">ongoing remote hands support</a> at the destination facility. The same team that executed the migration is available for day-2 and day-3 support: recabling issues, asset audits, hardware failures that surface in the first weeks of operation. Having continuity of knowledge between the migration team and the post-migration support team eliminates the handover gap that causes incidents in the stabilization period. For organizations planning full facility exits, the migration is often followed by <a href="/en/data-center-decommissioning/brazil/">datacenter decommissioning at the source</a>. Reboot Monkey can execute the source facility teardown as the final phase of the engagement: removing equipment, sanitizing storage media, returning cage space to the operator, and providing a final decommissioning report.

Brazil is the largest datacenter market in Latin America by installed capacity. The primary hub concentration is in the Sao Paulo metropolitan area, with secondary markets in Rio de Janeiro and Campinas. Understanding which operators hold the infrastructure your organization is moving out of, and which hold the destination, shapes the entire migration approach. <strong>Sao Paulo metro</strong> Sao Paulo hosts the densest concentration of carrier-neutral datacenter space in Latin America. Equinix operates multiple facilities in the Sao Paulo metro area (SP1 and others), serving large enterprise and cloud-interconnect requirements. Ascenty, a Digital Realty affiliate, operates facilities across Sao Paulo, Rio de Janeiro, and the Campinas region, supported by more than 4,000 km of fiber connecting Brazilian facilities to international submarine cable landing stations. Scala Data Centers operates a large campus in Campinas with capacity suited to hyperscale and enterprise deployments. TIVIT operates managed datacenter environments with integrated IT services, making TIVIT exits a common migration scenario where customers move from a managed environment to operator-neutral colocation. Odata operates neutral colocation facilities in Sao Paulo and other cities. Equinix's Brazil footprint is part of its global interconnection platform, which makes it a frequent destination for organizations migrating out of telco-managed or legacy facilities. <strong>Rio de Janeiro</strong> Rio de Janeiro is the second-largest datacenter market in Brazil, with a concentration of financial services, government, and media sector customers. Facilities in Rio serve organizations with regulatory data residency requirements that specify Rio as a location, and those with dual-city redundancy strategies. Rio-to-Sao Paulo consolidations are one of the most common migration scenarios Reboot Monkey handles in Brazil: organizations that maintained a Rio presence for historical or regulatory reasons and are now consolidating into a single Sao Paulo primary with cloud or remote DR. <strong>Campinas</strong> Campinas, approximately 100 km northwest of Sao Paulo, is an emerging hub for hyperscale and large enterprise capacity. Lower land costs and available power have attracted investment from operators including Ascenty and Scala. For organizations already operating in the Campinas market, or planning to use Campinas as a DR site, Reboot Monkey field engineers cover the Campinas metro from the same coverage pool as Sao Paulo. <strong>IX.br connectivity context</strong> Brazil's Internet Exchange infrastructure, IX.br (also known as PTT Metro), operates at more than 18 Tbps of traffic capacity across its nodes, with over 2,100 connected autonomous systems (ASNs), according to IX.br public data. Sao Paulo IX.br nodes are located inside or adjacent to the major carrier-neutral facilities, making IX.br peering a relevant factor in destination facility selection for organizations with connectivity-sensitive workloads. Reboot Monkey does not provide interconnection brokering, but migration planning for network-dense environments accounts for cross-connect lead times and IX.br port provisioning at the destination. <strong>Common migration scenarios in Brazil</strong> The migration scenarios Reboot Monkey encounters most frequently in Brazil include: - TIVIT exits: moving from a fully managed environment to neutral colocation, which requires building new operational procedures for hardware the customer now manages directly - Telco-DC-to-neutral moves: migrating out of Vivo or other telco-managed facilities into carrier-neutral space for greater control and multi-carrier connectivity - Rio-to-Sao Paulo consolidations: consolidating geographically distributed footprints into a single Sao Paulo primary hub - Campinas greenfield buildouts: deploying new infrastructure in Campinas to supplement or replace existing Sao Paulo capacity In every scenario, Reboot Monkey's role is the physical execution layer: the team that touches the hardware, coordinates the access windows, and provides the documented chain of custody that the customer's project record requires.

The organizations requesting full datacenter migration services in Brazil share a common characteristic: they have an infrastructure footprint that has outgrown its current home, and the move cannot be completed by a general IT team working during business hours. <strong>Enterprise IT teams exiting managed contracts</strong> Many Brazilian enterprises built their initial datacenter presence inside managed services contracts with operators like TIVIT, which bundle infrastructure with IT management. When contracts mature or the organization decides to operate its own infrastructure, the exit involves a physical migration that the enterprise IT team has not done before. Reboot Monkey provides the execution expertise and the project management structure that internal teams lack for a one-time event of this scale. <strong>Financial services organizations with LGPD and BACEN obligations</strong> Banks, payment processors, and fintech companies operating under BACEN CMN Resolution 4.658/2018 and LGPD have specific documentation and continuity requirements for infrastructure changes. Migration engagements for this sector require a migration plan that satisfies regulatory audit requirements, not just technical execution. The combination of physical expertise and compliance-conscious documentation is a primary reason regulated financial institutions engage Reboot Monkey for migrations rather than attempting them with internal resources. <strong>Multinational organizations consolidating regional footprints</strong> Multinational companies with Latin American operations often maintain distributed datacenter footprints that were built incrementally. A regional consolidation into a single Sao Paulo hub, or into a primary Sao Paulo facility with a Campinas DR site, requires coordination across multiple operators and often across multiple countries. Reboot Monkey's vendor-neutral position means there is no operator relationship incentivizing us toward a particular destination facility. <strong>Organizations exiting Rio de Janeiro facilities</strong> Rio-based datacenter customers face a specific challenge: the local Rio market has fewer carrier-neutral operators and less available power capacity than Sao Paulo. Organizations that need more capacity, more redundancy, or more carrier choice typically consolidate into Sao Paulo. The Rio-to-SP migration requires physical logistics across the 430 km corridor, which Reboot Monkey coordinates as part of the full engagement. <strong>SMBs without in-house DC expertise</strong> Small and mid-size businesses that colocate a modest rack count often have no datacenter-specialist staff. When the lease expires, the operator relationship changes, or the facility no longer meets requirements, the migration falls to IT generalists who have not executed a structured physical migration. Reboot Monkey serves as the outsourced migration team for organizations of this size: providing the project lead, the field engineers, and the runbook without requiring the customer to build internal DC migration competency. Regardless of organization size, the contact point for every Reboot Monkey migration engagement is the same: a dedicated project lead, not a service desk ticket. <a href="/en/contact/">Contact the team</a> to discuss scope, timeline, and approach before committing to a migration window.