Functionality going from UTM to SFOS - got a map?

First of all: I want to highlight the Migration script by Sophos to get the "busy work" done. https://github.com/sophos/Sophos-Migration-Utility-CLI This tool essentially is a script to migrate stuff from UTM like host objects etc and gives you an XML Import file for the firewall. 

You cant migrate things, which are differently in SFOS like firewall rules (UTM Rules make no sense in the SFOS, as SFOS approaches Zones differently). 

Points from alan weir are valid, if you face them. For example: Customers in your size often use a DHCP Server, therefore a DHCP static mapping is not applicable. 
Drag & Drop is more a "how do you like to do it" feeling. You can search in the field of SFOS to "click" it and not drag and drop. 
Easier or complicated is more a discussion in terms of "Are you used to a different approach". 

Things to notice from BrucekConvergent : NTP Server can be done by a NTP Server workaround:  Sophos Firewall: Using NAT to achieve NTP proxy like functionality  
Lets Encrypt is more for the WAF Features, depends if you use WAF on UTM or not - In SFOS the WAF Subscription is exclude from the bundle, as customer start to not opt-in for it anymore. 

Most - If not all - feature gaps are tracked by Sophos internally and considered to be addressed in the future (or not). Depending on the needs and the time to invest. For example a NTP Server on the firewall is easily workaround able and the time needed, to build a fully featured NTP Server and harden the system (as it is a service the firewall services, you have to harden the system), is much higher then the potential outcome. 

First of all: I want to highlight the Migration script by Sophos to get the "busy work" done. https://github.com/sophos/Sophos-Migration-Utility-CLI This tool essentially is a script to migrate stuff from UTM like host objects etc and gives you an XML Import file for the firewall. 

You cant migrate things, which are differently in SFOS like firewall rules (UTM Rules make no sense in the SFOS, as SFOS approaches Zones differently). 

Points from alan weir are valid, if you face them. For example: Customers in your size often use a DHCP Server, therefore a DHCP static mapping is not applicable. 
Drag & Drop is more a "how do you like to do it" feeling. You can search in the field of SFOS to "click" it and not drag and drop. 
Easier or complicated is more a discussion in terms of "Are you used to a different approach". 

Things to notice from BrucekConvergent : NTP Server can be done by a NTP Server workaround:  Sophos Firewall: Using NAT to achieve NTP proxy like functionality  
Lets Encrypt is more for the WAF Features, depends if you use WAF on UTM or not - In SFOS the WAF Subscription is exclude from the bundle, as customer start to not opt-in for it anymore. 

Most - If not all - feature gaps are tracked by Sophos internally and considered to be addressed in the future (or not). Depending on the needs and the time to invest. For example a NTP Server on the firewall is easily workaround able and the time needed, to build a fully featured NTP Server and harden the system (as it is a service the firewall services, you have to harden the system), is much higher then the potential outcome.