Check the result

Compare the exports

Compare what the project produces before and after the migration:

1. Before you migrate, with Syside v0.11, export every table and matrix with syside grid export (Grid command) and every diagram with syside viz view (Viz command), each into an empty folder. Only the standalone Syside v0.11 CLI has syside viz; the Syside v0.11 Python package doesn’t. Without it, skip the diagram comparison and review the diagrams in Syside v1 against Migrate diagram views. Run your Python scripts and keep their output.

2. After you migrate, export and run them again with Syside v1, into other empty folders.

3. Check that every file is present on both sides, then compare their contents. syside grid export writes no file for a view with no rows or columns, so a missing file can mean an empty view. Each difference in a table or script output should come from a change you made on purpose or one that these guides describe. Compare diagrams by eye: the diagram engine draws them differently, so the files are not expected to match.

If Syside v1 is already installed, export the tables and matrices while their views still run in compatibility mode instead (see Migrate grid views), and use those exports as the Syside v0.11 side. Use Export as CSV in the extension, and choose Export Anyway if the model has errors, or export every view at once with syside grid export. Do this before you fix the model errors, since the fixes can change the rows.

Check ReqIF exports

syside reqif now honors exclude in syside.toml (Import and export ReqIF documents). A file that exclude lists is left out of an export, and its requirements drop out of the exchange without a warning. Before exporting, check that exclude lists no file with requirements to exchange, and compare the requirement count with the last export Syside v0.11 made.