10 Things to Know Before Moving to Colocation

Deciding to move your hardware into a colocation facility is a major milestone for any growing business. It represents a shift from managing your own server room or office closet to leveraging enterprise-grade infrastructure. At mxNAP, we believe that making the jump to professional data centres should be a smooth transition that empowers your IT team rather than overwhelming them. Smart web hosting solutions made easy and affordable.

Colocation allows you to keep control over your hardware while benefiting from the power, cooling, and security of a dedicated facility. However, a successful move requires more than just unbolting racks and driving them across town. It demands meticulous planning and a deep understanding of your own environment. Before you start packing the van, here are ten essential things you need to know and prepare for.

1. Complete a Comprehensive Asset Inventory

You cannot move what you do not know you have. It sounds simple, but many IT environments grow organically over years, leading to undocumented hardware and "shadow" applications running on old machines under a desk. Your first step must be a full audit of every physical and virtual asset in your stack.

This inventory should include hardware specifications, serial numbers, warranty status, and the specific applications each server supports. You should also document the physical dimensions of your kit. Knowing if you have 1U, 2U, or 4U servers will dictate how much rack space you need to lease. Don't forget to inventory your networking gear, including switches, firewalls, and load balancers. If you are currently using dedicated servers provided by another vendor, verify which parts of the stack are yours to move and which belong to the provider.

2. Define Asset Criticality and Prioritisation

Not every server is a high-priority asset. When you move to a colocation facility, you need to know which systems must come back online first. Classifying your systems by mission-critical importance allows you to establish a logical migration sequence.

For example, your core database and primary web servers might be Tier 1, requiring the shortest possible downtime. Internal development servers or legacy archive systems might be Tier 3, meaning they can stay offline for a day or two without impacting the business. By setting these priorities early, you can manage stakeholder expectations and create a realistic timeline for the move.

3. Verify the Destination Site is Ready

Before the first rack arrives at the new facility, you must ensure the destination is fully prepared for your arrival. This goes beyond just having a space on the floor. You need to verify that the power density meets your requirements. If you are running high-performance clusters, a standard rack power allocation might not be enough.

Check the cooling capacity and ensure that the airflow in the cold aisles is sufficient for your specific hardware. You should also confirm that the physical security measures, such as biometric access or man-traps, are operational. It is also a good idea to perform a "dry run" of the physical path from the loading bay to your specific cage or rack to ensure there are no height or width restrictions for your equipment. If you need more flexible options before committing to full colocation, you might explore a cloud VPS to bridge the gap during the transition.

4. Review All Contracts and SLAs Carefully

The legal side of colocation is just as important as the technical side. You must review your existing contracts to check for early termination fees or notice periods. More importantly, you need to scrutinise the service level agreements of the new facility.

A good SLA should clearly define uptime guarantees for power and cooling, as well as network availability. Look for details on "Remote Hands" services. If a server fails at 3:00 AM, how much will it cost for a technician at the site to perform a hard reboot? Pricing for these services is usually quoted in £ per hour, and knowing these costs upfront will help you manage your operational budget. Ensure you also read the terms of service to understand your responsibilities regarding maintenance and insurance.

5. Document Dependencies and Network Topology

Systems rarely live in isolation. One of the biggest causes of post-migration failure is a "forgotten" dependency. If you move Server A but forget that it needs to communicate with Server B (which is staying behind or moving later), your application will break.

Map out your network topology and application data flows. This includes internal dependencies, such as DNS, Active Directory, and database connections, as well as external dependencies like API calls or third-party authentication services. Understanding how your data moves through your network ensures that you can reconfigure IP addresses and routing tables correctly once the hardware is racked in the new data centre.

6. Establish a Comprehensive Backup Plan

The physical transport of hardware is the moment of highest risk. Even with the best specialised movers, the vibration and movement of a truck can cause hardware failure, particularly in older spinning hard drives. Before you power down a single machine, ensure you have a verified, off-site backup of all critical data.

This shouldn't just be a backup of the data, but of the configurations and virtual machine images as well. If a physical server fails to boot up after the move, you need the ability to restore that service onto new hardware or into a temporary cloud environment immediately. Testing these backups before the move is not optional; it is a requirement for a professional migration.

7. Create a Detailed Rollback Procedure

Even the best-laid plans can go wrong. A rollback procedure is your "panic button" for when a migration encounters a critical, unforeseen issue. You need to define a "point of no return" for each stage of the move.

If you reach a certain hour and the primary database isn't communicating with the web front-end, do you keep troubleshooting, or do you move everything back to the original site? Your rollback plan should include clear triggers, a list of who has the authority to call for a rollback, and a step-by-step guide on how to revert changes to DNS and routing to restore the original environment.

8. Plan Your Migration Methodology

There are several ways to move your kit, and the right one depends on your budget and tolerance for downtime. The "forklift" approach involves powering everything down, loading it into a truck, and setting it up at the new site. This is often the cheapest but carries the highest risk and longest downtime.

Alternatively, a "phased" migration involves moving systems in groups over several weeks. A "swing" migration involves setting up new hardware at the destination site first, migrating the data over the network, and then decommissioning the old hardware once the new site is live. Each method has different costs, often measured in thousands of £, so choose the one that aligns with your business goals. You can learn more about our mission to provide affordable infrastructure if you need advice on the best approach.

9. Build a Strong Governance and Communication Structure

A colocation move involves multiple stakeholders, from IT and finance to legal and operations. You need a dedicated project manager who has the authority to make decisions across departments.

Communication is key. Everyone involved should know the timeline, their specific responsibilities, and the escalation paths if something goes wrong. Ensure your customers and users are also informed of the planned maintenance window. Clear communication prevents panic and ensures that everyone is working toward the same goal. If you need technical support or have questions about how we handle migrations, you can always contact us for guidance.

10. Assess and Mitigate Risk Thoroughly

Finally, perform a formal risk assessment. This should cover everything from physical security during transport to regulatory compliance. If you handle sensitive financial or medical data, does the transport company meet the required security standards? Is the new data centre compliant with your industry's specific regulations?

Consider the logistics of the move day. Have you insured the equipment for its replacement value during transit? Do you have spare parts (cables, power leads, rails) ready at the new site in case something is lost or broken during the move? Identifying these risks ahead of time allows you to put mitigation strategies in place, turning potential disasters into minor hiccups.

Moving to colocation is a significant step toward a more professional and resilient IT infrastructure. By following these ten steps, you can ensure that your hardware finds its new home safely and that your business continues to run smoothly. Smart web hosting solutions made easy and affordable.