Move your data.
Keep your rhythm.
A deliberate move, from the first dry run to the final read.
Start with an inventory.
Record object counts, total bytes, metadata, version history and application dependencies. Agree a change window. Keep the source intact until the destination has been verified. Check your current provider’s outbound transfer charges.
Connect the source.
Add your existing S3 provider as a named remote. The CLI prompts for the remote credentials. Use read-only access on the source and create a destination bucket in SIS3. Replace the example source endpoint with your provider’s endpoint.
sis3 login
sis3 remote add previous \
--endpoint https://s3.example.com
sis3 bucket create my-projectPreview. Copy. Verify.
First inspect the dry run, then copy without deleting the source. Sync copies current objects and their metadata; it does not transfer historic versions, bucket policies or lifecycle rules. Recreate those separately.
sis3 sync remote://previous/my-project \
s3://my-project --dry-run
sis3 sync remote://previous/my-project \
s3://my-project
sis3 verify remote://previous/my-project \
s3://my-project --checksumSwitch when the checks agree.
Checksum verification reads both sides and may incur transfer charges. Quiesce writes, run a final incremental sync and verify counts, bytes and content. Switch your application endpoint, test reads and writes, and keep the old configuration available for rollback. Delete the source only after your retention window and owner approval.