Server Migration Services in Brazil

Server migration in Brazil means moving physical hardware between datacenters. This is not cloud migration, not a virtual machine snapshot, and not a data replication exercise. Reboot Monkey engineers physically decommission, transport, and reinstall servers inside Brazil's colocation facilities, from the source rack through transit to the destination cage. Brazil's datacenter market is concentrated across three primary hubs: the Sao Paulo metro, Rio de Janeiro, and Campinas. Equinix SP1 and SP2 sit within the Sao Paulo metro area, alongside facilities operated by Ascenty, Odata, and TIVIT. These buildings house the country's largest financial institutions, media conglomerates, and multinational enterprise tenants. Physical access rules, power configurations, and cross-connect procedures differ between each operator, and Reboot Monkey engineers carry working knowledge of these site-specific requirements. A physical server migration engagement covers six stages: pre-migration audit and documentation, rack decommission and labeling, physical transport under chain of custody, destination rack-and-stack, cable management and patching, and power-on verification with the client's infrastructure team attending remotely or on-site. Each engagement produces a handover document that can be submitted to compliance teams under Brazil's Lei Geral de Protecao de Dados (LGPD) framework. Reboot Monkey operates as a third-party operator. We work inside facilities owned and operated by Equinix, Ascenty, Odata, TIVIT, and others. We do not own or manage any datacenter in Brazil. This is the defining characteristic of our service model: we are cross-operator by design, which means a migration from an Ascenty facility to an Equinix SP2 cage within the Sao Paulo metro uses the same Reboot Monkey project lead and the same documented process throughout. Single contract, single SLA, two facilities.

Every country presents distinct technical constraints, and Brazil is no exception. Three requirements appear on every Reboot Monkey pre-migration checklist for Brazilian facilities that are not present on the equivalent checklist for, say, a Frankfurt or Amsterdam engagement. <strong>Power: 220V/60Hz</strong> Brazil operates on 220V at 60Hz. This differs from the 230V/50Hz standard across continental Europe and the 120V/60Hz standard common in US datacenters. Engineers verifying power compatibility at destination facilities in Brazil must check both voltage and frequency. A server PSU that was spec'd for a European facility and auto-senses between 100V-240V will tolerate the voltage difference, but frequency-sensitive equipment (certain UPS bypass circuits, older PDUs) requires explicit verification. Reboot Monkey's pre-migration audit includes PDU model verification and frequency compatibility review for every hardware asset on the migration manifest. <strong>LGPD Data Breach Notification Window</strong> Brazil's LGPD, enforced by the Autoridade Nacional de Protecao de Dados (ANPD), requires notification of a data incident to the ANPD within 3 business days of the controller becoming aware of the incident. This is not 10 days. It is not 72 hours. It is 3 business days. If a server migration exposes a data breach through chain-of-custody failure, the client's 3-business-day notification clock begins on the day of discovery, not the day of the migration. Reboot Monkey's chain-of-custody documentation is specifically designed to establish that physical access remained controlled at all times, supporting the client's incident response and LGPD documentation obligations if an unrelated breach is discovered during the migration window. <strong>BACEN CMN 4.658/2018 and Physical Infrastructure</strong> Brazil's Central Bank regulation CMN 4.658/2018 governs data processing, cloud services, and technology outsourcing for financial institutions regulated by BACEN. It does not impose specific restrictions on physical access to servers or on which operator performs physical datacenter services. Financial sector clients using Reboot Monkey for server migrations should note that our service falls within the physical infrastructure operations layer, not the data processing or cloud outsourcing layer governed by CMN 4.658. However, Reboot Monkey recommends that financial sector clients confirm their own compliance scope with their legal and compliance teams before engagement, as each institution's BACEN obligations depend on their specific service architecture. Contact <a href="/en/contact/">Reboot Monkey's Brazil team</a> to discuss your specific facility and compliance requirements before scoping a migration.

Reboot Monkey's delivery model for server migrations in Brazil follows a structured five-phase process. This is not bespoke for each client. It is a repeatable process that reduces execution risk through standardization while accommodating the site-specific requirements of each facility. <strong>Phase 1: Pre-Migration Audit</strong> Before any hardware moves, Reboot Monkey's project lead performs a physical audit of the source environment. This covers rack inventory, cable labeling, power draw per server, interconnect dependencies, and cross-connect documentation. The audit output is a migration manifest: a numbered, photographed record of every asset to be moved. This manifest travels with the hardware and is signed at each handover point. <strong>Phase 2: Staging and Labeling</strong> Each server receives a physical label corresponding to its migration manifest entry. Cables are labeled before removal. A pre-migration photograph documents the source rack state at the cable level, not just the chassis level. This level of documentation exists because in cross-operator migrations, the destination facility's team cannot verify the source state. Photographic evidence resolves disputes that would otherwise delay the project or trigger LGPD-adjacent incident documentation. <strong>Phase 3: Decommission and Transport</strong> Hardware is removed from the source rack, packed to manufacturer standards, and transported under chain-of-custody documentation. For migrations within the Sao Paulo metro between, for example, Equinix SP1 and an Ascenty facility, transit times are typically under 2 hours when migrations are scheduled during off-peak windows. For inter-city migrations between Sao Paulo and Rio de Janeiro or Campinas, Reboot Monkey coordinates bonded transport. <strong>Phase 4: Rack and Stack at Destination</strong> Installation at the destination follows the migration manifest exactly. Every server goes into the pre-agreed rack unit position. Cabling replicates the source configuration unless the client has requested changes during Phase 1. <a href="/en/rack-and-stack/brazil/">Rack and stack work</a> at this phase includes cable management, PDU connection, and cross-connect patching where required. <strong>Phase 5: Power-On Verification and Handover</strong> Once hardware is installed and cabled, Reboot Monkey engineers power on servers in the sequence specified by the client's infrastructure team. Boot verification, IPMI/BMC access confirmation, and a final photograph of the destination rack are included in every engagement. The completed migration manifest is countersigned by the on-site engineer and provided to the client as the handover document. For the <a href="/en/smart-hands/brazil/">smart hands tasks</a> that occur during power-on verification, such as BIOS checks, firmware version confirmation, or network interface verification, Reboot Monkey's field engineers are equipped to perform these under remote instruction from the client's infrastructure team. This is not a separate service engagement. It is included within the migration delivery scope.

Reboot Monkey maintains two distinct operational commitments for server migrations in Brazil, and it is important to understand that these are separate. <strong>4-Hour Incident SLA</strong> The 4-hour incident SLA is an on-site response commitment. If an unplanned hardware incident occurs during an active migration window, such as physical damage during transit, a failed power-on, or a cable fault at the destination, Reboot Monkey commits to having a qualified engineer physically on-site and working on the resolution within 4 hours of incident declaration. This SLA applies to incidents within Brazil's major datacenter hubs, including the Sao Paulo metro, Rio de Janeiro, and Campinas. It does not mean the incident is resolved within 4 hours. It means an engineer is physically present and the resolution process is underway within 4 hours. <strong>Rollback Scope</strong> Rollback is a separate planning exercise. Before any migration begins, Reboot Monkey's project lead documents a rollback plan with the client. The rollback plan defines: which servers can be returned to the source facility, the conditions that trigger rollback, and the timeline for source facility availability after hardware removal. Rollback is not automatic, and it is not covered by the 4-hour incident SLA. The incident SLA covers diagnosis and mitigation at the destination. Rollback, if required, is executed against the agreed rollback plan with its own timeline, which depends on source facility access and transport logistics. This distinction matters for enterprise procurement. A CTO or IT Director reviewing the service agreement should confirm that their SLA expectations map correctly to either the incident response commitment or the rollback scope, not conflate the two. Reboot Monkey's project documentation is explicit on both, and both appear separately in the engagement contract. For clients in the financial sector operating under BACEN guidelines or with LGPD compliance obligations, the rollback plan also serves as part of the business continuity documentation that supports regulatory audit requirements. <table> <thead><tr><th>Commitment Type</th><th>Scope</th><th>Trigger</th><th>Timeline</th></tr></thead> <tbody> <tr><td>4-Hour Incident SLA</td><td>On-site engineer response</td><td>Unplanned hardware incident during migration window</td><td>Engineer on-site within 4 hours</td></tr> <tr><td>Rollback Plan</td><td>Return hardware to source facility</td><td>Client or PM decision per agreed conditions</td><td>Per rollback plan (facility-dependent)</td></tr> </tbody> </table>

Brazil has the largest datacenter market in Latin America by installed capacity. The Sao Paulo metro concentration is particularly pronounced: Equinix SP1 serves hyperscale and financial sector tenants within the Sao Paulo metro corridor, while Ascenty (a Digital Realty affiliate) operates the largest number of facilities across the country, with campuses in Sao Paulo, Rio de Janeiro, Campinas, and other cities. Odata and TIVIT round out the major third-party colocation providers. Numerous enterprise clients also maintain on-premise server rooms or single-tenant DC spaces within the Sao Paulo metro area. The practical implication of this ecosystem for server migrations is that the source and destination facilities are almost never operated by the same company. A financial institution moving hardware from a legacy TIVIT facility to a new Ascenty cage must coordinate with two separate operator security processes, two separate smart-hands approval workflows, two sets of shipping and receiving procedures, and two different power configurations (though both will be 220V/60Hz). Without a third-party operator who has established working relationships at multiple facilities, the client must coordinate these two sets of requirements independently, which significantly increases project management overhead and risk. Reboot Monkey resolves this by acting as the single point of accountability across the full migration. We hold the access credentials, manage the facility communications, and carry the migration manifest across operator boundaries. The client's IT team engages with one project lead, not two or more facility operations teams. For clients considering a <a href="/en/data-center-migration/brazil/">full datacenter migration</a> in Brazil rather than a server-by-server move, Reboot Monkey's project scope expands to cover full cage or suite decommissioning, which may involve <a href="/en/rack-and-stack/brazil/">rack and stack</a> at scale, cross-connect decommissioning, and coordination with network carriers operating in the facility. The same cross-operator model applies at the larger scale. Reboot Monkey also provides <a href="/en/remote-hands/brazil/">remote hands services</a> within Brazil's datacenters for ongoing physical support tasks that fall outside a structured migration project, such as visual inspections, cable audits, or hardware swap-outs.

Server migration services in Brazil are used by three distinct buyer categories, each with different priorities and procurement requirements. <strong>Enterprise IT Teams Without Local Datacenter Operations Staff</strong> Multinational enterprises operating in Brazil frequently maintain hardware in Sao Paulo's major colocation facilities but do not have a permanent on-site infrastructure team in the country. When a hardware refresh, facility contract end, or infrastructure consolidation triggers a migration need, the enterprise procurement team requires a qualified third-party operator who can act on behalf of the remote IT team. Reboot Monkey provides this for enterprises headquartered in Europe, the US, or APAC with Brazilian colocation presence. The engagement model is remote-instruction-driven: the client's infrastructure engineers direct the work; Reboot Monkey's field team executes on-site. <strong>Financial Institutions Under BACEN and LGPD Obligations</strong> Brazil's financial sector is one of the most heavily regulated in Latin America. Banks and financial services firms operating under BACEN supervision and LGPD data governance requirements need migration service providers who understand both the physical work and the documentation trail. The 3-business-day LGPD breach notification requirement and the need for audit-grade chain-of-custody records make documentation quality a procurement criterion, not just a service feature. Reboot Monkey's migration handover documents are designed to serve as compliance evidence, not just project records. <strong>Enterprises Consolidating After Facility Contract Expiry</strong> Facility contracts in Brazil, like elsewhere, do not renew indefinitely on favorable terms. When a colocation contract expires and the client chooses to consolidate hardware into a smaller footprint or move to a facility with better power pricing, a physical migration is required. Reboot Monkey can scope a consolidation migration within the Sao Paulo metro or between cities based on the client's timeline, asset inventory, and destination facility access lead times. For mid-market companies that do not maintain any on-site DC staff anywhere, Reboot Monkey's engagement covers the full physical scope. For enterprises that have some in-house capability but need augmentation for a large migration project, Reboot Monkey's engineers work alongside the client's own team under a defined scope split. <a href="/en/contact/">Contact Reboot Monkey</a> to discuss which engagement model fits your situation.