We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

Showing results for 
Search instead for 
Did you mean: 

Step By Step Guide To Xilinx SDK Project Migration To Vitis

6 2 1,113

Starting in the 2019.2 release, the Xilinx SDK development environment is unified into an all-in-one Vitis™ unified software platform.

Dear SDK users, experiencing this feature-rich tool is just a few clicks away!

So, let's get started with migrating a project from Xilinx SDK to Vitis.

Vivado Project Upgrade

  • It is required to back up the project before migration.
  • Open the older versioned Vivado project and opt for an upgrade as shown below.










  • Navigate to Reports -> Report IP Status


  • Navigate to the IP status window, check the status, and upgrade the IPs


  • Generate the bitstream and navigate to File -> Export -> Export Hardware to export the bitstream and XSA.

Importing the SDK project to the Vitis workspace


  • Launch the Vitis IDE.

  • Import the older versioned Xilinx SDK project by navigating to file -> Import


  • Select Eclipse workspace or zip file under Import Type and click Next


  • In the next window, select the root directory and projects to be imported.


  • After a successful import, the user can see the imported application project(s), and platform project(s) as shown below.


  • The imported board support package is now present inside the platform project as shown below.


  • In the next step, we need to update the hardware specification to the latest version. Right-click on the platform project and click on Update Hardware Specification.


  • Select the XSA file that was exported from Vivado and click on OK.


  • After the update, you wil see an Out-of-date tag near the platform project.


  • Right-click on the platform project and select Build Project.


  • Build the application project(s) again.


Your migration is now complete!



What about create platform with the spr file for each microblaze -> then ceate system -> then move the files...

Do I need all this? it does not happand automatically for me migrating from 2017.4.1 to 2019.2


Teacher drjohnsmith

Thats great ,

Do we have any info as to how many versions of vivado this will be true for ?

We have had sitautions in the past, such as ISE to Vivado, where only a few versoin of vivado supported migration.

In say 3 years time, when a company comes to update a product , based upoon the previosu xilinx standard SDK, will they be able to import it into Vivado 2023 or will they have to instal vivado 2019.4 and import then iport that into 2023 ?