
This page gives a quick overview of what migrating from Statsig Cloud to Statsig Warehouse Native looks like. If you're an enterprise customer on Statsig Cloud and want to use Statsig Warehouse Native, work with your Statsig contact to evaluate feasibility. If all (or most) of your metrics come from your data warehouse already, migration is relatively simple. Migration only changes where metrics are computed: Statsig sources them in your warehouse with WHN.

## Migration overview

1. Statsig creates a WHN project alongside your current project.
2. Test this project without changing anything in your app. Re-analyze some experiments you've already run on Statsig Cloud, using exposures from production and metrics from your warehouse.
3. To move forward, re-create in the WHN project all the metrics you need, on top of data in your warehouse.
4. Pick a migration date. Plan for a 24-hour change freeze on Statsig. (Admins can continue to make changes if you need to respond to an incident.)
5. During the migration window:
   a. Statsig copies the metrics from your WHN project to your current project.
   b. Statsig turns your current project into a WHN project.
   c. Statsig runs validation and then asks you to help validate project health.
   d. For any in-progress experiments, select scorecard metrics from the WHN metric set.
6. Migration is complete. There are minor differences in experience for your Statsig users. Prepare them for this.

The migration pattern is designed to keep the risk to your SDKs at zero. If there are issues, the impact is limited to delays in generating scorecard results, and are easily recoverable.
