Skip to main content

Migrate a Renku Legacy project to Renku 2.0

Time is running short! Renku Legacy was discontinued in October 2025, and you still have access to your Renkulab Gitlab projects until end of January 2026. Hence, move your code repositories as explained in our detailed migration guides and in our dedicated videos.

Learn the main steps to successfully migrate your project from Renku Legacy

The rest of this guide will explain to you how migrating a project from Renku Legacy to Renku 2.0 manually means, and walk you through the process.

tip

⚠️ If you have moved a repository to a new home (like GitHub or our new GitLab instance) and want to ensure old links, such as those in published papers, don't break, we have a solution. Simply fill out this form with your new repository location or Renku 2.0 project URL, and we will automatically redirect visitors from the old URL to the new one.

Manual Migration​

As of October 2025, Renku Legacy projects are not available anymore. Hence, you need to migrate a project manually, you can do so by creating a new Renku 2.0 project with all the same code, data, and session components. Here’s how:

  1. Create a new project in Renku 2.0
  2. Code: Add the new home of your Renku Legacy code repository to the Code section in your Renku 2.0 project
    1. See How to add a code repository to your project
  3. Data: If you use cloud storage in your project, create a data connector for the cloud storage object.
  4. Session: Add one session launcher or multiple session launchers according to the language you would like to work in your project.
    1. See Create an environment for your session

What happens to my Renku Legacy project assets?​

✅ Code Repository

Your project code repositories need to be migrated manually.

✅ ✳️ Datasets & Git LFS Data

Git LFS data, including Renku Datasets, are a part of your code repository, and will be available from inside your Renku 2.0 session via the git lfs command line tool.

Git LFS data will not be downloaded automatically upon session launch, so you must run git lfs pull inside your session.

Please, configure access to your cloud data storage provider as a Renku 2.0 Data connector.

warning

Please note that Renku 2.0 takes a significantly different approach to data compared to Renku Legacy. Read more on our blog post: Deep Dive: What's New in Renku 2.0. Consider moving your data into an external storage system and connecting it to your project via a Data connector.

✅ ✳️ Workflows

You may continue to use Renku workflows in your session via the CLI.

warning

Please note that Renku 2.0 takes a significant different approach to workflows compared to Renku Legacy. Read more on our blog post Deep Dive: What's New in Renku 2.0.

✅ Metadata

Project title, description, and keywords can be added and modified as you create your new project in Renku 2.0.

One exception is the project image, which is not supported at this time.

✅ Members

Please add members directly to your Renku 2.0 project after creating your new project.

tip

If you would like to share a set of projects with a group, you can create a Renku 2.0 group! See How to create a group.