Hm, but for this you can disable this setting?
Looks like a bug, we will check
Hello @helloitse
At some point we stopped deleting entities in some cases and instead we just set “Deleted in HubSpot“ field to true. After the merge old entities will have it as “true”. Then you can either delete them manually or setup some automation. Please note that any rich-text annotations or custom fibery data won’t transfer to new records automatically 
In case the field is not updated, please trigger “Full sync”
Out of curiosity, does the Jira two-way sync make use of the normal Custom-Integration API with some extra, unlisted endpoints/commands/parameters or was it a totally custom one-off?
I completely understand the team not prioritizing more integrations like this, but I’ve always wondered if there was some undocumented API stuff that we could experiment with. I have successfully gone down the rabbit-hole of Custom-Integration db → editable mirror db → send changes via external actions → get update via webhook (plus a bunch of little tweaks to make sure there is no looping and everything is linked correctly), but it’s pretty clunky and I would happily spend the time doing some reverse engineering if I knew the was a chance I could build something similar. I am aware that it would require some non-trivial coding to orchestrate and prevent looping.