Migrations

Move applications and platform-managed workloads into Docka with a staged workflow that keeps the migration plan visible from scan to completion.

Supported Platforms

  • Heroku
  • Railway
  • Vercel
  • Render
  • Fly.io
  • Coolify

What Gets Migrated

  • Application metadata and build/runtime settings
  • Environment variables and secret placeholders when supported
  • Primary custom domain and DNS guidance for cutover
  • Database inventory, credentials, and migration recommendations
  • Resource mapping between the source platform and Docka targets

The migration detail page stores the plan, progress, selected target server, and import mapping so teams can reopen the migration later and still understand what happened.

Typical Workflow

  1. Connect the source platform using an API token.
  2. Scan the account to discover apps, databases, add-ons, and domains.
  3. Select what to import and choose the Docka target server.
  4. Review compatibility warnings before the import starts.
  5. Execute the import, then verify app behavior and database connectivity.

Operational Notes

  • Use a low-traffic window if you also need database data migration outside Docka.
  • Keep DNS TTLs low before cutover so the final switch is easier to validate.
  • Record any source-side scheduled jobs or add-ons that need a Docka equivalent.
← Stages From Heroku →