Roboflow to Supervisely
Convert and copy multiple Roboflow projects into Supervisely at once.
This application allows you to copy multiple projects from Roboflow instance to Supervisely instance, you can select which projects should be copied, labels and tags will be converted automatically. You can preview the results in the table, which will show URLs to corresponding projects in Roboflow and Supervisely.
Complete migration guide from Roboflow to Supervisely.
Preparation
âšī¸ NOTE: Every project in Roboflow MUST contain at least one version, otherwise it's impossible to export data from Roboflow. Learn more about Versions in Roboflow documentation.
In order to run the app, you need to obtain Private API key
to work with Roboflow API. You can refer to this documentation to do it.
Now you have two options to use your API key: you can use team files to store an .env file with or you can enter the API key directly in the app GUI. Using team files is recommended as it is more convenient and faster, but you can choose the option that is more suitable for you.
Using team files
You can download an example of the .env file here and edit it without any additional software in any text editor. NOTE: you need to unzip the file before using it.
Create a .env file with the following content:
ROBOFLOW_API_KEY="qASymt32UTnQV1qABszF"
Upload the .env file to the team files.
Right-click on the .env file, select Run app and choose the Roboflow to Supervisely Migration Tool app.
The app will be launched with the API key from the .env file and you won't need to enter it manually. If everything was done correctly, you will see the following message in the app UI:
âšī¸ Connection settings was loaded from .env file.
â Successfully connected to https://api.roboflow.com.
Entering credentials manually
Launch the app from the Ecosystem.
Enter the API key.
Press the Connect to Roboflow button.
If everything was done correctly, you will see the following message in the app UI:
â Successfully connected to https://api.roboflow.com.
NOTE: The app will not save your API key, you will need to enter it every time you launch the app. To save your time you can use the team files to store your credentials.
Last updated