AWS S3 to Azure Blob Storage Migration Guide

Introduction

• This is the complete onboarding task flow for migrating data from AWS S3 storage to Azure blob storage.
• Complete each step in the order listed. Links to corresponding Knowledge Base articles are provided.

Prepare the Source Environment

• Create an account with AWS S3 read-only access.
  
  Notes:
  • When creating the user account, there is a tab labeled Attach existing policies directly. This contains a policy named AmazonS3ReadOnlyAccess. This is the policy that needs to be attached to this user account. Read the How do I create an AWS S3 account with read access? article.
  • When creating this account, the final page will show the access key ID and secret access key.
    
    Note: In order for the secret access key to be displayed, you need to click Show.
    
    Important: Write down the key, or download the key file to your computer before you press "Close" or "Cancel"; otherwise, you will not be able to retrieve the secret access key in the future. Later, if you cannot retrieve the secret access key, you will have to delete the Keys you created, and then create new Keys.
  • The Access Key ID and the secret access key need to be entered when creating your MSPComplete Source endpoint.

Prepare the Destination Environment

• Create an account with AWS S3 read-only access.
  
  Notes:
  • When creating the user account, there is a tab labeled Attach existing policies directly. This contains a policy named AmazonS3ReadOnlyAccess. This is the policy that needs to be attached to this user account. Read the How do I create an AWS S3 account with read access? article.
  • When creating this account, the final page will show the Access Key ID and secret access key.
    
    Note: In order for the secret access key to be displayed, you need to click Show.
    
    Important: Write down the key, or download the key file to your computer before you press "Close" or "Cancel"; otherwise, you will not be able to retrieve the secret access key in the future. Later, if you cannot retrieve the secret access key, you will have to delete the Keys you created, and then create new Keys.
  • The Access Key ID and the secret access key need to be entered when creating your MSPComplete Destination endpoint.

MSPComplete Steps

1. Create the customer. Read the View, Add, and Edit Your Customers article.
2. Create the Source and Destination endpoints. Read the View, Add, and Edit Customer Endpoints article.
   • For the Source endpoint:
     • Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type, select Amazon S3.
     • Enter the AWS Access Key ID and AWS secret access key in the fields provided. 
       
       Note: These were generated and obtained when following the steps in this guide under Prepare the Source Environment.
   • For the Destination endpoint:
     • Click Endpoints > Add Endpoint > Enter endpoint name > For endpoint type, select Amazon S3.
     • Enter the AWS Access Key ID and AWS secret access key in the fields provided. 
       
       Note: These were generated and obtained when following the steps in this guide under Prepare the Source Environment.
3. Purchase licenses. From your MSPComplete dashboard, click Purchase > Cloud Storage Migration > Select MigrationWiz-Cloud Storage, and enter the number of licenses you wish to purchase.
   
   Notes:
   • Steps to see how much storage has been used on S3: Open Account -> Account activity: https://aws-portal.amazon.com/gp/aws/developer/account/index.html?ie=UTF8&action=activity-summary > Click the [+] button near the Amazon Simple Storage Service and you will see detailed statistics for storage used, bandwidth, and requests.
   • Purchase enough licenses to cover your migration. Each license allows up to 10GB of data per bucket to be migrated. Therefore, if you have two (2) AWS S3 buckets, one with 45GB of data, and one with 58GB of data, then you need a total of 11 licenses: 5 licenses for the first bucket, and 6 licenses for the second.

MigrationWiz Steps

1. Create the Cloud Storage Migration project. Read the How do I set up a document migration project in MSPComplete? article.
   • Create the Cloud Storage Migration project > Select the customer > Select the Source endpoint > Select the Destination endpoint. Click the Save button.
2. Add items to the project: Select Quick Add, and specify the container (bucket) name for the Source, and the container (bucket) name for the Destination. Repeat for each container (bucket). Read the How do I add items to my migration project? article.
3. Set the Project Advanced Options. Read the What project Advanced Options are available? article.
   • Set the value for maximum licenses to consume per item, per pass. The default value is one license per item, which allows up to 10GB to be migrated. However, If you have S3 buckets with more than 10GB of data, then you will need to increase the licensing count to a number that will cover your migration. In the example above (under Purchase licenses), the largest bucket is 58GB. Therefore, this licensing count should be set to 6, since this is set in increments of 10GB. Read the How do I enable consumption of multiple licenses for a single item? article.
     
     Important: Leave the Source: AWS S3 bucket name field as MigrationWizArchive and the Destination: AWS S3 bucket name MigrationWizArchive. These are the default values.
4. Run Verify Credentials. Read the How do I verify credentials? article.
5. Perform the migration: Select the items > From the top navigation, click the Start button > From the drop-down list, select Full Migration > Click the Start Migration button. Read the How do I start a migration? article.
6. Click the pie chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. Read the How do I request statistics for my migration project? article.

Post-Migration Step

• Decommission the Source S3 storage account.