Repricing is a copy

A new listing appears in the marketplace: same region, newer CPU, more RAM, lower monthly price than the box you rented last spring. On a hosting contract, that's a migration project and a retention call with a sales rep.

Here it's two steps. Rent the new server into the same pool. For each container on the old box, POST /api/v1/containers/{id}/copy with target_server_id pointing at the new one: filesystem, packages, data, configuration all come across, and the copy starts on its own. Sync once more the night of the cutover, repoint DNS at the new box, done.

The old rental has no early cancellation and no refund, so you time the move to its rental_end and simply don't renew. Nothing auto-renews, so "don't renew" is an absence of action, not a ticket.

Hardware refresh stopped being a project the day moving a machine became a POST.