Destructive restoration after failed CMS schema modification

Assuming current Webflow CMS behavior, when a schema modification fails—such as an incompatible field type change or an unintended collection deletion—the site may be left in an unstable state. The goal is to restore the site to a known-good snapshot using the Backups panel without permanently losing CMS items, form submissions, or settings that were created or changed after that snapshot was taken.

Webflow documents that restoring a backup reverts the site's design, CMS content, and settings to the exact state of the selected snapshot. The restoration process is destructive to any changes made between the snapshot time and the restoration time, and the restoration action itself cannot be undone. This raises uncertainty about whether any selective preservation is possible for post-snapshot CMS data, or if the platform enforces a strict all-or-nothing rollback.

Is there a supported workflow to export or stage CMS items created after the backup point before initiating a full site restoration? Can form submissions received after the snapshot be recovered through any documented mechanism, or does their loss depend on the storage method? Does Webflow offer any partial rollback that isolates CMS collections from design and settings during recovery?