diff --git a/jenkins/4-custom-transformers.md b/jenkins/4-custom-transformers.md
index 1cf4658..612d274 100644
--- a/jenkins/4-custom-transformers.md
+++ b/jenkins/4-custom-transformers.md
@@ -318,4 +318,4 @@ Thats it! Congratulations you have overridden Valet's default behavior by custom
 
 ## Next lab
 
-[Forecast Jenkins Usage](../jenkins/5-forecast.md#forecast-the-runner-usage-of-a-jenkins-instance)
+[Perform a production migration of a Jenkins pipeline](5-migrate.md)
diff --git a/jenkins/6-migrate.md b/jenkins/5-migrate.md
similarity index 100%
rename from jenkins/6-migrate.md
rename to jenkins/5-migrate.md
diff --git a/jenkins/5-forecast.md b/jenkins/6-forecast.md
similarity index 100%
rename from jenkins/5-forecast.md
rename to jenkins/6-forecast.md
diff --git a/jenkins/readme.md b/jenkins/readme.md
index 94414af..9b76a0f 100644
--- a/jenkins/readme.md
+++ b/jenkins/readme.md
@@ -58,8 +58,8 @@ Perform the following labs to test-drive Valet
 2. [Perform an audit of a Jenkins server](2-audit.md)
 3. [Perform a dry-run of a Jenkins pipeline](3-dry-run.md)
 4. [Use custom transformers to customize Valet's behavior](4-custom-transformers.md)
-5. [Forecast potential build runner usage](5-forecast.md)
-6. [Perform a production migration of a Jenkins pipeline](6-migrate.md)
+5. [Perform a production migration of a Jenkins pipeline](5-migrate.md)
+6. [Forecast potential build runner usage](6-forecast.md)
 
 ## Troubleshoot the Valet CLI