AeroWave’s Migration Centre is there to make moving your services to AeroWave as smooth and stress-free as possible. Most migrations run automatically and complete quickly, letting you focus on your business rather than the technical details.

Occasionally, however, a migration may encounter issues that prevent it from completing successfully. To help you get back on track, we’ve outlined some of the most common migration problems and practical steps to resolve them. Following these guide will help you re-try the migration progress.

Migrating From WordPress Using FTP/SFTP #

Most of our WordPress migrations complete without any issues however for our Migrations Centre to migrate a WordPress website, a few conditions need to be met, most sites will meet these automatically, but if you’ve made some custom changes to your WordPress installation, you may need to make adjustments.

If your migration doesn’t complete successfully, please check the following:

• Checking your wp-config.php location – Our tool looks for your wp-config.php file in your main WordPress folder. If you’ve moved it elsewhere for security, please move it back to the main folder and retry the migration process again
  
  
• File & Folder Permissions – We’d recommend checking your File & Folder Permissions and making sure they are consistent with WordPress’ best practices. You can find more about the best practices by clicking here
  
  
• Whitelist our IP Addresses – Our tool attempts to connect to your WordPress site by using our IP Addresses, sometimes your existing host may block these for security so please reach out to them and ask them to whitelist IP Range 45.8.227.0/24
  
  
• Ensuring Your Domain Is Linked Correctly – For our Migration tool to work, please ensure your domain name is pointed to your existing web host. If the nameservers are pointed to a different web host or service, the migration may fail

Migrating From WHM / cPanel #

Our cPanel migration tools uses your existing built-in backup feature in cPanel to create a full account back to transfer to AeroWave, where it’s converted into a package on our platform.

Sometimes a migration can stall and get stuck at the ‘Waiting for cPanel Backup’ stage. This means that we’ve requested the backup from your cPanel server and are waiting for it to be generated and uploaded onto our servers so the migration can continue.

Backup times depend on the size of the website or websites being moved over to us. Smaller sites usually complete quicker, while larger sites may take longer. Occasionally, the backup process on the original server may stall and get stuck. If this happens, we recommend checking the following reasons why a backup may be delayed.

• Your account may be over it’s quota or possibly suspended – This can cause the backup to stall. Please reach out to your existing web host who should be able to help you with this
  
  
• Whitelist our IP Addresses – Our tool attempts to connect to your cPanel by using our IP Addresses, sometimes your existing host may block these for security so please reach out to them and ask them to whitelist IP Range 45.8.227.0/24
  
  
• Your server may be under a high load average – This can cause cPanel to throttle the backup but it is normally running in the background a lot slower
  
  
• Your site might be very large – This can cause the backup process to take longer than expected, our system will automatically continue the progress once your backup has finished.

If your backup seems to be taking an usually long time, we’d recommend reaching out to your existing host who should be able to provide some help.

Migrating From Plesk #

Our Plesk Migration tool works by connecting to your current Plesk setup via the Plesk API to request a backup. This backup is then transferred over onto our servers via FTP, extracted, and imported to complete the migration.

For the migration tool to access your files, Plesk API access must be enabled on the host you are migrating from. If your migration fails immediately, this is often the cause. Please reach out to your existing provider to double check that API access is available for your account.

Similar to cPanel backups, once we request a backup from Plesk, our system will wait until the backup is fully completed before continuing. If anything on your existing server prevents the backup from completing, the migration may stall and get stuck in the processing stage. To avoid this:

• Please ensure your existing account / server has enough storage space for us to create the backup
  
  
• Whitelist our IP Addresses – Our tool attempts to connect to the Plesk API by using our IP Addresses, sometimes your existing host may block these for security so please reach out to them and ask them to whitelist IP Range 45.8.227.0/24

Migrating from Heart Internet Migrations #

In February 2023, Heart Internet ended support for its API. Since our migration tool relied on this API, it can no longer be used unless you already have an active Heart API key.

Don’t worry though, our support team can always attempt to manually migrate you over, please reach out to us if you are currently with Heart Internet.