How to Migrate to Kerit Cloud Today — and Do It Cheap
A practical plan for moving any bot, server, database or VPS to Kerit Cloud with zero downtime — and knocking 10% off your first order with MIGRATE10, our never-expiring welcome code.
On this page
- MIGRATE10: our all-time welcome discount
- What you can bring over
- Step 1: Take a five-minute inventory
- Step 2: Provision on Kerit Cloud (free first, if you like)
- Step 3: Move your data
- Step 4: Recreate configuration and test
- Step 5: Redeem MIGRATE10 at checkout
- Step 6: Cut over and clean up
- Frequently asked questions
Switching hosts always feels like more work than it is. In practice, most bots and small servers move in well under an hour, and you can do it without your service ever going dark. This guide is the host-agnostic version of our migration playbook: it works whether you’re coming from Replit, Heroku, Railway, Render, a shared panel, or another VPS — and it applies to every product we run, from Discord bots to full KVM VPS.
And because a move is a good moment to save money, every first-time customer gets 10% off their first order with a code that never expires. More on that in a second.
Tip: If you only want the discount, skip to Redeem MIGRATE10 at checkout. If you want the clean, no-downtime move, read the whole thing.
MIGRATE10: our all-time welcome discount
MIGRATE10 is a standing offer, not a flash sale. Here’s exactly what it does:
| Detail | What it means |
|---|---|
| 10% off | A straight 10% off your order total. |
| Works on every service | Discord bots, Telegram bots, Lavalink, Minecraft, VPS and databases — anything in the catalogue. |
| First-time customers | Valid on your first order on the account, so it’s built for people moving in. |
| Never expires | No countdown, no “ends Sunday”. Use it whenever you’re ready to migrate. |
Because it’s a percentage off the whole order, MIGRATE10 is worth the most when you commit to a longer billing term up front — a yearly plan takes 10% off twelve months at once.
Note:
MIGRATE10is a first-order welcome code. If you just want to test the water first, you can claim a free server with no card at all, then applyMIGRATE10when you upgrade to a paid plan — the discount waits for you.
What you can bring over
Migrating to Kerit Cloud isn’t limited to one kind of workload. The same move works for:
- Discord bots — discord.js, discord.py, JDA and friends. See Discord bot hosting.
- Telegram bots — aiogram, Telethon, grammY and more. See Telegram bot hosting.
- Lavalink nodes — bring your own config or let us run it. See managed Lavalink and self-managed Lavalink.
- Minecraft servers — Paper, Fabric, Forge, whole networks. See Minecraft hosting.
- Databases — MySQL and PostgreSQL, with daily backups. See managed databases.
- Anything else — a full Ryzen KVM VPS with root, so you run whatever you like.
Every plan sits behind the same 17+ Tbps DDoS protection, so you don’t lose anything on the security side by moving.
Step 1: Take a five-minute inventory
Before you touch anything, write down what your current service depends on. For a bot or app that’s usually:
| Item | Where to find it |
|---|---|
| Runtime and version | package.json engines, .python-version, runtime.txt, or panel settings |
| Start command | Procfile, .replit run =, or the panel’s startup field |
| Environment variables | The old dashboard’s Secrets / Config Vars / Variables |
| Data files | SQLite files, JSON “databases”, uploaded assets |
| External database | Any Postgres/MySQL you connect to |
| Scheduled jobs | Cron, schedulers, add-ons |
Copy the environment variable names and values somewhere private — you’ll recreate them on the new host. If you’re coming off a general-purpose platform, our deeper guides on moving a Discord bot and moving a Telegram bot cover the platform-specific details.
Step 2: Provision on Kerit Cloud (free first, if you like)
You don’t have to pay to test the move. Two ways in:
- Free tier. Claim a free server — 256 MB RAM on AMD EPYC, NVMe storage, no sleep mode, no card. Perfect for confirming your bot runs on our stack before you commit.
- Paid plan. If you already know the size you need, order it directly and apply
MIGRATE10at checkout (Step 5).
Either way, deploy your code but don’t point production traffic at it yet. The goal is to have the new instance fully working in parallel with the old one.
Step 3: Move your data
Filesystems on some platforms reset on every deploy, so your database is the thing to be careful with. The general pattern:
# PostgreSQL
pg_dump "$OLD_DATABASE_URL" --no-owner --no-acl -Fc -f service.dump
pg_restore --no-owner --no-acl -d "$NEW_DATABASE_URL" service.dump
# MySQL
mysqldump --single-transaction -h old-host -u user -p appdb > app.sql
mysql -h new-host -u user -p appdb < app.sql
Every paid plan includes a database, and if a migration looks hairy, open a ticket and the team will do the dump-and-restore with you — that’s included, not an add-on. For Minecraft worlds, stop the old server, zip the world folder, and upload it; for VPS-to-VPS moves, rsync over SSH is your friend.
Step 4: Recreate configuration and test
Recreate every environment variable from your inventory on the new instance, then start it and watch the logs. Check the things that break most often:
- The bot actually logs in and comes online.
- Commands respond (test in a private server or DM first).
- Database reads and writes land in the new database.
- Scheduled jobs fire.
If you run a bot, keep the old instance running during this test so users are never without it. You’re aiming for a moment where both work and you simply switch off the old one.
Step 5: Redeem MIGRATE10 at checkout
When you’re ready to pay for the new plan:
- Add your plan (and billing term) to the order.
- On the checkout page, find the discount / promo code field.
- Enter
MIGRATE10and apply it — you’ll see 10% come off the total before you pay. - Complete payment.
Important:
MIGRATE10applies to your first order on the account, so enter it on that first purchase. If you started on the free tier, it’s the order where you upgrade.
Paid plans also come with a 3-day money-back guarantee, so the discounted first payment is low-risk while you finish the cutover.
Step 6: Cut over and clean up
Once the new instance has proven itself:
- Stop the old instance (don’t delete it yet — keep it as a fallback for a day or two).
- Update anything that points at the old host — DNS for a web dashboard, a Minecraft server address, webhook URLs.
- Remove old platform glue you no longer need — keep-alive pingers, sleep workarounds, hard-coded platform paths.
- After a day of clean running, cancel and delete the old service so you’re not double-paying.
That’s it. The whole thing is designed so there’s never a window where your users are offline.
Frequently asked questions
Does MIGRATE10 expire? No. It’s a permanent welcome code for first-time customers — use it whenever you migrate.
Can I use MIGRATE10 on any product? Yes — it applies across the whole catalogue: Discord and Telegram bots, Lavalink, Minecraft, databases and VPS.
I’m already a customer. Can I use it? It’s a first-order code for new accounts. If you’re an existing customer, the referral program is the better way to cut your bill.
Can you help me migrate? Yes. Open a ticket from your billing dashboard, or ask in our Discord, and the team will help with data exports and getting your service live.
Ready to move? Claim a free server to test the waters, or order any plan and drop MIGRATE10 in at checkout.