Merge pull request #491 from OpenFn/v2-v2-migration

add v2-v2 migration steps

docs/migration/automated-migration.md

@@ -35,7 +35,7 @@ workflows, runs, and features you desire for your v2 project.
 
 #### Setup and Deployment to v2
 
-4. In a code editor, create a new `config.json` file with the following content:
+4. In a code editor on your computer, create a new `config.json` file with the following content:
 
 - `apiKey`: Specify your API Key/ Personal Access Token from your v2 user
   account. See [this page](../manage-users/api-tokens.md) for how to to create
@@ -121,11 +121,14 @@ local deployment of the v2), you can also leverage the OpenFn
 sure you have the latest version of the CLI installed
 ([see CLI basic docs](../docs/build-for-developers/cli-intro.md)).
 
-::: info v2-to-v2 Migration Guide coming soon! 
+1. Export the project you want to migrate from your v2 instance. Go to
+   `Settings`, and under `Setup` click `Export project`. Your `project.yaml`
+   file will be automatically downloaded.
+2. Follow the steps for
+   [Setup and Deployment to v2](#setup-and-deployment-to-v2)
+   in the section above.
 
-A detailed guide on how to
-migrate projects between two instances of OpenFn v2
-([lightning](https://github.com/OpenFn/lightning)) is coming soon.
+:::info More on local deployment
 
 To learn more about OpenFn deployment, be sure to check out our
 [planning guide](https://docs.openfn.org/documentation/deploy/options) and