Generate Jira tickets from the migration checklist, grouped by Epic per phase with priorities and dependency links.
Generate Linear issues from the migration checklist, grouped by milestone per phase with priorities and blocked-by relations.
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
- 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
- Create scoped
paradimeservice 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
- 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
- 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 devto dev-environment schedule steps
- Monitor one full schedule cycle (daily/weekly/monthly)
- Verify CI triggers, alerts, and Catalog freshness
- Keep rollback path warm
- Delete migrated dbt Cloud™ jobs
- Revoke service token
- Cancel dbt Cloud™ subscription