For Omniscope Classic users who wish to migrate to the Evo application but have a large number of legacy IOK files, we have made the process smoother by adding an automated migration option.
To begin, upload an .iok file by dropping it onto the Projects page. When prompted to create a new project, click ‘No’, as this option uses the IOK as a data source.
The Evo app will then display a ‘Migrate’ button next to the file name. With a single click, the DataManager blocks are converted into their equivalent Evo blocks. Omniscope creates a duplicate Evo project with the same blocks alongside the original IOK file.
The user should examine the new project's data source paths to make sure the blocks are still correctly connected, as well as compare the transformation results to check that nothing was 'lost in translation'.
Note - the automated conversion process will create an approximate 'like for like' Evo workflow, however any data visualisations created in the Classic's Data Explorer will have to be re-built with new chart libraries, as this part of the app is not yet compatible with the old architecture.
Below is an example of an automated migration, where the Classic blocks that flowed top to bottom (left image) are rebuilt to flow left to right in the Evo IOX workflow.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article