Repository and data migration

Bring your app.
Keep your stack.

Move from Render, Heroku, Netlify, Fly.io, App Platform or another host. Use your repository or image and move data deliberately; this route does not connect to a provider API.

Deploy your repository

Before you switch

Inventory services, secrets and persistent data.

Record each service's source, build and start commands, port, environment variables and domains. Recreate these in an OpenShip project, or describe multiple services in Compose. Transfer secrets through the project settings, not your repository.

Keep an external database if its network access allows it, or restore a verified export into the destination. Copy uploaded files separately. Check provider-specific functions, storage APIs, redirects and scheduled jobs before moving traffic.

Test on a temporary domain. For a final data copy, pause writes when required and plan the interruption. Keep the source available until you have verified traffic, background jobs and data at the destination.

Deploy a Compose stack

Plan the move

Access, compatibility and the final switch.

  1. Review your stack

    List your services, environment variables, data volumes, and domains. Check the destination has enough capacity.

  2. Prepare your data

    Take an application backup and choose how to transfer it. Plan a maintenance window for stateful services.

  3. Deploy and verify

    Check logs, service health, sign-in, and stored data. Make sure the app works at its destination before switching traffic.

  4. Switch your domains

    Update routing and verify HTTPS. Retire the old deployment after checking the new app and its backups.

Choose your migration path

Review the guide for your current platform.

Railway and Vercel have guided import flows. Existing Docker servers have a separate discovery and review flow. Use those guides when they match your source.

Explore all migration options
Compare platforms

Put it to work.

Start on OpenShip Cloud or deploy on your own infrastructure.