docs(instance): add instance moving guide

Author: bene2k1

pages/instances/reference-content/moving-instances-between-az-and-projects.mdx

@@ -0,0 +1,72 @@
+---
+meta:
+  title: Moving Scaleway Instances between Availability Zones and Projects
+  description:  Find out how to move Scaleway Instances between Availability Zones and Projects.
+content:
+  h1: Moving Scaleway Instances between Availability Zones and Projects
+  paragraph:  Find out how to move Scaleway Instances between Availability Zones and Projects
+dates:
+  validation: 2025-07-15
+  posted: 2025-07-15
+categories:
+  - compute
+tags: instance migration
+---
+import Requirements from '@macros/iam/requirements.mdx'
+
+This guide explains how to move a Scaleway Instance (Virtual Machine) from one Availability Zone (AZ) to another or from one Project to another, regardless of whether the Instance uses Local Storage or Block Storage.  
+You can perform these actions using the Scaleway console, CLI, or API.
+
+<Requirements />
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- An [Instance](/instances/how-to/create-an-instance/)
+- The [Scaleway CLI](/docs/scaleway-cli/quickstart/) installed (for CLI-based instructions)
+- A valid [API key](/iam/how-to/create-api-keys/) with sufficient permissions (for API-based instructions)
+- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+
+<Message type="important">
+- Moving an Instance between AZs requires creating a snapshot of the Instance’s data and launching a new Instance in the target AZ, as direct migration of a running Instance is not supported.
+- Moving an Instance between Projects involves transferring ownership of the Instance or its snapshot.
+- Local Storage is tied to the Instance’s hypervisor and cannot be directly moved across AZs. Block Storage volumes can be detached and reattached within the same AZ but require additional steps for cross-AZ migration.
+- Ensure the target AZ supports the desired Instance type. Refer to the [Instances datasheet](/instances/reference-content/instances-datasheet/) for details.
+</Message>
+
+## Moving an Instance between Availability Zones
+
+### Creating a snapshot
+
+1. In the Scaleway console, navigate to **Compute > CPU Instances**, select your Instance, and go to the **Storage** tab to view attached volumes (Local or Block Storage).
+
+2. From the Instance’s **Storage** tab, click **+ Create snapshot**. A popup displays.
+     - Select the volume to snapshot, choose a name, and select the snapshot type (LSSD for Local Storage, BSSD for Block Storage).
+     - Click **Create snapshot**.
+     - Repeat for all volumes attached to the Instance if you need a full backup.
+     <Message type="note">
+        Snapshots can be created without stopping the Instance. However, for data consistency, pause heavy write operations if possible.
+    </Message>
+
+### Exporting the snapshot to Object Storage
+
+Snapshots must be exported to a Scaleway Object Storage bucket in the same region as the source and destination AZs to move them across AZs.
+
+#### Exporting Local Storage snapshots via the console
+   - Navigate to **Local Storage > Snapshots**, select the snapshot, and click **Actions > Copy to bucket**.
+   - Enter a file name for the QCOW2 export (ensure it ends with `.qcow` or `.qcow2`) and select an Object Storage bucket in the same region.
+   - Click **Copy snapshot to bucket**. Wait for the export to complete (status turns green).
+
+#### Exporting Block Storage snapshots via CLI
+- For recent snapshots, managed by the Block Storage API, use the following command to export the snapshot to an Object Storage bucket in the same AZ as the snapshot.
+     ```bash
+     scw block snapshot export-to-object-storage zone=<zone-to-target> snapshot-id=<snapshot-id> bucket=<bucket-name> key=<qcow2-file-name>.qcow2
+     ```
+    Replace `<snapshot-id>` with the snapshot ID, `<bucket-name>` with your Object Storage bucket name, and `<qcow2-file-name>` with the desired file name.
+
+
+- For legacy volumes, managed by the Instances API, usee the following command:
+     ```bash
+     scw instance snapshot export-to-object-storage zone=<zone-to-target> snapshot-id=<snapshot-id> bucket=<bucket-name> key=<qcow2-file-name>.qcow2
+     ```
+     Replace `<snapshot-id>` with the snapshot ID, `<bucket-name>` with your Object Storage bucket name, and `<qcow2-file-name>` with the desired file name.
+
+
+### Importing the Snapshot into the destination AZ