First draft of CLI import docs

Author: drakirnosslin

site/content/docs/cli/cli-vs-terraform-pulumi.md

@@ -1,7 +1,7 @@
 ---
 title: CLI vs. Terraform & Pulumi - Checkly Docs
 displayTitle: CLI vs. Terraform & Pulumi
-weight: 9
+weight: 10
 menu:
   platform:
     parent: "CLI"

site/content/docs/cli/command-line-reference.md

@@ -240,3 +240,41 @@ Copy Playwright config into the Checkly config file.
 ```bash
 npx checkly sync-playwright
 ```
+
+## `npx checkly import`
+
+Import resources not yet managed by the CLI from your account. See [Importing an existing account](/docs/cli/import/) for details.
+
+### `npx checkly import plan`
+
+Generate code for all resources to be imported:
+```bash
+npx checkly import plan [--root] [--config]
+```
+
+- `--root`: Specify the directory where the generated code should be placed. Default is the `checkMatch` directory in your `checkly.config.ts/js`
+- `--config` or `-c`: Location of your `checkly.config.ts/js` file. Default is current directory.
+
+### `npx checkly import apply`
+Applies a plan generated by `npx checkly import plan`:
+```bash
+npx checkly import apply [--config]
+```
+
+- `--config` or `-c`: Location of your `checkly.config.ts/js` file. Default is current directory.
+
+### `npx checkly import commit`
+Commits a plan applied by `npx checkly import apply`:
+```bash
+npx checkly import commit [--config]
+```
+
+- `--config` or `-c`: Location of your `checkly.config.ts/js` file. Default is current directory.
+
+### `npx checkly import cancel`
+Cancels a generated plan that has not been commited yet:
+```bash
+npx checkly import cancel [--config]
+```
+
+- `--config` or `-c`: Location of your `checkly.config.ts/js` file. Default is current directory.

site/content/docs/cli/import.md

@@ -0,0 +1,36 @@
+---
+title: Importing your account - Checkly Docs
+displayTitle: Importing your account to the Checkly CLI
+navTitle: Importing an existing account
+weight: 9
+slug: /import
+menu:
+  platform:
+    parent: "CLI"
+    identifier: import-cli
+---
+
+If you got started with Checkly working in the webapp you can use the `import` CLI command to download all your UI-managed resources as code and start managing your entire Checkly setup from the CLI.
+
+## How `import` works
+
+When importing an existing resource the CLI will both generate the code neccessary to manage the resource through code, and mark the resource itself as managed by the CLI, and not the UI. This allows you to start editing, and also deleting the resource through the CLI. 
+
+To ensure that you can go through this process safely, and test your setup along the way the import process is done in three separate steps: Plan, apply and commit.
+- `npx checkly import plan`: This generates the code for all resources in your account not already managed through the CLI, allowing for a review of all resources that will be imported. At this point no mapping have been created between imported resources and the existing ones in your account. A `deploy` in this state will create duplicate resources. If you cancel here, nothing will have changed for existing resources on your account.
+- `npx checkly import apply`: Links the imported resources to your CLI project, but keeps the mapping in a **pending** state. You can now make changes to resources in your account via the CLI, as the mapping has been established. As long as this mapping is **pending** you cannot delete any of the imported resources via the CLI. You are free to test your setup and deploy changes, but you will be prevented from deleting any resources until you commit your plan. You can cancel your import at this stage, but any changes made to resources through a `deploy` will persist.
+- `npx checkly import commit`: Commits the plan, removing the **pending** state from all imported resources. Imported resources can now be deleted through the CLI by removing their constructs. At this point the `import` is completed and cannot be canceled.
+
+## Importing step-by-step
+
+1. [Install the CLI](/docs/cli/installation/). At the end of the process ensure you have a `checkly.config.ts/js` file, and that you have logged in to the account you want to import resources from. You can verify the current account with `npx checkly whoami`.
+2. Run `npx checkly import plan`. This will generate the code for all resources in your account not already managed by the CLI. You can specify where the generated code should be placed using `--root`. If your Checkly config file is not in the current directory, specify the path using `--config`.
+3. Review the imported code before continuing.  You can verify imported checks with `npx checkly test`. At this point, avoid running `npx checkly deploy` as this will generate duplicate resources.
+4. Run `npx checkly import apply` to create the link between the imported resources and your CLI project. You can try out editing resources and pushing these updates to your account with `npx checkly deploy`.
+5. When you are satisfied with your setup, run `npx checkly import commit` to finalize the import.
+
+Remember that you can cancel your import with `npx checkly import cancel` at any point before running `npx checkly import commit`, but changes made to existing resources after the apply-stage will persist after cancelling.
+
+## Next steps
+
+Once you have a fully CLI managed setup you are ready to leverage Monitoring as Code to improve your setup. Check our how to [dynamically creating monitors](/docs/cli/dynamic-check-creation/), [combining MaC and Git](/docs/cli/using-git/), and how to [integrate Checkly in your CI/CD process](/docs/cicd/).