This experience report will focus on the issues which drive developers to migrate their application development to a new host or new target or new tool set. If there is no reason to change the embedded application, then there will obviously be no migration. Often there are compelling reasons to change the application, in which case the benefits of change will have to out weigh the costs. If the change can be incorporated using the existing tools, host, and target, then so much the better. But, if the existing tools, host, and/or target are no longer viable, then the cost of making a change to the application must include the cost of a migration.
/lp/association-for-computing-machinery/when-to-migrate-legacy-embedded-applications-5hbO5ODzlW