Coolify Migrator

This project aims to help users who have left their data on version Coolify v3 to migrate to version v4

Note

Tested and working with Coolify 4.0.0-beta.340

Important

This project is not affiliated with the Coolify project and author!

Caution

We assume no responsibility for errors or erroneous data transmitted during migration. You are 100% responsible that the migration may fail or that you may lose data.

Migrations supported:

• Sources

  • GitHub
    • Source
    • Private keys
  • GitLab

• Databases

  • PostgreSQL
    • Container
    • Volume data migration from dump
  • MySQL
    • Container
    • Volume data migration from dump
  • MongoDB (not really planned)
  • MariaDB (not really planned)
  • CouchDB (not really planned)
  • EdgeDB (not really planned)

• Applications

  • Deployment
  • Secrets
  • Persistent Volumes

Important

Services cannot be migrated and transferred directly, due to the architecture difference between the 2 versions. We currently offer a dump transfer (volumes + databases) from where you can manually import

• Services

  • Wordpress + MySQL

How to run it:

Before migration, you need to make sure the application/service/database is running

1. Complete .env with the server connection variables

2. Import v3 database:

yarn import:db

3. Install the proxy on v4 server:

yarn proxy

4. Complete your env file with the printed values from proxy installation (V3_SECRET_KEY, V4_SECRET_KEY, V4_DATABASE)

5. Start the migration interface:

yarn start

Also, make sure to create your own API key with All (root/admin access), be careful! permissions in your v4 instance!

After migration you can run docker compose down in ~/v4-proxy to disable the production database proxy.

Feel free to contact for any support on discord: @eduh

License

This project is licensed under the MIT License.