> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.zata.prathamchopde.site/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.zata.prathamchopde.site/_mcp/server.

# From Wasabi

Use rclone to copy objects from a Wasabi bucket to a Zata bucket. rclone reads from Wasabi and writes to Zata in one command. The data passes through the computer that runs rclone.

> **Info**
>
> The Zata settings on this page were tested with rclone v1.75.2 on Zata in October 2026.

## Before you start

* A Zata bucket, and a Zata access key from the same region. See [Create a bucket](/buckets/create-a-bucket) and [Access keys](/access/access-keys).
* A Wasabi access key. In the Wasabi console, open **Access Keys** and select **Create Access Key**.
* The Wasabi region of the source bucket, for example `ap-northeast-1`. You find it in the Wasabi console.
* rclone on a computer with a fast internet connection. Install the latest version from [rclone.org](https://rclone.org/install/); on Linux run `curl https://rclone.org/install.sh | sudo bash`.

![The Access Keys page in the Wasabi console with the Create Access Key button](/_fern-img/b6c56642b233cdf71a7f736f3a3b305e78763bcb7a7b6d842ae08d4e04f45c17.webp)

## 1. Add the Wasabi remote

Replace `ap-northeast-1` with the region of your Wasabi bucket, in both places.

```bash
rclone config create wasabi s3 provider=Wasabi access_key_id=YOUR_WASABI_ACCESS_KEY secret_access_key=YOUR_WASABI_SECRET_KEY region=ap-northeast-1 endpoint=s3.ap-northeast-1.wasabisys.com
```

## 2. Add the Zata remote

For a bucket in Mumbai, use `https://bom01.zata.ai` as the endpoint.

```bash
rclone config create zata s3 provider=Other access_key_id=YOUR_ACCESS_KEY secret_access_key=YOUR_SECRET_KEY region=us-east-1 endpoint=https://idr01.zata.ai force_path_style=true no_check_bucket=true sign_accept_encoding=false
```

Two of these settings are needed on Zata:

| Setting                      | Why                                                                      |
| ---------------------------- | ------------------------------------------------------------------------ |
| `sign_accept_encoding=false` | Without it, every command fails with `SignatureDoesNotMatch` (403).      |
| `no_check_bucket=true`       | Stops rclone from trying to create the bucket. Needed for sub-user keys. |

To set up the remote step by step instead, see [rclone on Linux](/connect/command-line/rclone-linux).

## 3. Check both remotes

```bash
rclone lsd wasabi:
rclone ls zata:my-bucket
```

The first command lists your Wasabi buckets. The second lists the Zata bucket, and shows nothing while it's empty. With a sub-user key, `rclone lsd zata:` shows no buckets, so always use the bucket name.

## 4. Copy the data

Replace `my-wasabi-bucket` with the Wasabi bucket and `my-bucket` with the Zata bucket.

```bash
rclone copy wasabi:my-wasabi-bucket zata:my-bucket --progress
```

* `copy` never deletes anything. It skips files that are already the same in Zata, so if it stops halfway, run the same command again.
* For a bucket with millions of objects, add `--fast-list --transfers 16 --checkers 32`.
* If your apps still write to Wasabi during the migration, run the copy again when you switch over to Zata, to pick up the latest files.

## 5. Check the copy

```bash
rclone check wasabi:my-wasabi-bucket zata:my-bucket --one-way
```

It ends with `0 differences found` when every object is in Zata with the same content. Objects uploaded in parts have no MD5 to compare. To compare their content too, add `--download` (slower, and it downloads the files from Wasabi again).

## What rclone doesn't copy

* **Old versions.** rclone copies the current version of each object only.
* **Bucket settings.** Versioning, lifecycle rules, bucket policies and Object Lock settings stay in Wasabi. Set them up again in Zata. If you need Object Lock, turn it on when you create the Zata bucket, before you copy: you can't add it later.

## Troubleshooting

| Problem                                                          | Fix                                                                                                                                             |
| ---------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| `SignatureDoesNotMatch` or `403 Forbidden` on every Zata command | Run `rclone config update zata sign_accept_encoding=false` (rclone v1.66 or newer).                                                             |
| `AccessDenied` when copying to Zata                              | Run `rclone config update zata no_check_bucket=true`. If it still fails, check that the key may write to the bucket.                            |
| `InvalidAccessKeyId` or `NoSuchBucket` on Zata                   | The key, the endpoint and the bucket must all be in the same region. See [Wrong endpoint or region](/help/troubleshooting/endpoint-and-region). |
| Errors from the Wasabi remote                                    | Check that the Wasabi endpoint matches the bucket's region.                                                                                     |