Relocate websites: Registrar change
If you want to keep your domain and have registered it with the old provider, you have to transfer it. The majority of top-level domains (.de or .com) can be automatically transferred within a short time. First of all, you have to cancel the domain with your current provider and request an authorization code (often called “Auth-Code” or “Auth-Info”). You have to specify this when ordering the new webspace. For some domains, there are special conditions for the transfer. Hosting providers such as 1 & 1, Strato and Co. provide appropriate guidance and advice *available on their websites, which should be considered. In the event that the domain does not need to be transferred, only the appropriate DNS settings must be edited so that the domain is linked to the new server.
Moving e-mail boxes will make things a bit more complicated. In order to migrate e-mails from the previous provider to an IMAP server at the new provider, the usual e-mail clients such as Thunderbird, Microsoft Outlook or Apple Mail are suitable. With drag-and-drop you can easily copy the old messages to the inbox of the new IMAP account. If you want to move your e-mails to a POP3 server, you can use a so-called collection service that many providers offer. The user enters here the new hoster’s e-mail address and the login data of the old provider and the messages stored there are automatically retrieved.
Providers take over the move
Businesses who do not want to worry about moving their email or website can resort to relocation services offered by many hosting providers. With the Umzugsservice Plus of the hosting specialist Mittwald, the relocation of website, main domain and e-mail goes without much effort on the stage. The hoster only needs the corresponding access data and then handles the complete move. The hosting provider DM Solutions offers a similar service. Simple websites (up to 700 megabytes in size) move around for free, while more complex systems and e-mail accounts cost extra.
Migrate critical business applications
For system administrators, moving a business application is a critical moment. For enterprise applications performance and availability are capitalized, end users should notice as little as possible of the migration. This is easier said than done. In practice, there are a number of dangers when moving complex web applications. The more complex the application infrastructure is, the more difficult the change is. Of course, if you run multiple server instances behind a load balancer and the database is replicated across multiple machines, the move is more time consuming than with a simple application running on a single server.
Like every move in real life, a server move is always associated with a certain amount of stress. For an optimal, that is as smooth as possible and stress-free hoster change first careful planning and a good preparation are crucial. The more complex the system to be migrated, the more useful it is to create a step-by-step guide that specifies all the tasks to be done in the correct order. If you do not want to experience any unpleasant surprises at the end of the move – such as bugs, incorrect links, ranking losses in the search engines or performance losses – you should do one thing above all else: test, test, test. And not only before the launch of the new server, but also afterwards. Especially in the first few days after the move, it is advisable to