Why choose cloud data migration to IDrive® e2?

Cost

  • No ingress, egress, or API charges
  • Predictable Pricing
  • 90% cheaper than AWS

Security

  • Protection against ransomware
  • Object lock for data immutability
  • eleven 9s of data durability

High Performing

  • Secure upload/download of data
  • Single-tier storage with quick data access
  • 14 edge locations across continents

Get started

Configure source

Add details of your current cloud storage provider

Select source data set

Choose the buckets or objects you want to migrate

Select IDrive® e2 destination

Add a region and bucket location for migration

Migrating data to IDrive® e2 cloud storage

To migrate data to IDrive® e2,

  1. Sign in to IDrive® e2 account via any browser.
  2. Navigate to the 'Data Migration' tab, and click 'Migrate data'.
  3. Select a service provider - AWS, Wasabi, Backblaze, and S3 Compatible Storage - from the dropdown.
  4. Configure the source of migration by selecting the options as applicable:
    1. Access Key ID - Enter the access key for your service provider.
    2. Secret Key - Enter the secret key for your service provider.
    3. Source regions - Select a region from the dropdown or click 'Add Source Endpoint' in the dropdown and add the source endpoint URL.
    4. Source endpoint - Enter the endpoint URL for your service provider.
  5. Click 'Configure Source'.
  6. Select the bucket that you wish to migrate and click 'Next'.
  7. Select the destination region in IDrive® e2 where you want to migrate the data.
  8. Choose a destination bucket or folder from the list or create a new bucket.
  9. Click 'Import'. The process of data migration will start. You can view the progress of the migration, estimated time of completion, and copied object size under 'Status' in the 'Data Migration' tab.
  10. You can pause the data migration by clicking , resume migration by clicking , or delete the migration from the list by clicking . You can also restart a failed migration by clicking .

Note:

  • Altering or modifying the data at the source location while the migration is ongoing can cause data corruption and IDrive® e2 will not be responsible for any such incident.
  • Only the latest version of objects will be migrated.