Unfortunately not at the application-level, however, the Zigbee Coordinator firmware does have a key store and stores all joined devices, so if you enter the Network Key and PAN ID in then you at least do not have to manually re-repair all of your devices as they are already approved by the Zigbee Coordinator as they will at least try to reconnect, but at the application-level you will still be like adding them from scratch, so you need to setup all your devices and device settings for each device again.
ZHA to ZHA migration is possible → https://skyconnect.home-assistant.io/migrate-zigbee-zha-only/
The problems are when want to migrate from ZHA to Zigbee2MQTT, or from Zigbee2MQTT to ZHA.
You will not get a seamless migration as all of the metadata is stored in host application databases.
Cross-applications migration only saves you the trouble of having to manually re-pair all devices, though note that you will still probably have to re-pair some devices, as well as re-do all application-level stuff.
This disclaimer below is posted on both these two guides:
“Note: this procedure only helps migrate basic network settings to your Home Assistant SkyConnect, customizations like device names will be lost and automations will need to be updated. Most powered devices like lightbulbs will be re-discovered over time (you can speed this up by rebooting the device) but your battery-powered devices may need to be re-joined to the network for the migration to complete. There is currently no migration path to migrate all settings and devices.”