For the Omniscope Classic users who wish to migrate to the Evo application, but have a large number legacy IOK files - we tried to make the migration process smoother by adding an automated process.
The user should upload an .iok file by dropping it on the projects' page (click 'No' when prompted to create a new project - this option will use the IOK as a data source).
The Evo app will then add a 'Migrate' button next to the file name and with a single click the DataManager blocks will be transformed into the equivalent Evo blocks. Omniscope will create a duplicate Evo project with the same blocks next to 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 we can see an example of an automated migration. The Classic blocks flowing top to bottom are now rebuilt and are flowing left to right in the IOX project.
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