This wiki was updated to MediaWiki 1.37. If you notice any issues, please report them to admin[at]

SDB:How to migrate to SLE

Jump to: navigation, search

This topic is getting more interesting with Closing The Leap Gap when openSUSE Leap 15.3 and newer will be newly based on binary rpms from SUSE Linux Enterprise Server 15.

The only supported migration path by SUSE at this moment is openSUSE Leap -> SUSE Linux Enterprise Server.

The following is the current abstract procedure to migrate from openSUSE Leap 15.3 to SUSE Linux Enterprise Server 15 Service Pack 3:

  1. You will need to install yast2-registration and suseconnect-ng (was SUSEConnect prior 15 SP4).
  2. Register your system with a valid SUSE Linux Enterprise Server 15 Service Pack 3 Beta registration code.
  3. Run yast2 migration to migrate your system and reboot.
  4. If something fails or you want to try the procedure again use snapper rollback to restore changes on the filesystem.

Emergency Rollback

We recommend using btrfs based installation and snapper openSUSE:Snapper_Tutorial for effortless rollback. Installing the rollback-helper will help you to clean up SCC in case you'd like to revert filesystem changes and the entire registration process.

Migration from openSUSE Leap to SUSE Linux Enterprise Server

This section will cover a standard openSUSE Leap to SUSE Linux Enterprise Server migration.

It's updated to match the required steps to migrate openSUSE Leap 15.3 Beta to SUSE Linux Enterprise Server 15 SP3 Public Beta.

What about older Releases? You can follow the same steps to migrate Leap 15.2 to SUSE Linux Enterprise 15 SP2, but all of the rpms will have to be replaced and that will take significantly longer. Additionally, you'll have to allow vendor change for rpms (openSUSE -> SUSE LLC). The last step is no longer required in-migration from Leap 15.3 to SLES 15 SP3.

Sle2leap zypper in.png

Install tools for registration

(30 seconds) In this section, we will install yast2-registration which also installs the required suseconnect-ng. rollback-helper is only needed in case that migration would not work as expected and you'd like to use snapper rollback to revert filesystem changes and clean up the SUSE Customer Center registration.

Please note that yast automatically creates snapshot prior both registration and migration.

Open terminal and execute:

$ sudo zypper in yast2-registration rollback-helper 
# to enable the rollback service
$ sudo systemctl enable rollback 

Sle2leap yast2 register.png

Register your system

(30 seconds) You'll need a valid SCC login and a registration code for this step. You should request on from

# This will ask for a valid SUSE Linux Enterprise Server Registration code
$ sudo yast2 registration 

Sle2leap yast2 migration summary.png

The migration

(2 minutes for repo refresh) We recommend using yast2 instead of zypper migration because our openQA test suite uses yast2.

This part might ask you to resolve conflicts, in case you have some on your system, e.g. that you use 3rd party repositories, or e.g. devel repositories from OBS.

$ sudo yast2 migration

11.4 NET installer-list.png

Reboot to SUSE Linux Enterprise Server

Reboot to SUSE Linux Enterprise Server.

# And we're done
sudo reboot 

Sle2 leap rollback.png

Need to rollback?

Something didn't go too well? Or perhaps you've changed your mind and would like to get the system to the state before migration or registration? It's quite easy.

sudo snapper list
# selected revision prior to migration or registration
sudo snapper rollback $REV 
sudo reboot # and that's all