Domain transfer for associations: moving safely

A guide for associations: how a domain transfer succeeds with an auth code and transfer lock, and how the email migration to Virtualmin works without downtime.

The board has decided to move the association's website and email addresses to a new host. Now the responsibility lies with you, and you want to ensure that no emails are lost during the move and that the website remains reachable. This practical guide walks you step by step through the secure domain transfer and the email migration.

Domain transfer for associations: the basics

Before you start the transfer, you should check whether the domain is registered with Denic or another registry and whether you have the necessary access credentials. For .de domains, an auth code is required, which you request from your current registrar. For other TLDs, the process may differ. Important: the transfer is only possible if the domain is not locked by a transfer lock.

Obtaining the auth code and observing the transfer lock

The auth code is a kind of password that confirms the release of the domain. You will usually find it in the customer area of your current registrar or you can request it by email. Make sure that the email address of the domain owner (often the association) is stored correctly, otherwise the code will not arrive.

A transfer lock prevents unauthorized transfers. If you want to move the domain, you must first deactivate the lock. This is also done via the customer area of the old registrar. Do not forget to reactivate the lock with the new provider after the transfer in order to protect the domain.

Timing deadlines correctly

The transfer itself takes different amounts of time depending on the TLD. For .de domains, the switchover often happens within a few hours; for .com it can take up to five days. It is important not to start the transfer shortly before the domain expires, as this can cause confusion. Therefore, plan the move with sufficient buffer, ideally several weeks before the next renewal.

A realistic example: a sports club wants to move its domain from one provider to Dezhost. The treasurer requests the auth code, deactivates the transfer lock and commissions the transfer. After two days, the domain has been moved. However, the email addresses are only switched over later so as not to disrupt ongoing operations.

Email migration to Virtualmin without downtime

The email migration is the most delicate part, because no messages may be lost here. On a virtual server with Virtualmin, you first set up the new mailboxes before changing the MX records. This allows you to test whether the new server works correctly.

Step 1: Create new mailboxes

Create the desired email addresses in Virtualmin and test sending and receiving via a temporary subdomain or by connecting directly via IMAP. This ensures that mail reception works.

Step 2: Change MX records

Change your domain's MX records so that they point to the new server. Before doing so, reduce the TTL (Time to Live) of the records so that the change propagates quickly. After the switchover, it may take a few hours until all senders use the new MX. During this time, emails may still arrive at the old server. Therefore, set up forwarding from the old to the new server if possible.

Step 3: Adjust SPF and DKIM records

SPF and DKIM are important for deliverability and against spam forgery. Adjust the SPF record (TXT record) so that it includes the new server. Remove outdated records of the old server. For DKIM, generate a new key in Virtualmin and publish the public part as a TXT record. Do not forget to set the selector name correctly.

After the switchover, test sending to various recipients (Gmail, Web.de, etc.) and check the headers for SPF and DKIM results. This allows you to identify problems early.

Checklist for the move

  • Request the auth code from the old registrar.
  • Deactivate the transfer lock.
  • Commission the transfer with the new provider.
  • Set up and test new email mailboxes.
  • Change MX records (reduce TTL beforehand).
  • Update SPF and DKIM records.
  • After the transfer: reactivate the transfer lock.
  • Set up email forwarding from the old server (if necessary).

Legal notes

When moving the domain and email, data protection aspects must be taken into account, especially if member data is affected. This is not legal advice; if in doubt, consult a specialized lawyer.

With this guide, you can safely carry out the domain transfer and email migration for your association. Take your time for planning and test each step before removing the old settings. This keeps your association reachable during the move.