Moving your VPS to another location

What this is#

Your VPS lives in one of our datacenters, and sometimes the right one changes: your users turned out to be mostly in Europe, latency matters to a trading setup, or you simply picked a location on day one that no longer fits. You order the move from your VPS's manage page for a $4 fee; after payment, a ticket opens with our team and we carry out the migration. Everything on the VPS moves with it, the OS, your applications, your data.

For other products, ask us and we'll see what's possible for your case.

Don't need the data? The move is free#

The $4 fee applies when you want your data migrated with the VPS. If there's nothing on it you need to keep, there's nothing to migrate, and we'll simply re-provision the VPS in the location you want, for free. That covers two common cases:

• You just ordered and picked the wrong location. If you haven't used the VPS yet, contact us and we'll re-provision it where you meant to deploy it, no migration fee.
• You were going to reinstall anyway, or the data on it doesn't matter. Same deal: open a ticket, tell us the location you want, and we'll re-provision it there fresh.

Re-provisioning means the VPS starts clean in the new location, so anything on the disk is gone, and the IP changes either way (see below).

The one big consequence: your IP changes#

IP addresses belong to a location, so a move always means a new IP, we don't offer floating or portable IPs that follow a VPS between datacenters. That's not a footnote, it's the part that needs planning:

• DNS: update the A/AAAA records for every domain pointing at the VPS, and lower the TTL ahead of the move if you want the switch to propagate quickly.
• Mail: if the VPS sends email, update SPF records that name the old IP, and set the reverse DNS (PTR) for the new IP on the Network tab again, rDNS does not follow you.
• Anything pinned to the old IP: firewall allowlists at third parties, API access lists, monitoring, hardcoded IPs in configs or client software.
• SSL certificates keyed to domains are fine once DNS points at the new IP; certificates or validations tied to the IP itself need redoing.

This is the same checklist as any server move, the migration guide covers it in depth.

Deciding whether the move is worth it#

The honest test is measurement, not intuition: check the latency your actual users get to your current location versus the candidate (our Looking Glass lets you ping and download from each location before committing). A 20 ms improvement matters to a game server or trading bot; for a typical website behind a CDN it often doesn't. If you're unsure whether a move buys you anything, open a ticket and describe the situation first.

How to start it#

For a move with your data (the $4 migration):

1. Open your VPS's manage page (https://vpsdime.com/myservices).
2. Use Migrate to Another Location and choose the destination.
3. Pay the $4 fee. A support ticket opens automatically, and our team performs the move, follow that ticket for timing and updates.
4. When the move completes, work through the IP checklist above, DNS first.

For a free re-provision without the data, skip the button: just open a ticket with the VPS and the location you want.

Still need help?#

You can open a support ticket. So we can help on the first reply, it's worth mentioning:

• the VPS hostname or IP and the destination location you have in mind,
• whether latency, compliance, or something else is driving the move,
• whether your setup has IP-sensitive pieces (mail, allowlists) we should know about.

Related questions#

• "Can I move my VPS to a different datacenter?"
• "How much does a location migration cost?"
• "I just ordered in the wrong location, can you fix it for free?"
• "Can I change location without paying if I don't need my data?"
• "Does my IP address change if I move my VPS?"
• "How do I move my VPS closer to my users?"
• "What do I need to update after moving my VPS?"