How to migrate from AWS S3 to Storivo

Because Storivo speaks the standard S3 API, moving off Amazon S3 doesn't require rewriting your application; it requires changing an endpoint and copying your objects. Most teams complete the cutover in an afternoon. Here's the process we walk customers through.

1. Get your Storivo access key and endpoint

Once your plan is set up, you'll get an access key ID, a secret access key, and a region-specific endpoint URL (for example https://s3.storivo.com). These work the same way as AWS credentials: any tool that authenticates against S3 will authenticate against Storivo.

2. Create a destination bucket

Create a bucket on Storivo with the same name (or a new name, if you'd rather keep things separate during testing). If you plan to use Object Lock for ransomware protection, enable it now: it can only be turned on when a bucket is created, not added retroactively. See the Object Lock guide if that applies to you.

3. Point your existing tools at Storivo

Most S3 clients and SDKs accept a custom endpoint. With the AWS CLI, for example, add --endpoint-url to any command:

aws configure set aws_access_key_id YOUR_STORIVO_KEY --profile storivo
aws configure set aws_secret_access_key YOUR_STORIVO_SECRET --profile storivo

aws s3 ls --profile storivo --endpoint-url https://s3.storivo.com

If that lists your new bucket, you're ready to copy data.

4. Bulk-copy your data

For most migrations, a sync tool is faster and safer than a one-time copy, since it can resume if interrupted. Using the AWS CLI against both endpoints:

aws s3 sync s3://your-old-aws-bucket s3://your-storivo-bucket \
  --source-region us-east-1 \
  --endpoint-url https://s3.storivo.com \
  --profile storivo

Tools like rclone work well too, and are often easier for very large buckets because they support parallel transfers and better retry handling:

rclone config   # add a remote for AWS S3, and one for Storivo (type "s3", provider "Other", set the Storivo endpoint)
rclone sync aws-s3:your-old-bucket storivo:your-storivo-bucket --progress

5. Point your application at the new endpoint

Update your application's S3 endpoint, access key and bucket name (via environment variables, a config file, or your CDN/origin settings) and deploy. Because the API surface is compatible, this is usually a configuration change rather than a code change.

6. Verify, then decommission the old bucket

Run a spot check (object counts, total size, and a handful of file checksums) to confirm the copy matches. Once you're confident, you can set a lifecycle policy on the old AWS bucket or delete it outright to stop paying for duplicate storage.