A Comprehensive Guide for Same-to-Same Server Transfers

The Step-by-Step Process:

1. Step 1: Environmental Alignment: Before starting, ensure your new iDatam server "matches" the old one. Check your PHP versions (e.g., 7.4 vs 8.2) and MySQL/MariaDB versions. Consistency here prevents 500 errors post-migration.

2. Step 2: Initialize the Tunnel: Log into your new iDatam WHM and navigate to Home > Transfers > Transfer Tool. This is where the magic happens.

3. Step 3: Secure Authentication: Enter the remote server's IP and root password. We recommend using SSH Keys for a more secure and faster handshake between the two machines.

4. Step 4: Account Selection: The tool will fetch a list of all users. You can choose to move everyone at once or migrate in batches to manage bandwidth.

5. Step 5: The Integrity Check: Use the "Preview Website" feature. This allows you to view the site as it exists on iDatam before you update your DNS, ensuring everything is pixel-perfect.

The Step-by-Step Process:

1. Step 1: Extension Setup: On your new iDatam server, install the Plesk Migrator from the Extensions catalog. It's a lightweight tool that does the heavy lifting.

2. Step 2: Configuration: Start a "New Migration" and select Plesk as your source.

3. Step 3: The Handshake: Input your source IP and credentials. Plesk will then perform a "Pre-Check" to ensure the two servers can communicate without firewall interference.

4. Step 4: Smart IP Mapping: This is a crucial step. Plesk will ask you to map your old IPs to your new iDatam IPs. You can assign dedicated IPs to specific subscriptions or consolidate them onto a shared IP.

5. Step 5: Automated Sync: Once you hit "Start," Plesk handles the rsync of files and database dumps in the background. You can close your browser and come back when the green "Success" banner appears.

The Step-by-Step Process:

1. Step 1: The Master Backup: On the old server, use the Admin Backup/Transfer tool. This packages the entire account—emails, databases, and configurations—into a single compressed file.

2. Step 2: High-Speed Transfer: Move these files to the /home/admin/admin_backups/ directory on your new iDatam server. We recommend using a direct rsync command via SSH for maximum speed:

   bash Copy

   
   rsync -avz /home/admin/admin_backups/ root@IDATAM_IP:/home/admin/admin_backups/
                                           

3. Step 3: The Local Restore: In the iDatam DirectAdmin panel, select the "Local" path. The system will detect the transferred backups and begin unpacking them into their new home.

4. Step 4: Final IP Alignment: Use the IP Management tool to "re-home" your domains to their new iDatam IP addresses.

• TTL Reduction (The 24-Hour Rule): 24 hours before your move, change your DNS TTL (Time to Live) to 300 seconds. This ensures that when you finally point to iDatam, the entire world sees the change in 5 minutes, not 5 hours.

• SSL Propagation: Modern browsers hate insecure sites. Verify that your Let's Encrypt or Sectigo certificates have successfully migrated. Most panels will auto-renew these once the DNS switch is complete.

• The Live-Sync Finish: For active databases (like e-commerce or forums), perform one final "Live-Sync" of the data right before the DNS flip. This captures any comments or orders that happened during the file transfer.

Don't Want to Do It Yourself?

Moving your business infrastructure is a high-stakes task. Why spend your weekend troubleshooting rsync errors when you can let the experts handle it?

If you order an iDatam Dedicated Server today, our Migration Concierge Team will handle this entire process for you—from initial audit to final DNS flip—completely free of charge.

[Browse Bare Metal Plans]