8.5.2. Problem importing supports between different SuCri versions

In this article you will learn why errors can occur when importing supports between different SuCri versions and how to fix them. Consistent software versions are crucial for smooth data exchange within your projects.

Prerequisites

• Access to the source and target installations of SuCri.
• The support data to be imported is available in JSON format.

Step-by-step guide

1. Check the versions: Determine which SuCri version was used for the export. An error occurs, for example, if supports were exported with version 24.1.7.5 and are now to be imported into version 25.1.0.2.
2. Export again: Open the source data with the current SuCri version (e.g. 25.1.0.2).
3. Export the supports: Export the supports again to generate a compatible JSON output format.
4. Run the import: Import the newly created files into your target environment.

Expected result: The import completes without an error message and the supports are available correctly.

Important notes

• Format changes: Between versions 24.1.7.5 and 25.1.0.2, there were changes to the JSON output format that prevent backward compatibility.
• Best practice: Ideally, always use the same SuCri version for export and import within a project.
• Project coordination: Before changing versions, clarify within the team whether existing export data needs to be migrated or recreated.
• Plant 3D: Standard Plant 3D supports are generally not affected by this issue.

Troubleshooting

• Error persists despite re-export: Check whether the supports are standard Plant 3D supports.
• Technical support: If problems persist, please contact support and provide the affected export data for analysis.

Copyright © 2026 by IntegaDesign GmbH. All Rights Reserved.