Migrating from dbt Cloud
Move your existing dbt Cloud setup into dbdeux with a guided, reviewable wizard. You upload an export of your account, see exactly what will be created before anything changes, and apply the import in one idempotent step.
Organization owners and admins run the migration from the Organizations area.
How it works
The wizard walks through four steps, and nothing is created until the final Apply step:
- Upload manifest: Export your dbt Cloud account with the dbdeux migration tool. It produces a manifest file that captures your projects, environments, and jobs as metadata only. Secret values (warehouse passwords, keys, tokens) are never included, so the file is safe to move around.
- Validate: dbdeux checks the manifest and shows a per-project summary (repository status, warehouse adapters, environment and job counts) alongside any findings grouped by severity (error, warning, info).
- Dry-run plan: A read-only preview against the target workspace. Every item is listed with the action dbdeux would take: create it, skip it because it already exists, or skip it because it is not yet supported.
- Apply: After you confirm, dbdeux imports everything in one pass and reports how many items were created, skipped, and failed.
Each step names what it will and will not do before you take it, so the page reads as a plan rather than a form: Upload says nothing is imported yet, Validate says the checks are read-only, Dry-run plan says every action is previewed, and Apply is the only step that writes anything.
Getting the export
The migration tab hands you the tool rather than sending you to look for it. Download the CLI gives you the export tool, with the three commands to run underneath it:
- Unzip and install the tool
- Copy the example configuration, then fill in your dbt Cloud service token and account id
- Run the extract command, which writes the manifest file
The extract command is shown with a copy button, so it goes straight into your terminal. The tool reads metadata only, and your dbt Cloud credentials stay on your own machine.
Back in dbdeux you can drag the manifest onto the page, pick it from your file browser, or paste it in. The file is parsed as you provide it, so a wrong or truncated file is caught immediately instead of at the end of the wizard.
Knowing the size of the move before you start
Validation summarizes the export as counts you can sanity check at a glance: how many projects, environments, and jobs were found, and how many secrets you will need to re-enter afterward. If that last number is the one that makes you wince, it is better to see it now than halfway through a Friday afternoon.
The dry-run plan is filterable, because a plan with several hundred lines is only useful if you can narrow it. Filter to what will be created, what already exists and will be skipped, what is not yet supported, or what will need a secret afterward, and read just that slice. The same counts appear as tiles above the list, so the shape of the import is clear before you read a single row.
After you apply, the result is reported the same way: created, skipped, and failed, with a plain list of what to do next rather than leaving you to work out where you stand.
What gets imported
- Projects and their repository links
- Environments with their variable names (you re-enter secret values afterward)
- Warehouse connections for the adapters in your account
- Scheduled jobs, including their commands and cron schedules
Safe by design
- Preview first: The dry-run plan shows every action before you commit, so there are no surprises.
- Idempotent: Re-running the import skips anything that already exists instead of creating duplicates, so a second pass is always safe.
- Jobs arrive disabled: Imported jobs are always created switched off. Nothing runs on a schedule until you review it and turn it on yourself.
- Secrets stay yours: The manifest carries only the list of secrets you need to re-enter, never their values. dbdeux shows you exactly which credentials to add after the import.
After the import
Once the plan is applied:
- Re-enter the secret values dbdeux flagged (warehouse credentials, tokens)
- Review the imported environments and connections
- Enable the scheduled jobs you want running
Your dbt project code moves with your Git repository, so your models, tests, and macros come across exactly as they are once the repository is connected.