Migrating from Pterodactyl (Dockerized)

This guide is for Pterodactyl installs running in Docker - if you have a docker-compose.yml with a Pterodactyl service, you are in the right place. If you are running Pterodactyl directly on the host without containers, use the Standalone guide instead.

This guide assumes Pterodactyl's standard Docker compose setup, but it also works for Blueprint's Docker compose variant. Variable names and locations are mostly the same.

The general shape of the import is the same regardless of how Pterodactyl is running: you point the Calagopus importer at a .env file containing Pterodactyl's database connection details, and it reads everything across. The Docker-specific wrinkle is that you'll usually need to construct that .env file yourself, since database hostnames inside Docker networks don't match what's in Pterodactyl's original .env.

API keys do not migrate. See the intro for the full reasoning - in short, the hashes are not compatible and the API is not either, so old keys would not work even if they were imported.

Prerequisites

Before you start, you'll want:

• Access to your Dockerized Pterodactyl install (the directory containing the compose file and .env)
• Calagopus Panel installed but not yet configured - we need to land on the Out-of-Box Experience (OOBE) screen and stop there

Install Calagopus First

If you haven't installed Calagopus yet, follow the installation guide. Once you reach the OOBE screen, stop. Don't click through it. Don't create the admin user. Just leave it on that screen and come back here.

Don't click through the OOBE

The importer needs an empty Calagopus database to write into. The OOBE creates initial records (admin user, default settings) that would conflict with what the importer wants to do.

I already clicked through - how do I undo it?

You'll need to drop and recreate the database. Pick the matching tab for how Calagopus is installed:

Head to the directory with your Calagopus compose file and stop the stack:

docker compose down

Delete the Postgres data directory:

# This wipes the Calagopus database. Don't run this if you have data you care about.
rm -r postgres

Start Calagopus back up:

docker compose up -d

Set the Pterodactyl Directory

Most of the commands below reference your Pterodactyl install directory. To save typing, set it as a shell variable up front. If your Pterodactyl host mount is at /srv/pterodactyl, this is fine as-is; otherwise change the path:

export PTERODACTYL_DIRECTORY=/srv/pterodactyl

This isn't required - you can substitute the path inline anywhere you see $PTERODACTYL_DIRECTORY - but it makes the commands shorter.

Choose Your Calagopus Install Method

The exact commands depend on how Calagopus itself is installed. Pick the matching tab and follow along:

Building the Pterodactyl .env File

Pterodactyl's database is reachable from within the Pterodactyl containers, but likely not from your Calagopus containers - different Docker networks use different hostnames. The solution is to build a small ptero.env file with database connection details that work from where the importer will run.

The importer needs all seven of these variables: APP_URL, APP_KEY, DB_HOST, DB_PORT, DB_DATABASE, DB_USERNAME, and DB_PASSWORD. You'll find them across Pterodactyl's docker-compose.yml and .env file. A finished ptero.env looks something like:

APP_URL=https://panel.example.com
APP_KEY=xc5QXq4u3Qgi3zRP0Q9qq32mnZvl0lVY
DB_HOST=172.20.0.4
DB_PORT=3306
DB_DATABASE=panel
DB_USERNAME=pterodactyl
DB_PASSWORD=mZCcs8KInMWexDRe704T6C8swXmbP8W2M+kCpbnQuv4=

Assemble the values one at a time using the steps below.

APP_URL

This is your existing Pterodactyl domain, from Pterodactyl's docker-compose.yml or .env. Looks like:

APP_URL=https://panel.example.com

APP_KEY

From Pterodactyl's .env:

cat $PTERODACTYL_DIRECTORY/var/.env | grep APP_KEY

Looks like:

APP_KEY=xc5QXq4u3Qgi3zRP0Q9qq32mnZvl0lVY

DB_HOST

Pterodactyl's .env probably has DB_HOST=database (a Docker service name), which won't resolve from outside Pterodactyl's compose stack. Get the actual container IP instead, running from inside Pterodactyl's directory:

# Linux/MacOS
echo "DB_HOST=$(docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' $(docker compose ps -q database))"

# Windows
echo "DB_HOST=$($(docker compose ps -q database) | foreach { docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' $_ })"

Looks like:

DB_HOST=172.29.0.4

DB_PORT, DB_DATABASE, DB_USERNAME

If you haven't modified the default Pterodactyl compose file, these are all defaults:

DB_PORT=3306
DB_DATABASE=panel
DB_USERNAME=pterodactyl

If you've customized them, check Pterodactyl's .env for the actual values.

DB_PASSWORD

In Pterodactyl's docker-compose.yml or .env, look for MARIADB_USER_PASS. Copy its value and use that as DB_PASSWORD:

# In Pterodactyl's compose file:
MARIADB_USER_PASS=mZCcs8KInMWexDRe704T6C8swXmbP8W2M+kCpbnQuv4=

# Becomes in your ptero.env:
DB_PASSWORD=mZCcs8KInMWexDRe704T6C8swXmbP8W2M+kCpbnQuv4=

Assembling the File

Head to the Calagopus directory (where your compose.yml lives) and create a file called ptero.env with all seven variables.

Running the Import

Copy the ptero.env you just made into the Calagopus container:

docker compose cp ptero.env web:/.env

Now run the importer:

docker compose exec web calagopus-panel import pterodactyl --environment /.env

This walks through users, servers, nodes, allocations, eggs, and so on. Larger Pterodactyl installs take longer; small ones finish in seconds. Progress is logged to stdout.

If the import errors out

Treat the database as poisoned. Partial imports leave Calagopus in an inconsistent state. Drop the Postgres data (the steps in the OOBE warning callout above), let Calagopus recreate it empty, and re-run the import.

When the import finishes, restart the stack:

docker compose down
docker compose up -d

Log in with your existing Pterodactyl credentials.

What's Next

Wings also needs to be updated to point at the new panel. See Wings - Updating for that step.

After the migration, regenerate any API keys used by external scripts. The old Pterodactyl keys will not work, and the Calagopus API differs from Pterodactyl's, so those integrations will need to be updated regardless.