Docs
Get Started

Migration

Kuberns migrations are source-driven. The AI agent can detect deployment configuration, but it does not automatically copy every external database, file, DNS record, secret, or provider-specific service.

Standard migration sequence

  1. Inventory source, processes, variables, data stores, files, domains, and scheduled work.
  2. Connect the repository and deploy a non-production environment.
  3. Provision required managed resources.
  4. Import data and persistent files.
  5. Validate logs, metrics, jobs, and integrations.
  6. Lower DNS TTL.
  7. Perform the final data sync.
  8. Point DNS to Kuberns and monitor.
  9. Retain the previous service until rollback risk is acceptable.

Provider guides:

Migrate from HerokuMap a Heroku application, process types, add-ons, configuration, and domains to Kuberns.Migrate from RenderMove Render web services, workers, data stores, variables, and domains to Kuberns.Migrate from RailwayMove Railway services, variables, data, and domains to a Kuberns project.Migrate from VercelAssess whether a Vercel workload should run as a long-running Kuberns service.Migrate from DigitalOceanMove an App Platform or Droplet workload to Kuberns.Migrate from AWSMove directly managed AWS application infrastructure into the Kuberns operating model.