Turkey (Türkçe) 
The hard part of moving a server is not loading it onto a truck. The real risk of a move is on the network side: the IP address changes, DNS records are updated, IP-bound licenses become invalid, e-mail sending stops for lack of rDNS. A well-planned move ends with a few hours of downtime; an unplanned one turns into a patchy correction process that lasts for days. This guide ties the move from the office or an old data center to the new facility to a step-by-step checklist.
In both cases the process goes through the same five stages: inventory, dependency analysis, physical preparation, cutover and commissioning, verification.
For every device you will move, put the following in writing: make/model, serial number, U height, chassis depth, number of power supplies, estimated watt consumption and number of network ports. This list is needed both for rack planning and for insurance.
Then draw up a dependency map of your systems. Which service runs on which server, which server connects to which? If you move the application server and leave the database behind, the latency between them can make the application unusable. Interdependent systems should be moved in the same window together.
If you are struggling with the U and depth calculation, see the rack unit calculation guide, and for the power budget the power and PDU guide for details.
In the great majority of moves the IP address changes. The list of everything that touches the IP is usually longer than expected:
| Item | What to do | When |
|---|---|---|
| DNS A / AAAA records | Lower the TTL to 300 seconds; update the IP after the move | T-2 days |
| rDNS / PTR record | Request it from the provider for the new IP — if it is missing, e-mail sending is blocked | T-1 day |
| SPF record | Add the new IP; remove the old one after the switch | T-1 day |
| IP-bound licenses | Reactivate panel, database and application licenses | T-0 |
| Firewall whitelists | The new IP is notified to payment providers, banks, API and business partners | T-7 days |
| SSL certificates | Unaffected if bound to the domain name; renewed if bound to the IP | T-7 days |
| Monitoring and backup targets | Update the monitoring agents and backup server addresses | T-0 |
If you have your own IP block and announce it with BGP, most of these problems disappear; the addresses move with you. For block leasing options, see the IP leasing page for details.
You have two options for delivery: ship it and leave the installation to our team, or come to the facility with your 24/7 physical access right and install it yourself. Setup is free in both cases.
A move is the moment when hardware failure is most likely. Before pulling the plug:
| Time | To do |
|---|---|
| T-14 days | Inventory and dependency map; rack/plan selection; power budget approval; contract |
| T-7 days | New IP allocation; third-party whitelist applications; sourcing rail kits and packaging; downtime window announcement |
| T-2 days | Lower DNS TTLs to 300 seconds; take a full backup and run a restore test |
| T-1 day | rDNS and SPF requests; cabling photos; labelling; final incremental backup |
| T-0 | Clean shutdown; removal and transport; rack mounting; power and network connection; first boot over KVM |
| T-0 +2 hours | RAID and disk health check; BIOS clock; network test; DNS update; license activation |
| T+1 day | Return TTLs to normal; remove the old IP from SPF; verify monitoring and backup jobs; e-mail delivery test |
When installation is finished, the first boot should be watched over KVM throughout. Thanks to the BIOS-level remote access provided free in all plans, you can see the POST screen, RAID controller messages and boot order without being on site. Check in order:
We shared what the latency values should be in the Turkey location ping guide article: 1–8 ms is expected from within Istanbul and 5–15 ms from Anatolian cities.
How much downtime does a move cause?
For a single server the typical window is 4–8 hours: shutdown, transport, installation and verification. DNS propagation takes an additional 5–10 minutes if the TTL has been lowered.
Is a move without downtime possible?
When a physical server is moved on its own, zero downtime is not possible. To eliminate downtime, a copy is first brought up on a temporary dedicated server at the new location, traffic is switched to it, the hardware is moved and then you switch back.
Is migration support charged for?
No. Setup and migration support from your old data center are free; rack mounting, cabling and IP configuration are included.
Can I ship my server?
Yes. Share the inventory list before shipping; on receipt, installation is done by our team. Alternatively you can install it yourself with your 24/7 physical access right.
Can I keep using my old IPs for a while?
That depends on your old provider's policy. If possible, planning a short overlap period on both sides provides a safe buffer until DNS propagation is complete.
What should I do if I have no hardware?
If you have no hardware to move, starting with a dedicated server is faster. The comparison of the two models is in the TCO guide.
Rack mounting, cabling and IP configuration included · Typical commissioning 24 hours
Server Colocation Rack Rental
