Migrate from Daytona v0

Migration from Daytona v0 moves an organization's resources to Daytona v2. When an organization is migrated, Daytona syncs its API keys, container registries, and snapshots into the organization's default project. Sandboxes are not synced: you import archived Daytona v0 sandboxes one at a time, each as a new persistent sandbox in the default project.

Snapshots arrive as named images in an older image format. Each image converts on its first Linux sandbox create, or ahead of time through image conversion. An imported sandbox boots from the last backup of its Daytona v0 sandbox and keeps the settings that Daytona v2 supports. Importing copies a sandbox and does not move it: the original keeps working on Daytona v0.

Every migration request is scoped to the organization's default project, and a request made with an API key for any other project is refused. API keys created in the default project can also be copied to Daytona v0; see Daytona v0 key sync. An organization shared with Daytona v0 also shares its single sign-on configuration.

Get the migration summary

Get a summary of what the migration brought into the organization's default project. The summary reports whether the organization was migrated from Daytona v0 and counts the API keys, container registries, and images from Daytona v0 snapshots in the default project. Images are counted separately by whether they are converted to the current format. The summary also counts the Daytona v0 sandboxes imported so far.

curl 'https://api.daytona.com/migration/v0/summary' \
  --header 'Authorization: Bearer YOUR_API_KEY'

{
  "from_v0": true,
  "api_keys": 3,
  "registries": 1,
  "images_to_convert": 4,
  "images_converted": 2,
  "sandboxes_imported": 5,
  "personal": false
}

List Daytona v0 sandboxes

List the organization's Daytona v0 sandboxes, one page at a time. Daytona reads the list from Daytona v0 on each request, so it reflects the current state of each sandbox. Each entry reports whether the sandbox can be imported now and, when it cannot, why. A sandbox that was already imported carries the ID of the sandbox the import created.

1. Go to Daytona Sandboxes ↗
2. Select the default project
3. Select Daytona v0 in the version toggle

The version toggle appears only for an organization migrated from Daytona v0.

curl 'https://api.daytona.com/migration/v0/sandboxes?limit=100' \
  --header 'Authorization: Bearer YOUR_API_KEY'

# Pass next_cursor from the previous page to get the next one
curl 'https://api.daytona.com/migration/v0/sandboxes?limit=100&cursor={nextCursor}' \
  --header 'Authorization: Bearer YOUR_API_KEY'

{
  "sandboxes": [
    {
      "v0_id": "0b6c5c43-7a52-4c1f-9a42-3f0c3d7f2a11",
      "name": "data-pipeline",
      "status": "archived",
      "class": "container",
      "importable": true,
      "last_backup_at": "2026-10-14T09:21:07Z",
      "labels": { "team": "data" },
      "cpu": 2,
      "memory_gib": 4,
      "disk_gib": 10
    }
  ],
  "next_cursor": null
}

Import a Daytona v0 sandbox

Import an archived Daytona v0 sandbox as a new persistent sandbox in the default project. The import registers the sandbox's last Daytona v0 backup as an image, converts the image to the current format, and creates the sandbox from it in the default project's region. The new sandbox waits in the queued state until the conversion finishes. The original Daytona v0 sandbox keeps working and is labeled with the ID of the sandbox the import created.

Importing the same sandbox again returns the existing import instead of creating another sandbox, unless you force a new import. When the sandbox an earlier import created was deleted or failed, the next import creates a new one.

1. Go to Daytona Sandboxes ↗ and select Daytona v0 in the version toggle
2. Click Import on the row of an importable sandbox
3. Click Import to confirm

curl 'https://api.daytona.com/migration/v0/sandboxes/{v0Id}/import' \
  --request POST \
  --header 'Authorization: Bearer YOUR_API_KEY'

# force creates another sandbox even when a live import exists
curl 'https://api.daytona.com/migration/v0/sandboxes/{v0Id}/import' \
  --request POST \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
  "force": true
}'

{
  "sandbox_id": "sbx_4kQm9TzVb2LxWp7R",
  "image_id": "img_7fJk2mQpXv9dLc3RtY",
  "status": "queued",
  "existing": false,
  "v0_labeled": true,
  "warnings": [
    "env vars not carried (sandbox secrets on Daytona v0; set them on the imported sandbox): OPENAI_API_KEY"
  ],
  "secret_env_vars": ["OPENAI_API_KEY"]
}

The import carries the following settings from the Daytona v0 sandbox and reports every dropped setting in the warnings: