Skip to main content Skip to navigation Skip to footer
ENCRYPTION CONTROL

Migrate without risking your data

Moving between servers, clouds, or providers? Your encrypted backups travel safely. No exposure. No data loss.

Every vendor moves data. None keep encryption intact during transfer. Rediacc does.

$ rdc repo sync push-all
Enumerating repositories ...... 4 repos
Snapshotting gitlab (42 GB) ... encrypted
Snapshotting nextcloud (128 GB) .. encrypted
Snapshotting mailcow (84 GB) .. encrypted
Snapshotting mariadb (96 GB) .. encrypted
Transferring via encrypted channel .. 350 GB sent
Verifying integrity on secondary .. SHA-256 match
Restoring on secondary ........ 4 repos live
✓ Migration complete: 4 repositories migrated to secondary
Transferred: 350 GB    Encryption: 100%    Exposure: zero    Time: 12m 34s

Illustrative output; actual runs may include extra logs. CLI reference: rdc repo sync

0
Data Exposed During Migration
100%
Encryption Maintained
Any
Destination Supported
THE PROBLEM

Migration is when data is most vulnerable

Moving data between systems creates exposure. Temporary files, unencrypted transfers, mismatched configs. Every migration is a window of risk. And most tools lose encryption settings when you move — forcing you to reconfigure everything from scratch on the other side.

89% of enterprises operate multi-cloud, yet only 8% encrypt 80%+ of cloud data Flexera 2024 / Thales 2025 [2]
$4.88M average cost of a data breach globally IBM Cost of Data Breach 2024 [3]
$90K–$300K egress cost per petabyte when migrating encrypted data between clouds Cloud provider pricing [4]
Traditional migration
Step 1 Decrypt data
Step 2 Export to staging
Step 3 Transfer unencrypted
Step 4 Re-encrypt on target
Result Config lost
With Rediacc
Run migrate
0 exposure
Verified
THE REAL COST

What migration risk is costing you

Every migration without end-to-end encryption is a compliance incident waiting to happen.

Migration Risk Calculator

Without Rediacc
Exposure windows / year24 hrs
Data at risk per migration20 TB
Re-encryption labor$4,800
Annual migration risk
$12,528
With Rediacc
Exposure windows / year0 hrs
Data at risk per migration0 TB
Re-encryption labor$0
Annual migration risk
$0
Assumes $200/hr labor for re-encryption configuration, $4,880/TB breach premium (IBM 2024) [3], and 1% breach probability per exposure window. Rediacc maintains encryption throughout — zero exposure windows, zero re-encryption needed.
HOW IT WORKS

One command. Zero exposure.

1

Pack

Your encrypted btrfs snapshots bundle with keys, configs, and policies intact. Nothing decrypted.

2

Move

Transfer to any destination over an encrypted channel. AES-256 never drops during transit.

3

Verify

SHA-256 integrity checks confirm every byte arrived intact. Automatic rollback if anything fails.

Source Exporting
gitlab 42 GB
nextcloud 128 GB
mailcow 84 GB
mariadb 96 GB
AES-256
Encrypted Channel
Destination Verified
gitlab SHA-256 ✓
nextcloud SHA-256 ✓
mailcow SHA-256 ✓
mariadb SHA-256 ✓
UNDER THE HOOD

Decrypt-transfer-re-encrypt vs. zero-exposure migration

Traditional migration tools decrypt data before transfer, creating exposure windows where your data sits unprotected. Rediacc never decrypts during migration — encrypted btrfs snapshots transfer as sealed blocks.

Traditional Migration
Rediacc
Decrypt → transfer → re-encrypt pipeline
Encrypted btrfs send/receive — never decrypted
Encryption keys must be shared with transfer tool
Keys travel separately, customer-held at all times
Config and policies rebuilt manually on target
Encryption config, Docker settings, network routes migrate together
Integrity assumed — no automatic verification
SHA-256 checksum verification per repository post-transfer
WHY IT MATTERS

What you get

Encryption in transit

Data stays AES-256 encrypted during every step of migration. No temporary decryption at any stage.

Settings travel with data

Encryption config, customer-held keys, Docker settings, and network policies all migrate as one atomic unit.

Zero-trust transfer

No temporary decryption. No exposure windows. No intermediary ever sees plaintext data.

THE GAP

What others can’t do during migration

Most backup tools treat migration as an afterthought. Rediacc treats it as a first-class encrypted operation.

Capability VeeamRubrikCommvaultDruva Rediacc
Zero-decryption migration
Customer-held keys during transfer
Config + data atomic migration [5]
Post-transfer integrity verification [6] [7] [8] [9]
Single-command migration
Any-to-any destination [10] [11] [12]
Automatic rollback on failure [13]
We migrated 42 servers from Hetzner to OVH over a weekend. 350 TB of encrypted data transferred without a single byte exposed. Our previous migration — just 8 servers — took three weeks and required decrypting everything to a staging area. That was the last time we accepted that risk.
Zero exposure windows · 10x faster

Migrate safely, every time

Start with the free Community edition. Encrypted migration included.

Start Free Free for up to 5 repositories · No credit card required
$ rdc repo push --to secondary -m primary
Encrypt any containerized workload
Databases, mail servers, CI/CD, file storage, auth, monitoring — if it runs in a container, Rediacc migrates it encrypted.
Sources & References
  1. Flexera, “2024 State of the Cloud Report,” 2024. “Multi-cloud usage up from 87% last year to 89% this year.” www.flexera.com
  2. Thales, “2025 Cloud Security Study,” conducted by S&P Global 451 Research, 2025. “Only 8% of organizations encrypt 80% or more of their cloud data.” cpl.thalesgroup.com
  3. IBM Security, “Cost of a Data Breach Report 2024,” July 2024. “The global average cost of a data breach reached $4.88 million in 2024.” newsroom.ibm.com
  4. AWS, “Amazon S3 Pricing — Data Transfer,” 2024. “Data Transfer OUT from Amazon S3 to Internet: $0.09 per GB for the first 10 TB/month.” aws.amazon.com
  5. Commvault CommCell Migration moves entire clients including configuration, backup history, and data as a single operation. documentation.commvault.com
  6. Veeam SureBackup verifies data integrity post-transfer by booting VMs and running application-level health checks. helpcenter.veeam.com
  7. Rubrik performs automated integrity checks on ingested data using its append-only file system verification. docs.rubrik.com
  8. Commvault validates data integrity post-transfer using CRC checksums at multiple stages including Data Verification jobs. documentation.commvault.com
  9. Druva Restore Check proactively verifies backup data consistency and device snapshots on an automated schedule. help.druva.com
  10. Veeam supports cross-platform recovery including VMware-to-Hyper-V, physical-to-virtual, and cloud migrations via Instant Recovery. helpcenter.veeam.com
  11. Rubrik supports cross-platform Live Mount and export to VMware, Hyper-V, AWS, and Azure environments. docs.rubrik.com
  12. Commvault supports cross-hypervisor restores (VM conversion) between VMware, Hyper-V, AWS, Azure, GCP, and more. documentation.commvault.com
  13. Commvault Undo Failover automatically rolls back to pre-failover state by restoring original VM configuration. documentation.commvault.com
Product performance claims are based on Rediacc’s btrfs copy-on-write architecture. Calculator estimates use industry-standard cost models; actual costs vary by organization.