Hello Aaron,
Since the stack comes in a library compiled with IAR, I think that migrate the code and have complete compatibility will be impossible.
The EABI is a standard that defines the mapping between low level concepts in high level languages. The purpose of this EABI is to allow interoperability between objects built in different tools. However, IAR doesn't have a public EABI. Each build tools provider provides its own EABI, allowing interoperability between objects built with the same build tools. Making the mentioned libraries interoperable could be possible only if the EABIs are compatible.
However, the thread in the link below could be useful for you.
MCR20A source migration from IAR to KDS
The reason our stacks are only supported for IAR is that it is a compiler more efficient than GCC and as you may know these are very complex stacks where the footprint would be considerably impacted.
Best regards,
Earl.