We are programmatically migrating Confluence page macros by replacing legacy P2 macros with Forge macros via REST API (updating the page’s ADF).

After updating a page’s ADF to replace legacy macros with Forge macros, the page displays correctly in View mode. However, when entering Edit mode, the legacy editor sometimes reverts the page content to its previous version, undoing the API update.

We'd like the ability to control or prevent this editor reversion programmatically via the API since it blocks automated macro migration for customers, as programmatic updates are lost when users attempt to edit affected pages and, therefore, it's a migration blocker for us.