Signing a colocation contract is the easy part. The real work happens in the weeks between signature and go-live, and that is where most avoidable problems start.

A server arrives with the wrong power plug. A carrier circuit is ordered too late. An engineer is turned away at the security desk because their name isn’t on the access list. None of these are facility failures. They are preparation failures, and each one can delay go-live by days.

This colocation move-in checklist covers what to prepare before your racks arrive, from colocation onboarding to cut-over day (the day you switch live systems to the new site). It assumes you have already sized your deployment. If not, start with our first-time buyer’s guide to data center capacity planning. If you are moving live systems from another site, pair it with our guide to data center migration with minimal downtime.

1. Confirm Your Power Plan Down to the Outlet

Power causes the most move-in surprises. Check:

• Power per rack: compare the contracted allocation (kW or kVA) with the measured draw of your equipment, not its nameplate rating (the maximum rating printed on the device label).
• A and B feeds: plan which power supply on each device goes to which feed, so losing one feed never takes a device down.
• Load per feed: keep each feed at or below 50% of its capacity. If one feed fails, the other has to carry the full load, and an overloaded feed can trip its breaker and take down both sides.
• Single-corded equipment (devices with only one power supply): replace it, add a rack-level transfer switch (a switch in the rack that moves the device to the backup feed automatically), or accept the risk knowingly.
• Outlets and plugs: check the outlet types on the rack PDU (the rack’s power strip) against your power cords. Mismatched plugs are a classic day-one delay. This is a common catch in Indonesia: equipment moved from an office server room often comes with local Type C/F wall-plug cords, while rack PDUs use IEC C13/C19 outlets. Order the right cords before you ship.
• Headroom (spare capacity): don’t fill a rack to its full allocation on day one.

2. Plan the Rack Layout

Draw a rack elevation (which device goes in which rack unit) before anything ships. It should cover:

• Heavy equipment at the bottom of each rack
• Front-to-back airflow, with every device drawing from the cold aisle (the aisle that feeds cool air to the front of the racks)
• Blanking panels (covers for empty rack slots) for empty rack units
• Space for patch panels, cable managers, and growth
• Rails and mounting hardware for every device

3. Order Network Connectivity Early

Network usually has the longest lead time. Start several weeks before go-live. Typical lead times at our Jakarta facility are 5 business days for a standard cross-connect (or within 24 hours of the order for an expedited one) and 1 business day for access enrollment and induction. Carrier circuits take longer and depend on the carrier, so order them first. What to order and confirm:

• Carriers: confirm your providers are present in the facility and order circuits early.
• Cross-connects: list every cross-connect you need, with both ends defined. Our guide to how cross-connects work explains the basics.
• Letters of authorization (LOA): a letter allowing the data center to connect to another party’s equipment. Request them from the other party early. They are a frequent source of delay.
• Internet exchange ports: if you plan to peer, order a port on EPIX and register your network on PeeringDB.
• Redundancy: use two carriers or diverse paths (physically separate cable routes) for anything critical.

4. Prepare IP and Network Configuration

The physical network can be ready and still fail on the day if the configuration isn’t. Prepare your IP plan, routing and BGP sessions, firewall rules, and VPNs in advance. Lower DNS time-to-live values (how long other systems cache your DNS records) well before the move, and set up an out-of-band management connection (a separate backup connection for managing devices). Pre-stage device configurations before shipping, so installation day is only about racking and cabling.

5. Arrange Site Access and Onboarding

Every data center controls access tightly. Before move-in:

• Submit the names and ID details of everyone who needs access, including contractors. At our Jakarta facility, local staff can use a KTP or SIM, and foreign staff a passport or KITAS. For privacy, only the last four characters of the ID number are entered into our access system
• Decide who can enter unescorted and who can authorize visits
• Schedule biometric enrollment and the site induction (a site safety briefing)
• Learn the booking process for visits, including urgent out-of-hours access

6. Plan Shipping and Receiving

When moving servers to a data center, confirm with your provider:

• Loading dock hours, booking, and vehicle size limits
• Whether the facility will receive and hold shipments, and for how long
• Labeling requirements (company name, rack or cage number, reference)
• Packaging rules: many facilities don’t allow cardboard or wooden crates in the data hall
• Insurance: colocation contracts typically make you responsible for insuring your own hardware
• Imported hardware: build customs clearance into your timeline and keep the commercial invoice and packing list ready. Clearance time varies, so don’t schedule delivery for the day before go-live.
• Delivery timing in Jakarta: check which hours trucks can reach the site and book the loading dock to match. A missed slot can push delivery back a day.

7. Define the Remote Hands Scope

Remote hands lets on-site technicians work on your equipment for you. Agree in advance which tasks are included, response times, who can raise requests, and how completed work is confirmed. Write a short runbook (step-by-step instructions) for common tasks. Remote hands are only as accurate as the instructions they receive.

8. Run Cut-Over Day From a Written Plan

Uptime Institute’s Annual Outage Analysis 2026 found that failure to follow established procedures is the leading driver of human-error outages. A written cut-over plan is the simplest protection. It should include:

• A step-by-step sequence with an owner for each step
• Go/no-go checkpoints (points where you decide to continue or stop) and a rollback plan
• Contact details for carriers, the provider’s operations team, and vendors
• A maintenance window outside peak business hours

9. Verify, Then Document

A system that is powered on is not necessarily ready. Before declaring the move complete, check that:

• Every device is on both A and B feeds where intended
• Redundant network links fail over correctly
• Monitoring and alerting work from the new site
• Applications pass functional tests
• Rack power draw is within the allocation

Then document the final state: rack elevations, a cross-connect register with circuit IDs, power per rack, access lists, and remote hands runbooks. This makes every future change faster and safer.

What you prepare vs. what we handle

Our Customer Care team is your onboarding contact from signature to go-live.

Conclusion

A smooth colocation move-in depends less on the facility than on preparation. That means a power plan matched to real equipment, a rack layout drawn before shipping, network ordered early, access arranged in advance, and a cut-over run from a written plan. Work through this colocation move-in checklist before go-live and most day-one problems never happen.

CTA: Planning a move into colocation in Jakarta? Talk to our team about preparing your power plan, rack layout, and cross-connects before your first rack arrives.