Migration
Your work comes with you.
Your next chapter starts here.
Import your service configuration from Render, Railway, or Vercel. Review the architecture before you apply it, and move your data and traffic with a deliberate plan.
Bring the right pieces
A considered move.
Connect and inspect.
Choose an import provider in the new-service flow. Supply a provider token and select the workspace or project you want to bring over.
Review your blueprint.
Check services, build settings, environment variables, and connections. Rename or remove what you don’t need before applying.
Test. Then move traffic.
Deploy, inspect logs, migrate data where needed, and test the new endpoint before updating your custom-domain DNS.
From Render or Railway.
Bring service configuration and connections into a project blueprint. Render environment groups and secret files are carried across. PostgreSQL data can be imported through the supported database flow.
See what gets importedFrom Vercel.
A Git-connected Vercel project becomes one Helicarrier service, with framework settings and variables from the environment you choose. External database URLs stay as they are; database data is not copied.
Read the Vercel guideMake the cutover intentional
Configuration is only the beginning.
Move your data carefully
PostgreSQL import is supported. Use engine-specific tools for other databases and validate the result before directing writes to the new service.
Plan the DNS change
Keep the source service available while you test. Attach the custom domain and use the DNS records shown by the new service.
Keep tokens short-lived
Provider tokens are used for the import and are not persisted. Revoke temporary tokens after the migration is complete.
Ready when you are
Make something.
We’ll keep it running.
Bring your code. Give your next idea a home on Helicarrier Cloud.