PRIVATEBYTE

Migration

Move your workload.
Keep your way back.

VPS migration planning

Plan your move to PrivateByte alongside your existing server. Compare the resources, test the new deployment and switch traffic when the application is ready.

Comparison only. No server is created or charged.

Keep your existing serverTest before cutoverPlan your rollback
PRIVATEBYTE CLOUDExample move
Rollback path Keep the old server and a tested backup until validation is done.

Overview

A move is easier with a sequence.

Start with the server you have and everything it depends on. The comparison wizard matches resources. This guide covers the rest: testing, the final sync and a way back.

Write down what you run

Record CPU, peak memory, disk use and traffic. Add databases, scheduled jobs, domains and anything that calls out or in.

Test before you switch

Deploy beside the current server. Check the application on the new address before you change public DNS or cancel anything.

Keep a copy you can restore

Take independent backups and test the restore. A rollback must account for anything written after the switch.

Workflow

Compare first. Move with a plan.

The wizard starts from your current provider and server specification. Comparing does not create or charge for a server.

01

Match your current server

Enter your resources and monthly price in the comparison wizard. Review the proposed plan and any differences in storage or software needs.

02

Build and validate alongside it

Provision the target when you are ready. Restore the application, test its dependencies and agree a cutover window if a final sync needs downtime.

03

Switch, monitor, then retire

Change routing only after validation. Watch errors and data integrity, keep a rollback route, and cancel the old service only when the move is done.

Cutover checklist

Match the server, then make the application ready. Timing and any assistance depend on the source system and workload.

Before the move

Confirm software versions, disk capacity, DNS access and any IP-bound licences or allowlists. Write the restore procedure, then test it on the new server.

At cutover

Decide how to pause writes or replicate, then run a final consistent sync. Test HTTPS, scheduled jobs, queues and integrations.

After the switch

Watch the new service while cached DNS records expire. Keep the old server until validation is done, and reconcile new writes before any rollback.

Pricing

Compare the target, beyond the price.

Monthly pricing in USD. Unmetered transfer, subject to the acceptable use policy.

Flare

Small projects & personal apps

$5.99/ month

Billed monthly. No setup fee.

Deploy Flare
CPU
1 vCPU
Memory
2 GB
SSD storage
25 GB
  • Unmetered traffic
  • Daily backups & dedicated IPv4

Orbit

Websites & lightweight services

$7.99/ month

Billed monthly. No setup fee.

Deploy Orbit
CPU
2 vCPU
Memory
4 GB
SSD storage
50 GB
  • Unmetered traffic
  • Daily backups & dedicated IPv4

Comet

Growing applications

$15.99/ month

Billed monthly. No setup fee.

Deploy Comet
CPU
4 vCPU
Memory
8 GB
SSD storage
100 GB
  • Unmetered traffic
  • Daily backups & dedicated IPv4

Pulsar

More demanding workloads

$27.99/ month

Billed monthly. No setup fee.

Deploy Pulsar
CPU
6 vCPU
Memory
16 GB
SSD storage
200 GB
  • Unmetered traffic
  • Daily backups & dedicated IPv4

Quasar

Heavy, memory-hungry workloads

$49.99/ month

Billed monthly. No setup fee.

Deploy Quasar
CPU
8 vCPU
Memory
32 GB
SSD storage
400 GB
  • Unmetered traffic
  • Daily backups & dedicated IPv4

Nebula

Our largest plan

$89.99/ month

Billed monthly. No setup fee.

Deploy Nebula
CPU
12 vCPU
Memory
64 GB
SSD storage
800 GB
  • Unmetered traffic
  • Daily backups & dedicated IPv4
These are target VPS plans, not an automatic match. Compare your current resources and dependencies in the migration wizard.

Included

DDoS protectionDaily backupsDedicated IPv4Root & console
All included features

DDoS protection

Always on. No scrubbing fee, no attack-time surcharge.

Daily backups

Automated, seven-day retention, restore them yourself.

Snapshots

Save a point to return to. Up to 7, free.

Dedicated IPv4

One public IPv4 of your own.

Browser VNC console

Console access from your browser, even without SSH.

Unmetered traffic

No per-GB charge, subject to the Acceptable Use Policy.

SSH key at deploy

Your public key is on the machine at first boot. No password sent by email.

Crypto payments

Pay in crypto at checkout, not only by card.

Telegram control

Servers, balance, invoices and tickets from your phone.

Answers

A few things to know.

Will opening the wizard charge me?+

No. The wizard compares your current specification and price. A server order is a separate step you review before paying.

Can you promise zero downtime?+

No. Cutover depends on your application, DNS caching and how writes are synchronised. Plan a maintenance window if your workload needs one.

Is migration help free or automatic?+

This page promises no free, automatic or unlimited migration work. Tell us the source system, operating system and workload, and we will confirm scope and any cost.

Should I cancel my old server first?+

No. Keep it through testing and the validation period. Hold backups independently of either server.

Can I just point DNS back?+

Only if the old application and data are still usable. If the new server took writes, reconcile them first. DNS caches can send traffic to both addresses for a while.

Start with the server you already have.

Compare your resources before deciding how to move.

Compare my server