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.
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.