From 947e5bab57466c319909f6641c4b105530faeb3f Mon Sep 17 00:00:00 2001 From: myronkaifung <97630035+myronkaifung@users.noreply.github.com> Date: Mon, 25 Nov 2024 10:02:44 -0800 Subject: [PATCH] Update project-migration.md --- pages/guides/playbooks/project-migration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/guides/playbooks/project-migration.md b/pages/guides/playbooks/project-migration.md index a606d449c4..b7739f42f1 100644 --- a/pages/guides/playbooks/project-migration.md +++ b/pages/guides/playbooks/project-migration.md @@ -107,7 +107,7 @@ curl --request GET \ If you choose to export a subset of events to bring over to your new project, you can leverage the `event` or `where` parameters to query for the specific event data you’re looking to migrate. ## Step 4: Transform Data -Upload the exported event data to your storage object, the process here may vary depending on the data warehouse you use. Our [warehouse connector](/docs/tracking-methods/data-warehouse) supports integrations with BigQuery, Snowflake, Databricks, and Redshift. +Upload the exported event data to your storage object, the process here may vary depending on the data warehouse you use. Our [warehouse connector](/docs/tracking-methods/warehouse-connectors) supports integrations with BigQuery, Snowflake, Databricks, and Redshift. Checklist before running transformations: