Last updated: November 4, 2026

Moving a Windows Server to a new VPS can feel risky, but with a clear plan it’s straightforward. Whether you’re switching from another VPS provider or moving from an on-premise server, this checklist walks you through each step, from backing up to switching your domain, with commands you can copy and paste.

We use Winserver’s Japan-based Windows VPS as the example, but the same steps apply to most Windows Server migrations.

Why Migrate to Winserver?

• Hosted in Japan for low-latency access across Asia-Pacific
• Windows VPS plans with full administrator access and the Windows Server license included
• VPN pre-installed from SSD-4G plans and up
• High reliability based on Japan’s stable hosting environment
• Flexible plans for businesses, developers, and remote teams

Why Choose a Japan-Based Windows VPS

Step 1: Choose the Right VPS Plan

Visit our VPS Plans page and choose a plan that fits your performance needs. As a rule of thumb, choose at least as much memory and storage as your current server uses, plus some room to grow.

If you’re unsure, we recommend the SSD-4G plan, which includes VPN pre-installed and is ideal for secure remote access and internal systems.

Still comparing providers? See our Japan VPS providers comparison.

Step 2: Prepare Your Source Environment

Before starting the migration, gather the following information from your current server:

• OS version and system settings
• Installed applications and licenses
• Firewall and remote access rules
• Scheduled tasks and services
• Data backups (files, databases, emails)

It’s highly recommended to create a full backup before you proceed, and to keep it until the migration is finished and tested.

Step 3: Set Up Your Winserver VPS

After your Winserver VPS is provisioned, you will receive:

• Remote Desktop (RDP) login credentials
• VPN connection information (for SSD-4G and up)
• Admin-level access to install and configure applications

Log in via RDP and begin setting up your server: install Windows updates, then reinstall the applications from your list in Step 2. If using VPN, follow our setup guide for a secure connection.

If you’re new to managing Windows VPS instances over Remote Desktop, the step-by-step RDP guide below will walk you through the setup.

Remote Desktop Setup Guide for Your Windows VPS

How to Set Up SoftEther VPN Client on Windows: Step-by-Step Guide

Step 4: Transfer Files and Data

You can migrate your data using one of the following methods:

• Remote Desktop: Transfer files via RDP by sharing a local drive
• Cloud Storage: Use OneDrive, Google Drive, or Dropbox
• FTP/SFTP: Set up a temporary server for large files
• Database Transfer: Export/import SQL backups or use remote database tools

Useful commands for the move

Run these in PowerShell as Administrator on the old server, then copy the results to the new VPS.

Copy folders (keeps permissions and timestamps, and can resume if interrupted):

robocopy "D:\Data" "\\NEW-SERVER\D$\Data" /E /COPYALL /R:2 /W:5 /LOG:C:\robocopy-log.txt

Replace the folder paths and NEW-SERVER with your own. Copying directly between servers needs file sharing access between them. If that isn’t available, copy the files over Remote Desktop or cloud storage instead.

Back up your IIS configuration:

& "$env:windir\system32\inetsrv\appcmd.exe" add backup "before-migration"

Export scheduled tasks:

New-Item -ItemType Directory -Force C:\task-export
Get-ScheduledTask -TaskPath "\" | ForEach-Object { Export-ScheduledTask -TaskName $_.TaskName | Out-File "C:\task-export\$($_.TaskName).xml" }

Export Windows Firewall rules:

netsh advfirewall export "C:\firewall-rules.wfw"

List installed programs (to reinstall on the new server):

Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion | Sort-Object DisplayName | Out-File C:\installed-programs.txt

Need help? Our support team is ready to assist you with the best method based on your setup.

Step 5: Test and Optimize

After transferring your data, test the following on the new server before switching any users over:

• Applications and websites
• Databases and file permissions
• Firewall and port settings
• VPN connectivity
• Scheduled tasks and monitoring tools
• Startup after a reboot (restart the server once to check everything comes back)

If some of your applications need a signed-in user to run, see our guide to starting applications automatically after a restart.

We also recommend enabling automatic backups and server monitoring with our available tools and add-ons.

Step 6: Update DNS or Domain Settings

If you’re using a custom domain, update your DNS records (A, MX, etc.) to point to your new Winserver IP.

Tip: 1–2 days before switching, lower the TTL (time to live) on your DNS records to something short, such as 300 seconds. When you change the records to the new server, most visitors will switch over within minutes instead of hours. Keep your old server running until you’ve confirmed everything works on the new one.

Note: DNS changes can take up to 24–48 hours to reach everyone worldwide.

Migration Checklist

• Full backup of the old server taken and kept
• New VPS set up, updated and applications installed
• Files, databases, IIS sites, scheduled tasks and firewall rules moved
• Everything tested on the new server, including after a reboot
• DNS TTL lowered, then records switched to the new IP
• Old server kept running until the new one is confirmed working

Need Help? We’re Here for You

Winserver offers friendly support throughout your migration process. If you need help, feel free to contact us — we’re happy to guide you every step of the way.

Conclusion

Migrating a Windows Server to a new VPS is straightforward when you back up first, test before switching, and keep the old server running until you’re sure. With Japan-based infrastructure, VPN-ready plans, and reliable Windows VPS hosting, Winserver makes the move simple.