Import from Railway

Railway projects often mix apps, services, and databases in one project graph, so scan first and decide what should map to an app versus a database before execution.

Preparation Checklist

  • Have a Railway API token with access to the target workspace/project.
  • Create the Docka server that will receive the imported resources.
  • Note any Railway-specific volume, cron, or service relationships that need manual follow-up.

1. Validate Credentials

POST /api/v1/imports/validate-credentials
{
  "platform": "railway",
  "api_key": "RAILWAY_TOKEN"
}

2. Create Import

POST /api/v1/imports
{
  "platform": "railway",
  "api_key": "RAILWAY_TOKEN"
}

3. Scan + Execute

POST /api/v1/imports/{importID}/scan
PUT /api/v1/imports/{importID}/select
POST /api/v1/imports/{importID}/execute

Recommended Review

  • Inspect the selected resource mapping before execution.
  • Double-check port exposure and start commands on each imported app.
  • Verify which databases were only discovered versus actually selected for the import.
← From Heroku Overview →