The drive towards standardization in the automotive sector puts a lot of pressure on software suppliers to comply with standards such as OSEK and AUTOSAR. However, many of these suppliers have a vested interest in proprietary software and are seeking ways to migrate their existing code-base to comply to these standards. This paper reports on a feasibility study to wrap a proprietary real-time operating system with an OSEK compliant interface. Besides investigating whether this is feasible, we also assess the performance impact in terms of computation time and memory consumption, as this is critically important for real-time systems. As such, we evaluate the typical trade-offs one has to make when adopting an incremental migration strategy towards a standard compliant interface.