it really depends
For now - I would use the Homematic IP Cloud based integration, just as you planned to do.
Keep your existing automations within the Homematic AP, because the Cloud API is a bit limited… and with too many automations in your HomeAssistant you might run into issues here.
Keep the Automations in Homematic, especially with devices that are using other Homematic Devices.
When it comes to communicate with other Hardware, like Fritz Smart devices, then use HomeAssistant.
A reason, why I’ve moved away from the Homematic IP App - and using the Homematic CCU (RaspberryMatic) was - to get rid of the API Limitations and because I wanted to use some Homematic devices that are currently not available as Homematic IP devices, and therefore could not be used with the AP and Cloudservice.
But even with this, I am using options from homematic, such as “direct communication” for example between the Window / Door Sensors and the Thermostats… I don’t need an automation in HomeAssistant, if Homematic can communicate directly between these devices.
Also, I am using SOME (not many) automation / programs directly within the Homematic CCU, rather than creating them in HomeAssistant.
Right now, this is a case for my smoke detectors.
It was easier to access the specific alarm type within homematic than getting this in HomeAssistant - but it should be possible to do in HomeAssistant as well.
the benefit in case of the CCU - you can create variables inside the CCU - and then, use these again in HomeAssistant, to do other actions or trigger additional devices / automations.
And since I am using HomeAssistant with the companion app and can Access my installation remotely, I don’t need the Homematic App in particular.
The benefit is:
You can move everything in a speed you like.
You can keep existing automations - as long as they are working fine… and move them, when it might be required to add or change something…
BUT: When switching from the Cloud to the CCU… you have to setup every device again… that’s the downside…