Feature RequestOtherOpen

Lifetime VPS Location Migration & Higher Usage Limits

Hello Zap-Hosting Team, I’m writing to suggest some improvements for your Lifetime VPS product to make it more flexible and user-friendly for long-term users: Add an Official Location Migration Currently there’s no easy way to move a lifetime VPS to another server location and there's no even ASIA server location on your choices tbh its really hassle (e.g., for you Asian Customers like me). This means many users end up needing to purchase a new VPS just to get a different region/location, which is inefficient and costly. 👉 Please consider adding an migration feature so we can switch server regions without having to buy a new server. Increase Resource / Usage Limits The existing limits (e.g., CPU/usage caps) can be too restrictive — for example, some VPS can get locked during basic tasks like OS installation or heavier workloads. Higher available limits or optional upgrade tiers would greatly improve usability and reduce disruptions when working on projects. Overall, these changes would make the Lifetime VPS product more practical and satisfying for customers who want long-term reliability and flexibility without unnecessary extra purchases.

Originally posted by Joms on our previous feedback board.

Ffeaturebase-import10 Jan 2026

Comments (12)

featurebase-import10 Jan 2026, 13:18

Additionally: Also, it doesn’t make sense that if the VPS is locked at a 550% limit, upgrading your server would actually help if the system still enforces that same hard cap. If the limits don’t increase with upgrades, then users will still hit the same ceiling (e.g., getting locked even during basic tasks like installing an OS), which defeats the purpose of upgrading in the first place and makes the whole upgrade option feel pointless. I hope you can clarify and adjust how these usage limits work so that upgrades actually provide meaningful increases in performance and capacity.

Originally posted by Joms on our previous feedback board.

ZAP

Official response

24 Mar 2026, 15:44

Plans are in place to get this changed from what I seen. However there is no ETA.

featurebase-import17 Jun 2026, 16:11

Transparency about this before you even purchase more CPU would be a good first step and pretty simple to implement in my honest opinion.

Originally posted by WilliDieEnte on our previous feedback board.

ZAP

Official response

18 Jan 2026, 01:54

We’re checking this out! 🔍 Our team is reviewing the details to see how it fits into our roadmap.

ZAP

Official response

9 Mar 2026, 23:39

Thanks for sharing your ideas on this. Regarding the location migration, I'm afraid this isn't something we can offer. Our host systems are set up in Proxmox clusters, which are location-specific. Proxmox doesn't support migrating a server from one cluster (location) to another Cluster in a different location. We have to keep them separate to maintain system stability. I know that's not the answer you were hoping for. As for the resource limits, I've sent a request to our developers to get more details on what's possible here. We'll follow up once we have more information.

featurebase-import10 Mar 2026, 01:50

Hoping you can do something about that both location and usage limit to be honest as a VPS owner having big project so hassle to just buy new vps for the same location only you can't even reach your people over the country because of that, and about the limits even you having big system specs still useless it kinda doesn't make sense of the upgrade because after you deploy your system after just an hr or minutes server gets suspended see the hassle upgrade kinda really useless in this part, hope you fix

Originally posted by Joms on our previous feedback board.

ZAP

Official response

10 Mar 2026, 17:41

I can fully understand, tomorrow we are doing an internal meeting with the board and it will be discussed in regards to what changes we are able to make.

featurebase-import16 Mar 2026, 23:30

Maybe you could offer the option to change the location with data loss and just redeploy the vps in another location on upgrade.

Originally posted by rexum on our previous feedback board.

ZAP

Official response

24 Mar 2026, 15:47

That is an idea possibly for the future, however due to the high usage of migrations with disk and cpu it is not ideal for host systems that have active monitoring to provision new systems for customers that may already be waiting for space to provision their orders. This is quite a large task for us as its fully custom coded by ourselves such would require legal and modifications to existing packages. I have shared your idea with the team, it will be looked into if its possible to integrate.

featurebase-import24 Mar 2026, 20:31

More usage limit over 550% is a 10/10 must-have

Originally posted by denizlebaguette on our previous feedback board.

featurebase-import11 Aug 2026, 08:56

🙏 Please reconsider 550 cap and/or other constraints with higher tiers, I would love to upgrade my server again as I’ve been really happy with zaphosting so far. I've only just learnt about this after reaching 12 cores and feel like I've wasted a bit of money or would not to be worth upgrading further

Originally posted by Apidaex on our previous feedback board.

ZAP

Official response

28 Sep 2026, 17:39

We're reopening this for ZapX: moving a VPS to another location isn't available yet, so we're keeping this request open for now. On the usage limits: ZapX VPS no longer have the old strict limits like the 550% CPU cap. You can use the resources you pay for, and only our general fair use policy applies.

Timeline

All important changes at a glance.

Official response from the ZAP team added.

From ZAP

28 Sep 2026

17:39

Status changed from “Implemented” to “Open”.

From ZAP

28 Sep 2026

17:39

Feedback

Do you have another suggestion?