Simulink.exportToVersion
R2026bExport model, library, or project for use in previous version of Simulink
Syntax
Description
exports the specified model or library to the specified version of Simulink® in a format that version can load.exported_file = Simulink.exportToVersion(modelname,target_filename,version)
If the system contains functionality not supported by the specified Simulink version, the command removes the functionality and replaces any unsupported blocks with empty masked subsystem blocks colored yellow. As a result, the converted system may generate different results.
The save_system
ExportToVersion legacy option is supported for this
functionality.
specifies additional options as one or more name-value arguments.exported_file = Simulink.exportToVersion(modelname,target_filename,version,Name=Value)
exports the project exported_project = Simulink.exportToVersion(proj,zipfilename,version)proj to a ZIP file
zipfilename in a format that the specified previous
Simulink
version can load. If the project contains requirements link
files or requirements files, Simulink.exportToVersion updates the
links to point to the newly exported files.
exports the project with the criteria specified by one or more
exported_project = Simulink.exportToVersion(proj,zipfilename,version,Name=Value)Name=Value arguments. You can use this syntax to export
referenced projects and missing files.
Releases prior to R2025a do not support filenames that exceed 63 characters. If you attempt to export a project that contains filenames exceeding 63 characters to a release prior to R2025a, the function lists the project files with long names. Shorten the names and replace all references to the filename in the project before exporting to a previous release.
Examples
Input Arguments
Name-Value Arguments
Output Arguments
Limitations
Simulink.exportToVersiondoes not support exporting external test harnesses to previous releases.For models with external test harnesses,
Simulink.exportToVersionautomatically converts them to internal test harnesses.For projects containing models with external test harnesses,
Simulink.exportToVersionexports the projects and reports the test harnesses as missing files.
Simulink.exportToVersiondoes not support exporting configurations stored in a data dictionary or a referenced dictionary. As a result, the exported data dictionary does not contain configurations stored in the original data dictionary.