Previously, restoring a site backup would cause CMS collection and item IDs –as well as Ecommerce, Page, and Asset IDs– to reset, requiring developers to reconfigure any API connections keyed off of those IDs.

Previously, restoring a site backup would cause CMS, Ecomm, Page, and Asset IDs to reset

Through our recent investments to make these IDs persistent, you can now confidently restore site backups without worrying about disrupting existing API connections.

With persistent CMS, Ecommerce, Page, and Asset IDs, you can now confidently restore site backups disrupting existing API connections.

‍Please note: This update applies to all site backups moving forward, not historical site backups. If you restore a historical site backup, your CMS, Ecommerce, Page, and Asset IDs will reset. If you’ve never restored a site backup, your IDs are persistent now and retroactively (in other words, you’re in the clear!).

To learn how to save and restore site backups, visit Webflow University.

Launched on

March 25, 2024