Gitpod Classic Shutdown: How to Migrate to Ona Before October 15

How to fix it

Try these in order — the most common fix is first.

1. 1. Create an Ona account

   Copy steps
   1. Sign up at app.ona.com with a new account, since Classic credentials do not carry over
   2. Note that Ona docs say new customer signup is closed, so check whether your organization can be invited instead
   Did this fix it? Yes No

2. 2. Convert your configuration

   Copy steps
   1. Start an environment in Ona
   2. Run gitpod env migrate to convert .gitpod.yml
   3. Replace it with devcontainer.json and automations.yml
   Did this fix it? Yes No

3. 3. Save your work

   Copy steps
   1. Push code to Git: content already pushed does not need downloading
   2. Download any workspace content you want locally; per Gitpod, this had to be done by the cutoff date
   3. Recreate secrets and projects manually in Ona
   Did this fix it? Yes No

Symptoms

You open gitpod.io and cannot log in or start a workspace, or your .gitpod.yml no longer works.

Why it happens

• Gitpod Classic pay-as-you-go ended on October 15 (announced September 2, 2025)
• Classic logins do not carry over to Ona
• Migration is not automatic: secrets, projects, configs and workspace data stay behind
• The .gitpod.yml file is deprecated

This guide also covers

• gitpod classic shutdown
• gitpod classic sunset
• gitpod classic migrate to ona
• gitpod env migrate

Other Gitpod errors

• Gitpod / Ona Environment Disappeared or Deleted: Archive and Auto-Delete Explained
• Ona (Gitpod) Credits Running Out: How OCUs Are Used
• Gitpod Classic Billing: Usage Limit Reached, Credits and Invoices
• Ona AWS Runner Failed: ROLLBACK_COMPLETE and ECS Circuit Breaker Errors
• Ona Environment Fails: AWS account policy blocks ssm:SendCommand
• Ona Environment Starts Then Stops in Seconds (Custom CA Bundle)
• Ona GCP Runner Not Connected: Terraform, Health Check and Zone Resource Errors
• Gitpod Classic JetBrains Gateway Not Working or Workspace Won't Start