diff --git a/.gitbook/assets/2.40-navigate-to-stack.gif b/.gitbook/assets/2.40-navigate-to-stack.gif
new file mode 100644
index 00000000..eee97671
Binary files /dev/null and b/.gitbook/assets/2.40-navigate-to-stack.gif differ
diff --git a/.gitbook/assets/2.40.0-Migrate-a-stack.png b/.gitbook/assets/2.40.0-Migrate-a-stack.png
new file mode 100644
index 00000000..27ea6ffb
Binary files /dev/null and b/.gitbook/assets/2.40.0-Migrate-a-stack.png differ
diff --git a/.gitbook/assets/2.40.0-Migrate-to-K8s.png b/.gitbook/assets/2.40.0-Migrate-to-K8s.png
new file mode 100644
index 00000000..9694b6d8
Binary files /dev/null and b/.gitbook/assets/2.40.0-Migrate-to-K8s.png differ
diff --git a/.gitbook/assets/2.40.0-Rename-a-stack.png b/.gitbook/assets/2.40.0-Rename-a-stack.png
new file mode 100644
index 00000000..19a59325
Binary files /dev/null and b/.gitbook/assets/2.40.0-Rename-a-stack.png differ
diff --git a/user/docker/stacks/migrate.md b/user/docker/stacks/migrate.md
index e8b3ee66..5761bfa4 100644
--- a/user/docker/stacks/migrate.md
+++ b/user/docker/stacks/migrate.md
@@ -8,13 +8,34 @@ metaLinks:
To migrate, duplicate, or rename a stack, open your environment, go to **Stacks**, and select the stack you want to change.
-
+
## Migrating a stack
-In the **Stack duplication / migration** section, select the destination environment for the stack, and optionally define a new name for the stack. Click **Migrate**.
+### Docker Compose to Kubernetes migration
-
+{% hint style="warning" %}
+Migrating Docker stacks to Kubernetes is currently an experimental feature and is not recommended for production workloads.
+
+Before starting the migration, we recommend [taking a backup](../../../admin/settings/general.md#back-up-portainer).
+{% endhint %}
+
+Portainer allows you to migrate your Docker Compose workloads to Kubernetes. This feature uses the [Kompose](https://kompose.io/) tool to convert Docker Compose definitions into Kubernetes resources.
+
+From the stack you want to migrate, select **Migrate this stack**. In the dialog box that appears, select your Kubernetes environment as the destination for the migration, then complete the fields as described below. Click **Migrate**.
+
+| Field | Overview |
+| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Namespace | Specify the [namespace](../../kubernetes/namespaces/) you wish to migrate to. If the namespace you enter does not exist, a new one will be created during migration. |
+| Convert to Helm chart | Toggle this on to convert your stack to a Helm chart. Note that if migrating to a Helm chart, the preview function will no longer be an option. |
+
+
+
+### Migration between Docker environments
+
+From the stack you want to migrate, select **Migrate this stack**. Select the destination environment for the stack, and optionally define a new name for the stack. Click **Migrate**.
+
+
Migrating does not relocate the content of any persistent volumes that may be attached to the stack. Acknowledge this warning and confirm the migration by clicking **Migrate**.
@@ -22,16 +43,16 @@ Migrating does not relocate the content of any persistent volumes that may be at
## Duplicating a stack
-In the **Stack duplication / migration** section, give the new stack a descriptive name then select the environment the stack should duplicate to. When you're ready, click **Duplicate**.
+From the stack you want to duplicate, select **Migrate this stack**. Give the new stack a descriptive name then select the environment the stack should duplicate to. Click **Duplicate**.
-
+
## Rename a stack
-In the **Stack duplication / migration** section, give the stack a new descriptive name and select the environment that the stack is currently on. When you're ready, click **Rename**.
+From the stack you want to rename, select **Migrate this stack**. Give the stack a new descriptive name and select the environment that the stack is currently on. Click **Rename**.
-
+
-Renaming creates a new stack instance and does not transfer the content of any persistent volumes that may be attached to the stack. Acknowledge this warning and confirm the migration by clicking **Rename**.
+Renaming the stack creates a new stack instance and does not transfer the content of any persistent volumes that may be attached to the stack. Acknowledge this warning and confirm the migration by clicking **Rename**.
