diff --git a/content/docs/blueprint/migrations/docker.mdx b/content/docs/blueprint/migrations/docker.mdx
index c17b3e5..66dc6f1 100644
--- a/content/docs/blueprint/migrations/docker.mdx
+++ b/content/docs/blueprint/migrations/docker.mdx
@@ -5,15 +5,28 @@ description: Guide for migrating from Pyrodactyl to Pyrodactyl (Blueprint) using
 
 ## Migrating from Pyrodactyl (Docker)
 <Callout type='warning'>
-Always make sure you take a backup of your Pterodactyl database and other relevant data.
+Always ensure that you make a backup of your Pyrodactyl database and any other relevant data. Provided below is how you can make a backup of your Panel Database. (Replace ``panel`` with the database name you use)
+
+```
+# If using MySQL
+mysqldump -u root -p --opt panel > ./panel.sql
+
+# If using MariaDB
+mariadb-dump -u root -p --opt panel > ./panel.sql
+```
 </Callout>
 
-If you already have Pyrodactyl running in Docker, simply update your panel image in your `docker-compose.yml` file:
+If you already have Pyrodactyl running in Docker, update your panel image and add these volumes to your `docker-compose.yml` file:
 ```diff
--image: ghcr.io/pyrohost/pyrodactyl:main
-+image: ghcr.io/pyrodactyl-oss/blueprint:latest
+panel:
+   -image: ghcr.io/pyrohost/pyrodactyl:main
+   +image: ghcr.io/pyrodactyl-oss/blueprint:latest
+
+volumes:
+    + - "/srv/pyrodactyl/extensions/:/blueprint_extensions"
+    + - "app:/app"
 ```
 
 <Callout type='error'>
 Switching back from Blueprint to Pyrodactyl is not supported. We do not provide any support for this and cant guarantee that it will work. If you care about your data, **make a backup** before switching.
-</Callout>
\ No newline at end of file
+</Callout>
diff --git a/content/docs/pyrodactyl/migrations/native-to-docker.mdx b/content/docs/pyrodactyl/migrations/native-to-docker.mdx
index 8dd4df5..1a70275 100644
--- a/content/docs/pyrodactyl/migrations/native-to-docker.mdx
+++ b/content/docs/pyrodactyl/migrations/native-to-docker.mdx
@@ -5,6 +5,18 @@ description: Guide for migrating from native Pterodactyl installation to Pyrodac
 
 ## Migrating from Pterodactyl (Native → Docker)
 
+<Callout type='error'>
+Once you switch to Pyrodactyl, switching back to Pterodactyl is not supported and may cause errors as Pyrodactyl modifies the Pterodactyl Database Schema. Provided below is how you can make a backup of your Panel Database if you need to switch back. (Replace ``panel`` with the database name you use)
+
+```
+# If using MySQL
+mysqldump -u root -p --opt panel > ./panel.sql
+
+# If using MariaDB
+mariadb-dump -u root -p --opt panel > ./panel.sql
+```
+</Callout>
+
 ### Prerequisites
 
 - Linux system with root access
@@ -14,6 +26,18 @@ description: Guide for migrating from native Pterodactyl installation to Pyrodac
 - Avoid using Snap-based Docker installations on Ubuntu
 - Enable Docker auto-start on boot
 
+<Callout type='error'>
+Once you switch to Pyrodactyl, switching back to Pterodactyl is not supported and may cause errors. Provided below is how you can make a backup of your Panel Database if you need to switch back. (Replace ``panel`` with the database name you use)
+
+```
+# If using MySQL
+mysqldump -u root -p --opt panel > ./panel.sql
+
+# If using MariaDB
+mariadb-dump -u root -p --opt panel > ./panel.sql
+```
+</Callout>
+
 ### Pyrodactyl Installation
 
 1. Create a new folder (e.g. `pyrodactyl-panel`) on your server in a safe location, and switch to it.
@@ -51,6 +75,7 @@ description: Guide for migrating from native Pterodactyl installation to Pyrodac
    ```
 
 1. If your database is running on the same machine as your panel, set it to listen on the IP `172.17.0.1`, and change the `DB_HOST` environment variable to `172.17.0.1`.
+
 1. Rename `docker-compose.example.yml` to `docker-compose.yml`
 1. Run the following command to start the panel:
    ```bash
diff --git a/content/docs/pyrodactyl/migrations/native-to-native.mdx b/content/docs/pyrodactyl/migrations/native-to-native.mdx
index 139181b..621eba6 100644
--- a/content/docs/pyrodactyl/migrations/native-to-native.mdx
+++ b/content/docs/pyrodactyl/migrations/native-to-native.mdx
@@ -5,10 +5,16 @@ description: Guide for migrating from native Pterodactyl installation to native
 
 ## Migrating from Pterodactyl (Native → Native)
 
-<Callout type="warn">
-  Before making any changes, back up your entire panel directory and database.
-  Pyrodactyl modifies the database schema, and rolling back to Pterodactyl may
-  result in data loss or instability.
+<Callout type='error'>
+Once you switch to Pyrodactyl, switching back to Pterodactyl is not supported and may cause errors as Pyrodactyl modifies the Pterodactyl Database Schema. Provided below is how you can make a backup of your Panel Database if you need to switch back. It is also recommended that you make a backup of the Pterodactyl folder aswell if anything goes wrong during migration. (Replace ``panel`` with the database name you use)
+
+```
+# If using MySQL
+mysqldump -u root -p --opt panel > ./panel.sql
+
+# If using MariaDB
+mariadb-dump -u root -p --opt panel > ./panel.sql
+```
 </Callout>
 
 ### Prerequisites
diff --git a/content/docs/pyrodactyl/migrations/native-update.mdx b/content/docs/pyrodactyl/migrations/native-update.mdx
index 134968d..4442335 100644
--- a/content/docs/pyrodactyl/migrations/native-update.mdx
+++ b/content/docs/pyrodactyl/migrations/native-update.mdx
@@ -10,8 +10,15 @@ Newest release version:
 ![Pyrodactyl Latest Release](https://img.shields.io/github/v/release/pyrohost/pyrodactyl?style=for-the-badge)
 
 <Callout type="warn">
-  Before proceeding with any updates, make sure to back up your database and
-  panel files.
+  Before proceeding with any updates, make sure to back up your database and panel files. Provided below is how you can make a backup of your Panel Database. (Replace ``panel`` with the database name you use)
+
+```
+# If using MySQL
+mysqldump -u root -p --opt panel > ./panel.sql
+
+# If using MariaDB
+mariadb-dump -u root -p --opt panel > ./panel.sql
+```
 </Callout>
 
 ### Prerequisites