Language
Move from Contabo to Valebyte: dedicated vCPU instead of oversold shared, 10 Gbps unmetered, faster I/O on real NVMe.
Contabo VPS S ($8/mo for 4 vCPU/8 GB) is famous for high CPU steal under load — typical 30-50% during peak hours. The advertised vCPUs are not what you actually get.
VPS S/M/L use shared SSD storage with measurable IOPS contention. Random read/write benchmarks land far below dedicated NVMe equivalents.
Some Contabo locations (Singapore, Tokyo) suffer from network bottlenecks during peak. EU and US-Central usually fine. Hard to test before commit.
Contabo charges €5-10 setup fee on monthly plans. Quarterly/yearly billing waives it but locks you in.
No proper snapshot/restore in real-time. Reinstall is a multi-step process. Console access via VNC works but is dated UX.
Email support primarily during German business hours. Live chat is limited. Response times measured in days, not hours.
No marketing — actual differences. Including where they win.
Total time — 1 hour (small VPS) to 4 hours (TB-scale DB). Zero-downtime possible — steps 4-6.
Contabo control panel → VPS → 'Snapshots' tab. Note: snapshots take significant time and may briefly pause the VPS. For databases, do logical dumps instead.
Contabo doesn't have a built-in DNS service. Your DNS is at your registrar (Namecheap, GoDaddy, Cloudflare, etc.) — export from there.
Do this 24h before cutover. Visitors see new IP within 5 min instead of waiting hours for caches.
Match RAM and vCPU; disk you can grow later. Pay your preferred way (card, SEPA, USDT/BTC, MIR/SBP).
`rsync -avzP --delete /source/ root@new-server:/dest/` for files, configs, Docker volumes, and pre-dumped databases. Test first with `--dry-run`.
Postgres: `pg_dumpall | ssh new-server psql`. MySQL: `mysqldump --all-databases | ssh new-server mysql`. Contabo doesn't offer managed DB. Your database is self-hosted on the VPS, so use standard `pg_dump`/`mysqldump` to migrate to your new Valebyte VPS.
Don't copy `/etc/shadow` blindly across distros — use `useradd` and copy `~/.ssh/authorized_keys`. Verify sudoers with `visudo -c`.
Same Docker Compose, Ansible playbook, or k3s manifest works on Valebyte (Ubuntu 22/24, Debian 12, AlmaLinux 9 are available). No vendor-specific lock-in.
List your existing rules → recreate via `ufw` or `nftables` on Valebyte. Test all inbound services with `nmap` from outside before going live.
Wait for old TTL to expire (5 min if you lowered earlier). Watch traffic with `tcpdump` to confirm requests are arriving on the new server.
Don't shut down the old side immediately. Watch error rates, latency, customer complaints. If something breaks — flip DNS back instantly.
Wait until you're sure nothing references old IPs (cron jobs, webhooks, hardcoded configs in third-party services).
All plans: 10 Gbps, dedicated IP, full root, KVM console
10 Gbps unmetered, multi-region, flexible payment (card, SEPA, crypto, MIR). VPS in 30 seconds.