IP Migration Wizard — Simple & Complete Guide

IP Migration Wizard — Simple & Complete Guide

Use this tool to move hosted accounts and their services from one IP address to another on the same server. It updates related web and DNS settings so sites continue working after the change.

Important:
  • Schedule a maintenance window; brief interruptions can occur.
  • Back up key configs and ensure the destination IP is routed and active.
  • If DNS is external, you must update those records separately.

What This Wizard Can Update

  • Account IP assignments (sites move from the old IP to the new IP).
  • Web server vhost entries (so HTTP/HTTPS resolves on the new IP).
  • Local DNS zone A/AAAA records for moved domains (if zones are hosted here).
  • Service mappings where applicable (mail, FTP, and related configs).

Before You Begin

  • Confirm the destination IP exists on the correct interface and is not reserved for other purposes.
  • Lower DNS TTL a few hours in advance to speed up propagation.
  • If you rely on reverse DNS (PTR), arrange the new PTR with your provider.
  • Check firewall, CDN, and allowlists for references to the old IP.
Quick TTL prep (example): 
# Lower zone TTLs in advance (example command hints)
# After change, reload DNS and wait for previous TTLs to expire

Run the Wizard (Step-by-Step)

  1. Open IP Migration Wizard.
  2. Select the Source IP (current address of the accounts).
  3. Select the Destination IP (the new address).
  4. Choose which accounts to move:
    • All accounts on this IP, or
    • Selected accounts only (use the checkboxes).
  5. Review update options (web configs, local DNS zones, and other mappings) and confirm.
  6. Click Migrate. Monitor the progress messages until the job completes.

What Happens During Migration

1) Update account-level IP assignments
2) Rebuild web server vhosts to bind on the new IP
3) Update local DNS A/AAAA records (if zones are hosted here)
4) Restart/reload impacted services as needed

After the Move

  • Test each site over HTTP and HTTPS on the new IP.
  • If you use external DNS, update A/AAAA records there and allow time for propagation.
  • Re-issue or check SSL coverage if domains changed IP and certificates are IP-dependent (rare; SNI generally handles this).
  • Verify mail, FTP, and application callbacks that reference the server IP.
Tip: Keep the old IP active for a short overlap if third-party services cache it. Decommission it only after traffic stabilizes.

Quick Verification

# Check DNS answers (replace domain)
dig +short example.com A
dig +short example.com AAAA

# Confirm HTTP/HTTPS responds on the new IP
curl -I https://example.com

# Ask the server directly with Host header (replace NEW_IP)
curl -I -H "Host: example.com" http://NEW_IP

Common Scenarios

  • Move everyone off a retiring IP: Choose the old IP as source, select “all accounts,” and migrate to the new shared IP.
  • Shift only a few high-traffic sites: Pick those accounts individually and move them to a dedicated IP.
  • Prepare for IP decommission: Migrate accounts, update external DNS, confirm traffic, then remove the old IP from the server.

Troubleshooting

  • Site still answers on old IP: CDN/browser/DNS cache. Clear caches and verify TTLs have expired.
  • Invalid host routing: Rebuild vhosts and ensure the destination IP is bound to the correct interface.
  • External DNS not updated: Edit records at your external provider to point to the new IP.
  • Mail delivery warnings: Check reverse DNS on the new IP and update any SPF/allowlists.

Summary

  • Select source and destination IPs, then choose all or specific accounts.
  • Wizard updates web configs and local zones, then reloads services.
  • Verify DNS/HTTP/HTTPS and update any external records.
  • Plan PTR, firewall, and third-party integrations before decommissioning the old IP.
case studies

See More Case Studies