There are some things to consider in preparation for migrating your Checkmk server. There are also several scenarios regarding migration.

Scenario: Change the IP address of your Checkmk server

Things to consider

- If the update server is not configured as a DNS name, make sure to update the IP address of the update server prior to migration.
- Ensure your TLS certificates match the new server configuration and are baked into the agent.
- Verify that all agents are up-to-date!

- Checkmk Agent: Ensure your IP allowlist contains both the old and new IP of the server prior to the migration (Rule: Allowed agent access via IP address (Linux, Windows))
- TLS Encryption: If you have registered to the Checkmk server using an IP/DNS name, you have to make sure this either remains the same or you have to re-register
- SNMP: Ensure ACL on SNMP devices will allow the new IP

Make sure your central firewall(s) allow all necessary traffic (See the following article for reference: Network ports used by Checkmk)

If custom routes have been configured on the Checkmk server, make sure to check and, if necessary, adapt them.

If the server name changes, you need to acquire new certificates. See also the section Agent Updater!

Make sure your mail server is still accessible from the new IP

If your server acts as a target for SNMP traps or remote syslog messages, you might have to change the target IP/DNS name on the sending devices.