Migrating CloudBees Jenkins Platform to CloudBees CI

Migrating a client controller instance from CloudBees Jenkins Platform to CloudBees CI

Back up your CloudBees Jenkins Platform client controller instance before starting your migration.
The minimum requirement for such a backup is to save a copy the $JENKINS_HOME directory from your CloudBees Jenkins Platform client controller instance. If the BUILD_DIRECTORY is outside the $JENKINS_HOME directory, then you must save a copy of this directory as well.

Ensure you have stopped your CloudBees Jenkins Platform client controller instance.
```
sudo service jenkins stop
```
Install the client controller for CloudBees CI on traditional platforms.
Create a copy of the jenkins directory (from your old CloudBees Jenkins Platform client controller installation) for CloudBees CI (named cloudbees-core-cm) and change the ownership of this new directory to the new cloudbees-core-cm user:
```
cd /var/lib/
sudo cp -rf jenkins/* cloudbees-core-cm/
cd cloudbees-core-cm/
sudo chown -R cloudbees-core-cm:cloudbees-core-cm .
```
Start your new CloudBees CI client controller instance.
```
sudo service cloudbees-core-cm start
```
Uninstall the CloudBees Jenkins Platform client controller:
- On Ubuntu or Debian.
  sudo apt-get purge jenkins
- On Red Hat, CentOS, Fedora or Amazon Linux 2.
  sudo yum remove jenkins
- On OpenSUSE.
  sudo zypper remove jenkins
( Optional ) If the migration of your client controller instance to CloudBees CI ran successfully, you can remove the old CloudBees Jenkins Platform client controller directory:
```
rm -rf /var/lib/jenkins
```

Migrating an operations center Instance from CloudBees Jenkins Platform to CloudBees CI

Back up your CloudBees Jenkins Platform operations center instance before starting your migration.
The minimum requirement for such a backup is to save a copy the $JENKINS_HOME directory from your CloudBees Jenkins Platform operations center instance. If the BUILD_DIRECTORY is outside the $JENKINS_HOME directory, then you must save a copy of this directory as well.

Ensure you have stopped your CloudBees Jenkins Platform operations center instance.
```
sudo service jenkins-oc stop
```
Install the operations center for CloudBees CI on traditional platforms.
Create a copy of the jenkins-oc directory (from your old CloudBees Jenkins Platform operations center installation) for CloudBees CI (named cloudbees-core-oc) and change the ownership of this new directory to the new cloudbees-core-oc user:
```
cd /var/lib/
sudo cp -rf jenkins-oc/* cloudbees-core-oc/
cd cloudbees-core-oc/
sudo chown -R cloudbees-core-oc:cloudbees-core-oc .
```
Start your new CloudBees CI operations center instance.
```
sudo service cloudbees-core-oc start
```
Uninstall the CloudBees Jenkins Platform operations center:
- On Ubuntu or Debian.
  sudo apt-get purge jenkins-oc
- On Red Hat, CentOS, Fedora or Amazon Linux 2.
  sudo yum remove jenkins-oc
- On OpenSUSE.
  sudo zypper remove jenkins-oc
( Optional ) If the migration of your operations center instance to CloudBees CI ran successfully, you can remove the old CloudBees Jenkins Platform operations center directory:
```
rm -rf /var/lib/jenkins-oc
```