Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A guide to migrating from dbt Core to dbt Cloud #4880

Closed
1 task
runleonarun opened this issue Feb 9, 2024 · 1 comment
Closed
1 task

A guide to migrating from dbt Core to dbt Cloud #4880

runleonarun opened this issue Feb 9, 2024 · 1 comment
Assignees
Labels
content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear priority: high Technical inaccuracy, missing/incorrect information, or broken links. Negatively affects workflows

Comments

@runleonarun
Copy link
Collaborator

runleonarun commented Feb 9, 2024

Contributions

  • I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates

https://docs.getdbt.com/guides

What part(s) of the page would you like to see updated?

Requested recently by @T-Dunlap and @Stevedow99, and Inspired in part by @anaisvaillant 's idea here.

Migration guide for customers interested in moving from dbt core to dbt cloud.

Create a framework of how to think about a migration and provide a list of considerations (similar to the how to configure your dbt repository (one or many) post) so the customer has a better grasp of the amount of work and time needed.

It might help to think of workflow and how these would change:

  • people
  • dbt (cloud account, dbt cloud project and dbt project)
  • other tools they may have (orchestration, docs, BI, etc)
  • Target Audience: a data engineering lead, architect, project leader

Additional information

We can use this internal doc as a resource. It's an initial outline of helpful questions compiled by @azzam34 and others.

@runleonarun runleonarun added content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear priority: high Technical inaccuracy, missing/incorrect information, or broken links. Negatively affects workflows labels Feb 9, 2024
@mirnawong1 mirnawong1 self-assigned this Feb 15, 2024
@mirnawong1
Copy link
Contributor

mirnawong1 commented Apr 30, 2024

completed in april: https://docs.getdbt.com/guides/core-cloud-2?step=1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear priority: high Technical inaccuracy, missing/incorrect information, or broken links. Negatively affects workflows
Projects
None yet
Development

No branches or pull requests

2 participants