The Vitis Unified IDE workspace ensures version control optimization. Hence, the workspace and project metadata is incompatible with classic IDE. To help you transition, two methods are available for migrating your projects.
Migrate Manually (from 2025.1 Onward)
Starting with the 2025.1 release, you can no longer use the Vitis Classic IDE. No migration utility is available in this version. If you did not migrate your workspace in a previous release, you need to manually recreate your workspace in the Vitis Unified IDE.
To manually migrate your project, follow the steps below:
- Generate a new XSA file using the latest Vivado tools.
- Recreate your platform project in the Unified IDE based on the updated XSA file.
- Recreate your application project using the new platform.
- Import your application source code into the new project.
- Build your application and resolve any issues that arise during the
build.Note: If you encounter any issues related to migration, refer to Standalone Application Component Migration Details
Migrate Projects Using Previous Version Utility
A migration utility is available in the Classic IDE for release versions 2023.2, 2024.1, and 2024.2. After migrating your project in the Classic IDE, you can then update your hardware platform and application to the current release.
To use this method, follow the steps below.
- Open the workspace with the Classic Vitis IDE.
- Select . Once you choose this, a dialog box appears.
- In the dialog setup page, specify the migration target workspace
location.
- Click Finish. The Vitis tool generates a migration script in the specified location.
- Open a terminal with Vitis environment
settings, type the following command and hit
enter.
The Vitis tool runs the migration script and copies the project resources to the new location. The process takes some time. Once completed, you can see the migrated components and projects in the workspace directory. You can find the project resources in the new location.vitis -s migrate.py - Open the migrated workspace with the Vitis Unified IDE.
- Open your platform project in the IDE and locate and open the platform Json file.
- Click Switch/Re-read XSA to select the
updated XSA file generated with the latest tool version.Note: This action regenerates the System Device Tree (SDT) and Board Support Package (BSP) for your applications.
- Rebuild your platform and applications.
| Project type | Limitation | Workaround |
|---|---|---|
| Platform | Local changes to BSP sources are not be migrated to the new workspace. A new BSP is created, and the settings are applied on the new BSP. | Copy the sources to the new BSP manually. |
| Any embedded software repositories added to Vitis IDE cannot be migrated. A warning is shown in the wizard if you have any local sw repos. | All software repositories need to be migrated to lopper first. The path to the migrated repository can be added to the migration script (refer below screenshot for an example) to migrate the projects. | |
| IP drivers included in XSAs which were created with 2023.1 or older releases can encounter compilation errors. | Need to regenerate the XSA with 2024.2 release. | |
| Embedded Application | Applications referring to platforms that are outside the current workspace cannot be migrated. | Migrate the platform first and update the application to use the new platform before migrating the application. |
| If your application relies on the device ID, some modifications can be required in the application source code. This is because the Device ID in the xparameter.h file has is deprecated. For more details, refer to Porting Guide for embeddedsw Components System Device Tree Based Build Flow (UG1647) | Refer to Standalone Application Component Migration Details | |
| Debug Configurations cannot be taken over to Unified IDE | Create launch configuration in Vitis Unified IDE |
vitis --classicFor more information on Vitis Unified IDE, refer to Launching the Vitis Unified IDE and Vitis Unified IDE View and Features.