Migrating to a new VPS
Moving servers has two halves: your licence, and your data. IP pin & migrating VPS covers the licence. The data half is a support job — message @roitrack on Telegram and we’ll run the move with you.
Plan it for a quiet window. It’s straightforward, but it isn’t instant.
Do this yourself, a day ahead
Lower the TTL on your DNS records to 300 seconds.
This is the one step that has to happen early, and the one that causes real damage when it’s skipped. TTL is how long the internet caches your DNS. If yours is still set to 24 hours, traffic keeps arriving at the old server for a day after you’ve moved — and those clicks land in a database you’ve stopped using. There’s no way to merge them afterwards.
Change it the day before, wait for the old value to expire, then tell us you’re ready.
What we’ll do
- Back up everything on the old server, landers included
- Install Roitrack on the new one
- Unpin your licence and activate it on the new server
- Restore your data
- Verify before touching DNS — we check your campaigns and historical reports are all present while traffic is still flowing to the old server
- Repoint your domains
- Re-issue SSL certificates
- Watch clicks arrive on the new server
Step 5 is why this is worth doing together. Verifying before DNS moves means a problem is a pause, not an outage.
Afterwards
Your postback URLs keep working as long as your tracking domains don’t change — networks look up the hostname, not the server. You won’t need to touch anything at your affiliate networks.
Your tracking links keep working for the same reason. Live campaigns don’t need editing.
Backups need re-enabling on the new server. Ask us to set them up again as part of the move.
Don’t change tracking domains at the same time
Tempting, and worth resisting. If clicks stop after a combined move, there’s no way to tell whether it’s the server, DNS, certificates, or the new domain. Move the server, confirm traffic flows, then change domains as a separate step a day later.