Migration Request Procedure

A Migration Request form is the first step in completing your migration project with iWeb. If  ticket has not been opened for you by customer service, please open a ticket to request a migration. You will receive an auto-reply confirmation email that a ticket has been opened in your account. Please reply to that email and attach the excel spreadsheet once you have completed it.

Download the form here: Migration Request form 

Please Include as much information as possible, including contact info for individuals who can answer technical questions. Remember to delete the example information in the spreadsheet and use the drop-down menus when applicable. 

The following articles may help you answer some of the questions about software versions: 

Please note: iWeb strongly recommends you perform a complete backup prior to migration.  

Instructions on uploading a temporary maintenance message on your homepage are available in our webmaster section.

If you are migrating within iWeb, be aware of the following :

  • What is a primary IP ?

The primary IP, or main IP, is given to a specific server's location (or server ID). This IP cannot be migrated to a different location.   

  • What is a secondary IP ?

The secondary IP addresses are subnets given entirely to specific servers by routing them towards the main IP. They can be moved/routed to a different location/server, in any of our Montreal datacenters, as long as the server type does not change (they cannot be moved between Smart/Cloud/VPR/Cluster/etc).

  • What happens with my IPs during a migration ?

The main server IP will be lost, as it must stay on the same server's ID/location. However, we can move/reroute the secondary IPs to the migration target, avoiding a DNS modification/propagation. This is valid as long as the source server is the same type as the destination server.


Following the receipt of your Migration Request form, the procedure will follow the nine-step flow, outlined below: 




Please note: iWeb is unable to modify DNS records outside its control (Example: With a DNS provider such as GoDaddy). You are responsible for modifying DNS records hosted outside iWeb.


Article is closed for comments.
Powered by Zendesk