# Motoko stable record upgrades

**URL:** <https://forum.dfinity.org/t/motoko-stable-record-upgrades/36322>\
**Category:** Developers\
**Created:** [October 18, 2024, 7:38pm UTC](https://forum.dfinity.org/t/motoko-stable-record-upgrades/36322 "2024-10-18T19:38:39Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![icme](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/icme/32/4327_2.png) [@icme](https://forum.dfinity.org/u/icme)\
**Post date:** [October 21, 2024, 3:12pm UTC](https://forum.dfinity.org/t/motoko-stable-record-upgrades/36322/12 "2024-10-21T15:12:20Z")

</div>

In one of the previous [Motoko developer working groups](https://forum.dfinity.org/t/motoko-developer-working-group/20488) I believe @luc-blaeser was coming up with an easy migration pattern integrated at the language level that would run on upgrade, and rollback if a trap occurred.

So I think this is being considered/worked on?

I asked him if there was a downgrade abstraction as well (allowing you to downgrade the migration if there’s a bug in new code that uses it), so not sure if they’re considering that or not.

---

_[View the full topic](https://forum.dfinity.org/t/motoko-stable-record-upgrades/36322)._