NHR/HLRN Project Migration

Starting 2024/Q2, all NHR/HLRN new projects are created in the HPC Project Portal. Projects started before that point are known as legacy projects. Since the start of 2026, legacy projects can no longer be used until they are migrated to the Project Portal.

Preparing for Migration

Migration is a multi-step process:

  1. The PI/s must create Academic Cloud accounts if they do not already have them. In many cases, one already has an Academic Cloud account as part of the federated institutional login. Otherwise, create an account.
  2. The PI/s must login to Academic Cloud at least once and get their usernames (go to the Account page) or provide the email address their Academic Cloud account is listed under.
  3. (Optional) Any number of non-PI project members do steps 1 and 2 as well and collect their usernames or email addresses their accounts are listed under.
  4. If migrating unprompted (before renewal), a member of the project (a PI or someone authorized by the PI/s) must start a support ticket requesing migration (see Getting Started to get the right email address). If the PI/s have been contacted about migrating, they must simply reply. In both cases, the usernames of the PI/s and any other members to migrate (or email addresses listed under their Academic Cloud) must be provided as well as to which user all existing files/directories should have their ownship changed to.
  5. We will get confirmation from every PI who did not send the migration request or do the migration response. This is done to ensure all PIs are on board.
  6. The PI/s (or who they designate) must make an appointment for the day the migration is to take place. This is important because the project must not be used during the migration process.
  7. The migration takes place on the agreed upon day. Note that all the project’s Slurm jobs that have not finished before the migration begins will be cancelled. The migration will take up to 1 day to complete.

Changes During Migration

Migrating a project to the HPC Project Portal brings with it many changes which are summarized below:

Changes for The Project

The project undergoes the following changes during migration:

  1. POSIX group changes from PROJECT to HPC_PROJECT. This is accompanied by a GID change.
  2. The new Slurm account is created.
  3. New data stores are created.
  4. The owner and group of the old data stores are changed to the new POSIX group and the project-specific username of one of the PI/s or some other member the PI/s choose/s. Note that this means the legacy users can no longer access the project data.
  5. Filesystem quotas on the old data stores are rebuilt.

Changes for The Project Members

The following changes happen to the members of the project during the migration:

  1. The legacy NHR/HLRN usernames of the members lose access to the project data due to the change in project POSIX group.
  2. If the PI/s are migrating members, the members gets a new project-specific username in the new project using their Academic Cloud account which:
    1. Gets a new HOME directory and other data stores.
    2. Made a member of the new POSIX group of the project, thereby giving access to the project data.
    3. Added to the project’s new Slurm account.

Personal directories of legacy NHR/HLRN usernames will not be migrated and are retained until the start of 2027. To migrate data from your legacy NHR/HLRN username to your new one, see the Data Migration Guide.