Migrating an Option Pool Between Environment

We are currently using PTC Windchill 13.0.2.12 to develop a Configurable Module in one of our test environments. As the solution matures, we expect to validate it in an additional test environment before ultimately deploying it to production.

We have identified the mechanism for exporting and importing an Option Set, which appears to support the transfer of a Configurable Module structure. However, our concern is the long-term maintenance of the module. As new Design Options, Design Choices, and Rules are added, we need to ensure that the underlying Option Pool can also be migrated and maintained across environments.

Without a way to transfer the Option Pool, we would effectively be limited to the state of the Option Set at the time of export. Future enhancements would require manually recreating Design Options, Design Choices, and Rules in each downstream environment, which introduces additional effort, risk, and validation requirements.

Ideally, we would like to avoid manually re-entering the entire Option Pool for each test environment and for production deployment.

We have discussed this issue with PTC support but have not yet been provided with a solution.

Has anyone successfully migrated an Option Pool between Windchill environments, or established a proven process for promoting configurable module data (including Design Options, Design Choices, and Rules) from development to test and production?

Any suggestions, best practices, or lessons learned would be greatly appreciated.

Thank you!