# Migrate from Nodus Compute 0.x

> What moves to the new Nodus automatically, what you recreate, and how the CLI, SDK, agents and billing change.

Source: https://nodus-platform-site.pages.dev/docs/guides/migrate-from-0x/
Build revision: 211ad9f836655b1c3a2668c4693e442471f28614

Nodus 1.0 carries over your account, sign-in and organization memberships. Each migrated user receives $30 in free starter credit once, subject to email verification. Runs, Sandboxes and API keys must be recreated.

## What moves automatically

|From 0.x|In Nodus 1.0|
|-|-|
|Email/password, Google or GitHub sign-in|Your existing sign-in method|
|Your account and organization memberships|An org with a `default` project and your mapped member role|
|An account without an organization|Your sign-in is preserved; create your first org during onboarding|

The old billing system used sandbox payments. Its balances, debt, saved cards, payments and invoice history do not carry over. Add a payment method in the new console when required to run work.

## Your $30 starter credit

The grant is once per user across all organizations and expires 30 days after it is granted. If you already received starter credit in the new platform, migration does not grant it again, even if it has expired.

Verified users with an imported organization receive the grant when that organization is released. If your email is not verified, verify it and open an organization you belong to; the console claims your credit automatically. If you have no organization, create one during onboarding. Your entitlement remains available while you complete these steps; its 30-day expiry starts only when the grant is issued.

## Cutover timeline

Follow the announced cutover dates for pausing work and downloading outputs. The old service is kept available for the announced read-only window; running work and stored outputs are not copied into the new platform.

## What you recreate

* **API keys.** 0.x keys (`nk_…`) stop working. Sign in with `nodus login` or create a new key in the console.
* **Runs, Sandboxes and 0.x workspaces.** They are not copied. Download any files you need before the cutover date in your notice; the 0.x API keeps serving reads for 30 days afterwards. Recreate workspaces as `Workspace` resources.
* **BYOC pools and hosts.** Recreate pools and enroll hosts in the new platform.
* **Cloud accounts.** Re-connect AWS and GCP accounts as `CloudAccount` resources and remove the old role or grant.

## Update your tools

1. **Upgrade the SDK and CLI.** `pip install -U nodus-compute` installs 1.0 under the same package, import and command names. The 1.0 API is new: a 0.x `Workload` becomes a `Job`, and `nodus run` replaces the 0.x submit commands. On first run, 1.0 moves an old `~/.nodus` config aside to `config.0x.bak`.
2. **Sign in again.** Run `nodus login`. `NODUS_BASE_URL` still works as an alias of `NODUS_API_URL` for this major version, with a warning.
3. **Reconnect coding agents.** Hosted MCP clients prompt you to authenticate again; local clients follow the setup at [/connect](https://nodus-platform-site.pages.dev/connect/).
4. **Update CI.** The 0.x GitHub Action fails with a migration message. Use `nodus-compute/run-action@v1` with a new API key.

## Billing changes

Start-up and shutdown time is now billed

0.x started the meter when your command started. Nodus 1.0 bills rented machines from the moment they are created until their deletion is confirmed, at provider cost ÷ 0.875, and itemizes each charge as `Boot`, `Running`, `Restore` or `Teardown`. The same run can cost more than it did on 0.x, and the estimate shows each part before you launch.

Links to 0.x docs pages redirect to their 1.0 equivalents, and old console links open a page that helps you find the object in the new console.