> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paradime.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Migration Checklist

> The dbt Cloud™ to Paradime migration checklist to keep the team on track and finish migration with zero hassles.

Copy these prompts into your AI assistant (e.g., ChatGPT, Claude) to convert this checklist into project-tracked tickets.

<Prompt description="Generate **Jira** tickets from the migration checklist, grouped by Epic per phase with priorities and dependency links." icon="ticket" actions={["copy"]}>
  You are a project manager. Convert the migration checklist below into Jira tickets.

  For each checklist item, create a Jira ticket with:

  * Summary: a clear, actionable title
  * Description: context on what needs to be done and any dependencies
  * Labels: "dbt-cloud-migration"
  * Epic: use the phase name (e.g., "Phase 0 - Pre-migration review")
  * Priority: Medium (unless it blocks other work, then High)

  Group tickets under their phase as an Epic. Add dependency links where one task must complete before another can start (e.g., Phase 1 tasks depend on Phase 0 completion).

  Output the tickets in a table with columns: Epic, Summary, Description, Priority, Blocked By.

  Here is the checklist:

  Phase 0 - Pre-migration review

  * Audit dev / staging / prod environments and connection settings
  * List all env vars (UI + every env\_var() call)
  * Inventory all jobs (type, cron, commands, dependencies)
  * Pick 3-4 representative pilot jobs
  * Review key-term mappings with the team

  Phase 1 - Paradime setup

  * Connect the data warehouse (dev to prod)
  * Configure Bolt schedule env vars (bulk CSV)
  * Configure Code IDE env vars
  * Verify IDE with dbt debug
  * Kick off SSO / Okta configuration with IT

  Phase 2 - Run the importer

  * Create scoped paradime service token (Account Admin, one project)
  * Connect dbt Cloud integration + Test Connection
  * Run import, review paused Bolt schedules
  * Validate cron, commands, overrides, triggers per schedule
  * Resolve state:modified+ deferral targets and cross-project chains

  Phase 3 - Pilot run

  * Enable pilot schedules (dev, then prod)
  * Disable the same jobs in dbt Cloud (paused, not deleted)
  * Monitor \~2 days vs dbt Cloud history
  * Re-point externally-triggered pilot jobs to the Bolt API

  Phase 4 - Full cutover

  * Enable remaining schedules per workspace, upstream first
  * Disable equivalent dbt Cloud jobs (keep 1-2 weeks)
  * Migrate CI checks to Turbo CI, validate on a sample PR
  * Re-point API apps, monitoring, and alert webhooks
  * Add --target dev to dev-environment schedule steps

  Phase 5 - Hypercare

  * Monitor one full schedule cycle (daily/weekly/monthly)
  * Verify CI triggers, alerts, and Catalog freshness
  * Keep rollback path warm

  Phase 6 - Decommission

  * Delete migrated dbt Cloud jobs
  * Revoke service token
  * Cancel dbt Cloud subscription
</Prompt>

<Prompt description="Generate **Linear** issues from the migration checklist, grouped by milestone per phase with priorities and blocked-by relations." icon="ticket" actions={["copy"]}>
  You are a project manager. Convert the migration checklist below into Linear issues.

  For each checklist item, create a Linear issue with:

  * Title: a clear, actionable title
  * Description: context on what needs to be done and any dependencies
  * Label: "dbt-cloud-migration"
  * Project: "dbt Cloud to Paradime Migration"
  * Cycle/Milestone: use the phase name (e.g., "Phase 0 - Pre-migration review")
  * Priority: Medium (unless it blocks other work, then Urgent)

  Group issues by phase using milestones or sub-projects. Add "blocked by" relations where one task must complete before another can start (e.g., Phase 1 tasks depend on Phase 0 completion).

  Output the issues in a table with columns: Milestone, Title, Description, Priority, Blocked By.

  Here is the checklist:

  Phase 0 - Pre-migration review

  * Audit dev / staging / prod environments and connection settings
  * List all env vars (UI + every env\_var() call)
  * Inventory all jobs (type, cron, commands, dependencies)
  * Pick 3-4 representative pilot jobs
  * Review key-term mappings with the team

  Phase 1 - Paradime setup

  * Connect the data warehouse (dev to prod)
  * Configure Bolt schedule env vars (bulk CSV)
  * Configure Code IDE env vars
  * Verify IDE with dbt debug
  * Kick off SSO / Okta configuration with IT

  Phase 2 - Run the importer

  * Create scoped paradime service token (Account Admin, one project)
  * Connect dbt Cloud integration + Test Connection
  * Run import, review paused Bolt schedules
  * Validate cron, commands, overrides, triggers per schedule
  * Resolve state:modified+ deferral targets and cross-project chains

  Phase 3 - Pilot run

  * Enable pilot schedules (dev, then prod)
  * Disable the same jobs in dbt Cloud (paused, not deleted)
  * Monitor \~2 days vs dbt Cloud history
  * Re-point externally-triggered pilot jobs to the Bolt API

  Phase 4 - Full cutover

  * Enable remaining schedules per workspace, upstream first
  * Disable equivalent dbt Cloud jobs (keep 1-2 weeks)
  * Migrate CI checks to Turbo CI, validate on a sample PR
  * Re-point API apps, monitoring, and alert webhooks
  * Add --target dev to dev-environment schedule steps

  Phase 5 - Hypercare

  * Monitor one full schedule cycle (daily/weekly/monthly)
  * Verify CI triggers, alerts, and Catalog freshness
  * Keep rollback path warm

  Phase 6 - Decommission

  * Delete migrated dbt Cloud jobs
  * Revoke service token
  * Cancel dbt Cloud subscription
</Prompt>

***

**Phase 0 - Pre-migration review**

* [ ] Audit dev / staging / prod environments and connection settings
* [ ] List all env vars (UI + every `env_var()` call)
* [ ] Inventory all jobs (type, cron, commands, dependencies)
* [ ] Pick 3–4 representative pilot jobs
* [ ] Review key-term mappings with the team

**Phase 1 - Paradime setup**

* [ ] Connect the data warehouse (dev → prod)
* [ ] Configure Bolt schedule env vars (bulk CSV)
* [ ] Configure Code IDE env vars
* [ ] Verify IDE with `dbt debug`
* [ ] Kick off SSO / Okta configuration with IT

**Phase 2 - Run the importer**

* [ ] Create scoped `paradime` service token (Account Admin, one project)
* [ ] Connect dbt Cloud™ integration + Test Connection
* [ ] Run import, review paused Bolt schedules
* [ ] Validate cron, commands, overrides, triggers per schedule
* [ ] Resolve `state:modified+` deferral targets and cross-project chains

**Phase 3 - Pilot run**

* [ ] Enable pilot schedules (dev, then prod)
* [ ] Disable the same jobs in dbt Cloud™ (paused, not deleted)
* [ ] Monitor \~2 days vs dbt Cloud™ history
* [ ] Re-point externally-triggered pilot jobs to the Bolt API

**Phase 4 - Full cutover**

* [ ] Enable remaining schedules per workspace, upstream first
* [ ] Disable equivalent dbt Cloud™ jobs (keep 1–2 weeks)
* [ ] Migrate CI checks to Turbo CI, validate on a sample PR
* [ ] Re-point API apps, monitoring, and alert webhooks
* [ ] Add `--target dev` to dev-environment schedule steps

**Phase 5 - Hypercare**

* [ ] Monitor one full schedule cycle (daily/weekly/monthly)
* [ ] Verify CI triggers, alerts, and Catalog freshness
* [ ] Keep rollback path warm

**Phase 6 - Decommission**

* [ ] Delete migrated dbt Cloud™ jobs
* [ ] Revoke service token
* [ ] Cancel dbt Cloud™ subscription


## Related topics

- [Migration Playbook](/guides/migrations/dbt-cloud-tm-importer/migration-from-dbt-cloud-playbook.md)
- [Changelog](/changelog/overview.md)
- [Migrations](/guides/migrations/index.md)
- [Confluence Tool](/products/dino-ai/tools-and-features/confluence-tool.md)
- [customize-agent](/products/dino-ai/slack-agent/customize-agent.md)