# Question about Migration Strategy

**URL:** <https://forum.inductiveautomation.com/t/question-about-migration-strategy/113911>\
**Category:** Module Development\
**Tags:** ignition83\
**Created:** [February 11, 2026, 8:41pm UTC](https://forum.inductiveautomation.com/t/question-about-migration-strategy/113911 "2026-02-11T20:41:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eden.Mar](https://avatars.discourse-cdn.com/v4/letter/e/35a633/32.png) [@Eden.Mar](https://forum.inductiveautomation.com/u/Eden.Mar)\
**Post date:** [February 11, 2026, 8:41pm UTC](https://forum.inductiveautomation.com/t/question-about-migration-strategy/113911/1 "2026-02-11T20:41:02Z")

</div>

Hello, I had a question about the 8.3 ExtensionPointMigrationStrategy builder. I have an 8.1 module with two different versions, v1 and v2. The difference between the versions is v2 has some extra fields. I have included those extra fields in my 8.3 release, v3. My migration strategy accounts for these extra fields, and when I migrate from v2 to v3, things work as expected.

When migrating from v1 to v3, it looks like the value I get in the migrated settings is based off the default values from the v2 settings record, which I am perfectly happy with. My question is this expected behaviour? Is what I’m seeing when migrating from v1 to v3 going to remain consistent?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [February 11, 2026, 9:13pm UTC](https://forum.inductiveautomation.com/t/question-about-migration-strategy/113911/2 "2026-02-11T21:13:05Z")

</div>

I would expect you can only specify one `PersistentRecord` type for a given IDB table. Whatever you put there is all it can draw from.