ServerBudget

VPS Upgrade vs Downgrade: Four Official Paths and What "Change Plan" Actually Means

By Marcus Reid · Published Nov 18, 2026 · Last updated Nov 18, 2026

Short answer: On four official pages read on 2026-11-18, "upgrade" and "downgrade" are four different operations: OVHcloud upgrades in one click with a quick reboot but sends downgrades to a new plan and a data transfer; DigitalOcean lets CPU and RAM move both ways but powers the Droplet off and never shrinks the disk; Vultr performs an in-place plan change only when the host has room and keeps the IP in that case, otherwise it is a snapshot-and-new-server migration with a new IP; Hetzner rescales up or down inside the same architecture and refuses any disk downgrade. A plan table that lists only sizes shows none of these paths.

Comparison table: plan change paths, four providers (checked 2026-11-18)

Every cell comes from an official provider page opened on 2026-11-18. Where the page printed no figure or statement, the cell says so and names the pages read.

ProviderUpgrade path as printedDowngrade path as printedReboot / power stateData and IP as printedDisk limit as printedOfficial source (opened 2026-11-18)
OVHcloud (US)"Upgrade your VPS resources with a single click -- just a quick reboot required, with no data migration or configuration changes needed"; "without changing servers" [S1]"You will need to subscribe to a new plan, transfer your data, then cancel your old service" [S1]"just a quick reboot required" for upgrade; no downgrade reboot statement on the page read [S1]No manual data migration on upgrade; downgrade requires transferring data; IP behaviour on either path: Read not available on the page read [S1]Read not available — the VPS page read prints no disk shrink or disk floor rule [S1]us.ovhcloud.com/vps/ [S1]
DigitalOceanResize changes CPU and RAM in either direction; a second option also "permanently increases the size of a Droplet's disk" [S2]"CPU and RAM only" can decrease; resize is allowed only to a plan with "equal or greater amount of disk space as the original Droplet" [S2]Power off before resizing in the control panel or CLI; API resize powers down automatically; "Droplets may change hypervisors during a resize" [S2]Backup recommended before resize because filesystem changes can lose data; IP behaviour on resize: Read not available on the page read [S2]"You cannot decrease the size of a Droplet's disk"; volumes are suggested as removable storage instead [S2]docs.digitalocean.com/products/droplets/how-to/resize/ [S2]
VultrConsole Settings, Change Plan, Upgrade; an in-place upgrade is used when the physical host has room [S3]Read not available — the docs page read covers in-place upgrade and migration to a new host only; the docs sitemap was searched and no downgrade-in-place article was found [S3][S4]"Your server will restart with the new plan"; migration path requires snapshot, new deployment and removal of a rescue ISO [S3][S4]"The server's IP address will remain the same after an in-place upgrade"; a snapshot-based migration gives the new server "a new IP address" [S3]Upgrading to a larger plan increases the virtual disk, after which the partition and file system must be expanded manually; no disk shrink path printed on the pages read [S4]docs.vultr.com/how-to-upgrade-your-plan-without-reinstalling [S3]; docs.vultr.com/resize-disk [S4]
Hetzner"You can also rescale to and from a plan with shared resources or up- and downgrade to another plan"; the plan change is done in Hetzner Console [S5]Rescale down is possible only to a plan whose disk is at least as large as the current disk; "we do not offer disk downgrades" [S5]Reboot or power state on rescale: Read not available — the FAQ read prints no rescale reboot statement [S5]CPU type may change during rescale; same architecture is required; IP retention on rescale: Read not available, though a Primary IP can be reassigned to a new server if auto-delete is off [S5]"You can only rescale to server plans with a disk size equal to or larger than the current disk"; when scaling up you may keep the current disk size to preserve a later downgrade; partition must be enlarged manually via Rescue System [S5]docs.hetzner.com/cloud/servers/faq/ [S5]

A downgrade that ends in a new plan still leaves the disk floor to deal with; the VPS downgrade rollback page follows what happens after the plan change, including the copy to a smaller disk and the address rules on the replacement machine.

A range change is a different question from a plan change; the VPS 2027 config shift page records why the same configuration may require a different model when a provider replaces a range.

None of the four "upgrade" paths is a single atomic change: one is a control-panel click with a reboot, one is a CPU/RAM dial that may move the machine to another host, one is conditional on spare host capacity, and one is a plan rescale that cannot cross architectures.

Four findings a plan table cannot print

  1. "The four official pages use one word — upgrade, resize or rescale — for four different operations: a one-click in-place resource change with a quick reboot at OVHcloud, a CPU and RAM change that may move the Droplet to another hypervisor at DigitalOcean, an in-place plan change that keeps the IP only when the host has room at Vultr, and a plan rescale that cannot cross architecture types at Hetzner." — Angle: same feature name, different operation. A plan list prints the word; the operation is only visible in the manual.
  2. "Vultr says the IP stays the same after an in-place upgrade but becomes a new IP after a snapshot-based migration, OVHcloud prints no IP statement for either path, DigitalOcean warns that a resize may change hypervisors, and Hetzner says a Primary IP can be moved to a new server only when auto-delete is off; four official pages print four different kinds of address claim." — Angle: the same item printed with a different nature by each provider. No single "IP is kept" line can be copied across them.
  3. "DigitalOcean's resize moves CPU and RAM in both directions but permanently enlarges the disk when disk is included, Hetzner lets a customer keep the old disk size at scale-up so a later downgrade stays possible, OVHcloud's downgrade is a new subscription with a data transfer, and Vultr's Change Plan article documents only the upward direction; a buyer comparing the word downgrade is comparing a dial, a ratchet, a migration and an undocumented path." — Angle: same feature name, different operation. The word is identical; the work behind it is not.
  4. "OVHcloud asks for a quick reboot, Vultr says the server restarts with the new plan, DigitalOcean requires a power-off before resize and says the Droplet may change hypervisors, and Hetzner's rescale FAQ prints no reboot statement; these are four different kinds of downtime, so the table does not print one downtime number." — Angle: the same item printed with a different nature by each provider. A shared "downtime" column would hide the conditions.

Where the first ten result slots stop (Google US, udm=14, gl=us, checked 2026-11-18)

  1. VPS Hosting Service — "How to Upgrade or Downgrade Your VPS Plan" (vpshostingservice.co knowledgebase): a single vendor's control-panel steps; no cross-provider paths, no reboot or IP conditions side by side. This page supplies the four official paths.
  2. Flipper Host — "How do I upgrade or downgrade my service?" (flipperhost.com billing knowledgebase): one billing workflow, not a comparison of what an upgrade means on four platforms. This page separates plan change from disk change.
  3. Reddit r/hetzner — "Can I downgrade to a cheaper VPS?": only the SERP title was read; body read not available on three paths — old.reddit returned a network-policy block, search.json returned a network-security block, and the Google cache attempt returned a cookie-consent page. No community claim is used here.
  4. Flipper Host — "How do I upgrade or downgrade my service? - Kennisbank" (flipperhost.com, Dutch knowledgebase): the same vendor workflow in another language; no official provider documentation from the providers compared here. This page quotes only provider documentation.
  5. QHoster — "How to upgrade or downgrade your VPS server hosting plan" (qhoster.com clients how-to): one hosting panel route; no statement about disk floors or address behaviour. This page prints both.
  6. VPSCost — "Data, Downtime, IP and Downgrade Limits (2026)" (vpscost.com blog): the title promises the same fields but the result is a third-party roundup, not a provider manual. This page uses only official pages opened on 2026-11-18.
  7. GreenCloud — "How do I upgrade or downgrade my service? - Base de conocimientos" (greencloudvps.com billing knowledgebase): another single-vendor billing article; no cross-provider path comparison. This page compares four vendors' own words.
  8. QHoster — second "How to upgrade or downgrade your VPS server hosting plan" result (qhoster.com): a duplicate result for the same host's article; no additional fields. This page does not repeat a vendor's workflow as evidence.
  9. RazeHost — "Como fazer Upgrade/Downgrade na VPS" (video result, RazeHost): a Portuguese-language clip title with no on-page text of provider conditions. This page uses text published by the providers.
  10. No tenth natural web result was present on this SERP: the Google result page returned nine organic entries plus an AI overview; the tenth slot is recorded as absent rather than filled with an ad or a video card. This page lists every organic entry actually returned.

Cross-check with a page already on this site

An existing page on this site, [VPS downgrade rollback](/cheap-vps-downgrade-rollback), records that DigitalOcean forbids shrinking a Droplet disk and that Hetzner refuses disk downgrades while allowing rescale to a plan with an equal or larger disk. The OVHcloud official page read today adds a third shape: its downgrade is not a dial at all but a new subscription, a data transfer and cancellation of the old service. The site's existing facts and today's OVHcloud fact are both official; together they show that one word, downgrade, covers a CPU/RAM dial, a disk floor and a service replacement.

What the manuals print beyond the plan name

DigitalOcean's resize guide recommends a snapshot before resizing and gives separate procedures for the control panel, CLI and API; it also says a resize can take longer when more disk data has to move over the network. [S2]

Vultr's upgrade article says an in-place upgrade takes several minutes and needs spare capacity on the physical host; when that capacity is absent, or when the server type changes, the documented route is a snapshot, a new deployment and a new IP. [S3] Its file-system guide explains that a larger plan may leave the old partition unchanged and that the file system must be expanded by hand from a rescue environment. [S4]

Hetzner's FAQ says the CPU type may change on rescale because hardware is allocated by availability, and that rescale is restricted to the same architecture type. [S5]

OVHcloud's VPS page says an upgrade needs no data migration or configuration changes, while a downgrade needs a new plan and a data transfer. [S1]

Sources

Marcus Reid
Systems Architect & VPS Infrastructure Analyst

Marcus has been working with virtualized server infrastructure since 2015, deploying and benchmarking VPS and cloud instances across DigitalOcean, Vultr, Hetzner, OVHcloud, Contabo, RackNerd, Hostinger, and the major hyperscalers. His work focuses on the gap between what providers advertise and what actually happens when you deploy a real workload. He verifies every price and specification against official provider pages before publication.