How to Migrate from Amazon WorkDocs to Office 365

Introduction

Our purpose is to act as an intermediary between various web technologies that don't play nice together. We take your files from one place and copy them to another. No downloads and nothing to watch over—our web-hosted app does all the work!

Undertaking any corporate migration is a daunting task. When moving from Amazon WorkDocs to Office 365, there are many things to consider. Our team has done this enough times to have learned a thing or two. We hope this guide helps you migrate successfully from Amazon WorkDocs to Office 365.

If you experience any issues, please do not hesitate to ask us questions!

Rocket

File Processing Summary

When we transfer a file, a temporary copy is downloaded from Amazon WorkDocs to a temporary server and then uploaded to Office 365. Upon successful upload, that file is deleted from the temporary server. When your migration is complete, that temporary server is destroyed. Any log data expires in 90 days and is never retained by us. We do not perform any actions beyond copying files and folders and sharing permissions. We never perform delete operations.


Communicating with Stakeholders

A migration is a significant undertaking for any organization. Trying to grasp the entire extent of all data and communicating with your employees is complicated. We sympathize!

Before, during, and after a migration, it will be of utmost importance to communicate clearly and effectively with your user base. We will provide timely support and communication materials to your transition team to help you communicate these changes with each stakeholder.

Management — Management will need good, succinct information about the how’s and why’s of the migration such as costs, benefits, and expectations. You will need to paint a clear picture of what a successful migration should look like. Granular information is important when running a department.

For example, the Sales Manager needs to know how operations will be affected, such as: can employees still work over the weekend if needed?

End Users — These are your bread and butter employees. They need to know when changes are taking place and who to go to with questions or issues.

Key questions to address:

  • Why are we migrating our data?
  • How does it impact me?
  • What are the benefits?
  • How disruptive is this change going to be?
  • What are the differences between Office 365 and Amazon WorkDocs, and how do I reconcile them?

Third Parties — If people outside your organization have access to collaborate on documents, this could potentially be interrupted and require re-sharing of data. We talk about best practices for this later in our guide.

IT Helpdesk/Support Staff — If your organization is large enough to have specific support staff for other employees, they will need to understand each step of the migration.


Planning

Planning is the hardest part of a migration. It is also one of the most critical phases to get right. To have a smooth and stress-free migration, you need to gather relevant organizational information, determine project timelines, and mitigate any surprises that may appear.

Gathering Information

Prior to migrating, it is important to gather all the information you need to run the migration smoothly. Make sure you have confirmed the information from the checklist below.

Migration Information Checklist

  • Number of users to migrate
  • Data ownership
  • Data distribution
  • Amount of data to move
  • Number of files to move
  • Individual file sizes and/or file sizes on average
  • Who is your migration team?
  • Who is your designated contact with us?
  • Who is our point of contact with you?

Scanning

To help with your planning, we offer a scanning feature. Our scan identifies how many users own data and how much there is to move.

This scan is effectively a simulated dry-run migration, with no set destination, which helps to identify any problematic files/folders before you begin migrating data.

Note: the scan is available in our Migration Manager once you have first set up a migration.

Keep reading through our guide to better understand the full migration process or skip ahead to Setting Up the Migration. For detailed instructions on how to run the scan, go to Scanning.

Number of Users to Migrate

Each "user" is defined by a unique source and destination pairing.

For example:

  • user01@example.com => user02@example.com
  • user01@example.com => user03@example.com

These would be considered two separate "user licenses" because they have different destinations.

Migrations are run on a per-user basis. Because of our app's scalable infrastructure, it is feasible to run dozens of users or thousands simultaneously. Any number of users can be migrated in whatever pre-defined order or grouping you desire.

Collaborators-only: Your fiscal budget need only include users that own data in Amazon WorkDocs. Anyone that strictly engages as a collaborator in Amazon WorkDocs (i.e., they only share other users' content) will not have any data copied and therefore will not incur a fee.

Setting permissions is free. Users that strictly collaborate in Amazon WorkDocs will receive equivalent sharing permissions in Office 365 for free.

Data Ownership

Data ownership needs to be considered. If a user has only shared data, and absolutely no owned data, we will transfer 0 files from Amazon WorkDocs to Office 365 for that particular individual.

Definitions:

  • Shared data are files and folders that are not owned by the user. When permissions are applied in Office 365 after transferring, folders will be shared again with the appropriate users.
  • Owned data are files and folders that are owned by the user. Data almost always needs to have an owner within your organization. This is the only data that we actually transfer.
  • Ownership is typically determined by who created the file or folder, but in some cases it can depend on the owner or creator of the parent (upper or top level) folder.

Data Distribution

Determining the distribution of data across the user base is an extremely important component of a migration because we copy data in a highly parallel manner, and our servers transfer data as fast as each cloud storage provider can handle. Both Amazon WorkDocs and Office 365 have rate limits for how fast data can be downloaded and uploaded.

The more users simultaneously being transferred, the higher our throughput for your migration. We highly recommend that users with very large data sets be broken into smaller accounts to facilitate faster transfers.

Note: To maximize throughput, users should not own > 5 TB of data. The more users you have and the smaller the amounts of data they own, the faster your migration will go.

For example:

If one user owns 10 TB of data, we recommend dividing that between 10 users so that each one owns 1 TB.

If data cannot be broken up, this should not hinder other users from migrating. But as a general rule, users with a lot of data require a lot of time to migrate.

Amount of Data to Move

Knowing the total volume of data you are moving helps to create a more realistic timeline for your migration.

Your Migration Team

Establish a migration team to lead your organization through the project. The team’s role includes liaising with us, undergoing training, and notifying employees of each change during the migration process.

An IT Manager or the Head of IT could be a good choice for our point of contact because they will understand the ins and outs of your organization's systems. To ensure a smooth, successful migration, we will work closely together and be with you every step of the way.


Timelines

Be Realistic

The amount of time required to plan, execute, and wrap up a migration depends on many factors. Organizational requirements, budget, security reviews, and support from management are just a few.

We typically see corporate transfers take a minimum of 30 days to plan and execute. Ensure you allot yourself enough time for each stage, which we cover later on in this guide.

Evaluate Your User Base

It is critical that you plan which users are migrating and when. Ask yourself questions like these:

  • Is the entire organization migrating, or just a few users?
  • Is everyone migrating at once, or are you splitting them into batches like department, office, or region? If so, why?
    • Note: Batching migrations this way increases complication and may extend your migration.

We recommend migrating during a slower organizational period, such as the weekend, to avoid work interruptions.

Keep Your Accounts Active

When migrating from Amazon WorkDocs to Office 365, you need to ensure all your users are active and accessible. Knowing exactly when your Amazon WorkDocs may shut down or expire is key to safely planning enough time to migrate.

Consider Migration Speed Factors

We're the fastest way to migrate your data, but the speed of your migration may still be affected by bottlenecks. Speed bottlenecks include, but aren't limited to, the following:

  • Number of files and folders being moved
    • This is objectively the biggest speed limit on the Internet, as it determines the total number of operations required. Most providers rate limit their ingress to 1 file per second per user. This isn't universally true, but it's a baseline conservative metric you can use when estimating.
    • Our observable average across our customers is a 2.4 MB average file size.
    • Knowing file size is necessary to estimate transfer speed. If you are not able to determine exact numbers, most services can provide reports that illustrate individual or average file size.
  • Total amount of data being moved
    • Total data can affect speed, but it is ultimately overshadowed by the number of files.
  • Server connections with the source or destination Connector
  • Complexity of permissions or sharing schemes (if applicable)

What may be surprising is how large of an impact factors other than the size of the data you are moving can have.

For example, it is common for there to be half a second of overhead per file being moved. If you are moving 200,000 files, this would be 200,000 seconds or more than two days' worth of overhead alone!

Suffice to say, we cannot give you exact estimates on time because there are too many factors at play at any given point. By the time you have read this section we could have easily copied several files totalling many GB or a few hundred files equalling a small amount of data.

We are always happy to have a conversation with you about estimates.

Notify Stakeholders About the Migration

Your employees have different needs with respect to their data, and it is paramount to know what those are. Take a shopping list of all departments, contact their managers, and identify key concerns in their processes and applications.

Keep in mind that while cloud storage is sometimes just a container for files, people might also be using it with third-party apps or for more advanced collaboration.

Example Emails to Send

Subject: ATTENTION: Decision to Migrate from Amazon WorkDocs to Office 365

Message: A few months ago, management decided we will leaving Amazon WorkDocs and transition to Office 365. In Office 365, all employees will have access to cloud storage and its included apps.

We will manage the migration to ensure all of our data gets transferred securely and efficiently. Please let me know if you have any questions or concerns about the process.

Subject: ATTENTION: Important Information Regarding Cloud Data Migration

Message: As you know from prior emails, we are moving from Amazon WorkDocs to Office 365 as our cloud storage provider.

To assist in this migration, we ask all employees to finish working and upload any last changes to files in Amazon WorkDocs by 17:00 PT on Friday, April 7, 2020. Changes to files or data in Amazon WorkDocs after this time will not be moved.

On Monday, April 10, 2020, all employees will be using Office 365.

Questions and concerns can be directed to your immediate manager and/or our technical support staff via the usual channels.


Connectors

What is a Connector?

A Connector is what we call our link to your cloud storage accounts.

To set up a transfer, you must grant us access to your cloud storage accounts. Without this link we are unable to communicate with them.

Creating a Connector may involve authenticating via oAuth or with normal username/password credentials. You only need to authenticate once per account.

Our authorization is lost when you delete the Connector, delete your account with us, or revoke our access through your cloud service's security settings.

Which Connector to Use for Each Microsoft Service

Microsoft Service Which Mover Connector to Use
Azure Blob Storage Azure Blob Storage Connector
OneDrive Consumer OneDrive Consumer Connector
OneDrive for Business (Administrator) Office 365 Connector
OneDrive for Business (User) OneDrive for Business (User) Connector
SharePoint Online Office 365 Connector
SharePoint on-premise Agent Connector (source Connector only) or the Microsoft SharePoint Migration Tool

Deleting Connectors

Deleting a Connector will revoke our access to your cloud storage accounts. To confirm that we have been deauthorized, visit the security settings in your respective cloud service and check for our app.

Using our app to remove our authorization with a particular cloud service is simple:

  1. From the Transfer Wizard, click Manage ▼ on the Connector type you wish to delete.
  2. Select the arrow to the right of the Connect button.
  3. Click Delete.
  4. Confirm you wish to delete, and you're done!
  5. Connector deletion process

Note: Connector deletion is permanent and cannot be reversed. The Connector type will disappear from the Transfer Wizard. To add a new Connector, click Authorize New Connector.

Reauthorizing Connectors

Reauthorizing a Connector is sometimes necessary if we lose authorization or access to your cloud storage accounts or web servers. It is also a good first step in trying to resolve most issues with your Connectors.

The process to authorize a Connector again is very simple:

  1. Find the Connector type you would like to reauthorize.
  2. Click Manage ▼.
  3. Click next to Connect to see other options for the Connector.
  4. Click on Reauthorize.
  5. Follow the same steps you performed when you first created the Connector in order to renew the authorization tokens/permissions.
    • Note: You will be unable to change the display name of the Connector. If you wish to rename it, you will have to delete and re-add the Connector.

Connectors will be deauthorized automatically if they haven't transferred any data in the last 90 days. If you try to load a deauthorized Connector in the Transfer Wizard, you will receive an error message and a prompt to reauthorize the Connector.


Migration FAQ

What gets transferred?

Only owned folders and the root files for each user will be copied. If a user is not the owner of data they can access, we will not copy it. Content may be automatically re-shared once it is migrated so that each user has access to their content exactly as before.

Does Mover sync files?

Our app offers a source-to-destination delta—when you run a transfer, we compare the destination directory to the source and only transfer new or modified files over. We call this our incremental feature.

We compare the timestamps of the files in both the source and destination and transfer the newest versions only. The incremental feature is always on.

Here are a few examples of how we deal with changes to files and folders.

Content changes: If a document is edited in your source or you have added a few new files, we will copy them to your destination on the next incremental run, overwriting the previously existing file(s) in the destination.
Name changes: If the name of a file or folder changes in Amazon WorkDocs, we will treat it as a brand new object. This can lead to duplicate files being migrated to Office 365, or worse: entire folders worth of data being duplicated from the changed folder downwards.
Example: Changing the path /Sales/Clients to /Global Sales/Clients will result in two copies of your Sales folder once the Global Sales folder is also copied during an incremental pass.

Does Mover delete files?

We never delete your data from any source. The app simply takes your data from one place and copies it to another—akin to "copy and paste" rather than "cut and paste." We also don't retain any of your cloud storage data for any reasons.

We strive to keep your users' experience as similar as possible between Amazon WorkDocs and Office 365.

How are permissions affected?

When moving from Amazon WorkDocs to Office 365, user roles *on folders* will change.

We do not explicitly set a user as an owner of data during a migration.

Ownership of files and folders is always implicitly set by virtue of copying data into a user in Office 365.

Translating Permissions

Amazon WorkDocs logo iconOld Amazon WorkDocs Role Office 365 logo iconNew Office 365 Role
  • Owner
  • Owned implicitly by receiving user or library
  • Manager [OneDrive]
  • Contributor
  • Edit
  • Viewer
  • Read

Please note that the app only sets permissions on folders.

Can I rearrange content during a migration?

Not recommended. Any major changes in directory structure should happen before or after your migration. It is also not a good idea to use the app to rearrange content.

The risks that come with rearranging content during the migration are primarily in the form of data duplication; our incremental process will see all changes as new data. So, for example, if you change a folder name at the root, we will detect that as a new folder and all of the contents will be re-transferred including all subfolders.

When sharing permissions are transferred, both owners and collaborators will receive duplicate data if content has been rearranged or renamed.

What happens to external sharing links?

Our application does not recreate external sharing links. These will have to be set in the destination manually after migration.

What about external collaborators?

We do not share content with external collaborators. This policy is in place to protect your organization, and industry best practice is to never automatically share sensitive internal data with external users.

Does Mover preserve file versions?

We do not preserve file versions. Only the most recent version of a file will be transferred from Amazon WorkDocs to Office 365 during a migration.

Does Mover notify end users?

We automatically suppress all emails to end users so they are not bombarded with excessive notifications about the data they now have access to.


Account FAQ

How do I reset my password?

From the sign in screen

Follow these steps to change your account password from the login screen:

  1. Hit Forgot password.
  2. On the next screen, enter your account email and click Reset Password.
  3. Follow the steps we send to your account email and you're done!

From your account panel

If you are already logged in to our app, you can change your password there too.

  1. When logged in, click account email in the top right corner of the app to visit your Account settings (shortcut).
  2. Select Password from the left-hand menu.
  3. Click Reset Password.
  4. Follow the steps we send to your account email and you're done!
Reset Password

How do I enable multi-factor authentication?

Follow these steps to enable multi-factor authentication:

  • Log in to the app and click your account email in the top right corner of the app to visit your Account settings (shortcut).
  • Select Password from the left-hand menu.
  • Click TURN ON under Enable 2-Step Verification.
Reset Password

Note: You will be automatically signed out of your account.

  • Log-in to your e-mail and copy the verification code sent to you.
    • If a verification code e-mail does not appear in your inbox [or spam] click "Didn't get the code? Resend now." just below the verification window in the app sign-in.
Verification Code
  • Enter the Verification Code and voila! You now have 2-Step verification enabled.
Reset Password

To turn off 2-Step verification return to the Password tab and select TURN OFF under Enable 2-Step Verification

Reset Password

How do I delete my account?

Deleting your account will delete all your scheduled transfers, multi-user migrations and authorized connectors.

Follow these steps to close your account:

  1. When logged in, click account email in the top right corner of the app to visit your Account settings (shortcut).
  2. On the left hand side, select Leave Mover.
  3. Read all of the text on that page.
  4. If you are ready, enter your current password & click Delete Account.
  5. A prompt will dropdown, and you will need to click OK

To reiterate:

  • Deleting your account will:
    1. Delete all scheduled transfers.
    2. Delete all connector authorizations.
    3. Delete any subscriptions associated with your account.
    4. Delete your Mover account.
  • This will not:
    1. Delete your transfer history. We retain these for security and compliance.
    2. Remove any trace that your account once existed with Mover.

Please Note: Deleting your account is not reversable.

Delete Account

How do I edit my email notifications?

By default you will receive an email every time a transfer finishes. To edit your email notification settings:

  1. Click on your email address in the top right of the app to visit the account settings.
  2. Select Preferences.
  3. You have the option to receive emails On Completion (default), Never, or Only on Errors.

Can I change my account email?

Unfortunately at this time, we do not allow you to change the email associated with your account.

You may, however, delete your account — losing the schedules, connector authorizations, and transfer history associated with it — and create a new account with the email you would prefer.

How do I check my transfer usage?

Checking your usage of our app will let you know the total amount of gigabytes you have transferred over the history of your account.

To check your transfer data usage, follow these simple steps:

  1. When logged in, click account email in the top right corner of the app to visit your Account settings.
  2. By default, you will already be in the Plan section.

Amazon WorkDocs FAQ

User Count

At this time, Amazon WorkDocs can sometimes return an inflated or incorrect user count to us when you load the connector in the Transfer Wizard. This number is purely cosmetic and should not affect your migration setup or migration in any way.


Office 365 FAQ

The Mover Office 365 Guide can now also be found on Microsoft Docs:

  • Office 365 to Office 365
  • Will there be unsupported files and characters?

    We automatically process file and folder names to ensure they are accepted by Office 365.

    • Files larger than 15 GB are not migrated.
    • Files with a size of 0 bytes (zero-byte files) are not migrated.
    • The following characters in file or folder names are removed:
      " * : < > ? / \ |
    • Leading tildes (~) are removed.
    • Leading or trailing whitespace is removed.
    • Leading or trailing periods (.) are removed.
    • See all invalid file or folder names and other Office 365 limitations here.

    In some possible circumstances with older sites, any file or folder ending in _files could fail. If you experience these errors please contact support.

    Microsoft currently has no file type limitations, meaning you can upload data with any file extension. Read more here.

    Character limits for files and folders

    • File names may be up to 256 characters.
    • Folder names may have up to 250 characters.
    • Total path length for folder and file name combinations may be up to 400 characters. See below for a deep dive on this topic.

    What happens to long paths?

    During a prescan, the app will automatically detect and report paths that are too long for OneDrive or SharePoint to accept. The current path length limit for Office 365 is 400 characters. The path length is calculated when going in to Office 365 and includes your tenant url, user site, path, and any character encoding.

    Example:

    This path is 93 characters long despite "Documents/Old Docs" being only 18 characters.
    https://example-my.sharepoint.com /personal /example_user /%2FDocuments%2FOld%20Docs

    If a file exists that has a very long path, the app will skip it and report it in your log files.

    To save time and headaches you are encouraged to shorten any identified long paths before you migrate.

    amazon-workdocs logo iconTurn this... office-365 logo icon...into this!
    • User's Root
      • my really really
        • really really
          • super long
            • completely
              • unncessary
                • ridiculous path
                  • with my files.pdf
                  • and stuff.xlsx
    • User's Root
      • my useful path
        • with my files.pdf
        • and stuff.xlsx
    • Site Collection
      • Site Contents
        • Documents
          • my useful path
            • with my files.pdf
            • and stuff.xlsx

    Are timestamps preserved?

    The original timestamps from Amazon WorkDocs are preserved when migrating into Office 365.

    Note: Timestamps are only applied to files/data transferred and not folders. Folders and Folder structure are created in the destination during migration and will reflect the date of the migration.

    Is file authorship preserved?

    When migrating from Amazon WorkDocs into Office 365, the "modified by" author will be preserved. However, the "created by" will be changed to the end user.

    Does the Mover app interact with the sync client in OneDrive for Business?

    We do not interact with the sync client in OneDrive for Business. We recommend disabling it prior to a migration. If you use it during a migration, it will try to sync all the migrating data.

    What happens to shared data?

    Data shared with a user by another user will appear in the Shared with me folder. Data owned by a user will appear in the user’s designated destination folder.

    What about notifications?

    The Mover app silences notifications during the migration to prevent users from being spammed.

    What happens to data shared to Office 365 Groups?

    Data shared to an Office 365 Group does not appear in the Shared with me section. Microsoft also does not notify end users that they are now a member of an Office 365 Group.

    NOTE: This is a limitation of Office 365 Groups and cannot be changed on our end.

    The user will have to navigate to the appropriate group within either their Outlook Desktop Client or by logging into their desired e-mail through outlook.office.com.

    Once the user has logged in:

    • Navigate to the left hand menu;
    • Scroll down the folder listings to "Groups";
      • If the available groups are not visible click the small arrow beside the "Groups" listing to open the group directory.
    • Select the desired group.

    From here the left hand menu should Change allowing you to open and edit Files/Notes within the selected Office 365 Group.

    What SharePoint site formats are supported?

    Both Modern and Classic sites are supported and will appear the same in our app.

    What will my file paths look like in SharePoint?

    During the migration setup (described later in this guide), you can edit the path(s) to specify where in SharePoint you would like your data to go. From the root level of SharePoint Online, you can go into Site Collections, and inside each Site Collection you will find directories for Site Contents and Subsites.

    Site Contents will take you to document libraries (ie. the Documents section) whereas Subsites will take you to the Subsites of that site collection. Navigating Subsites will take you through the same dichotomy.

    Most cloud storage providers, G Suite Drive for example, will start the listing with a user such as /user@example.com/Marketing Folder. SharePoint Online does not do this, so you would be looking at a path such as /Marketing/Site Contents/Documents.

    SharePoint Online logo iconSharePoint Online
    • Site Collection
      • Site Contents
        • Documents
          • Files.pdf
          • Stuff.xlsx
      • Subsites
        • Subsite 1
          • Site Contents
          • Subsites

    How does library permissions inheritance affect migration?

    In order for us to set specific permissions on folders in a document library, inheritance must be disabled. Permissions inheritance is typically on by default, which makes all the data within the library subject to the permissions set on the library - this is similar behaviour to team folders or team drives in other cloud services, where if users have access to the root level they will have access to everything contained within.

    If inheritance is not disabled at the root, any permissions we try to set on individual folders will be overridden by the library access permissions.

    To disable inheritance:

    In the Library settings, visit Permissions for this document library:

    • Select Stop Inheriting Permissions
      • This will allow you to select the permissions you would like to remove
        • Site members
        • Site visitors
    • Select Remove User Permissions

      This will prevent site members/visitors from inheriting permissions to all the data that we migrate into that library, allowing permissions to only those site members who we explicitly write to the folders themselves.

      Read more about SharePoint Online permissions inheritance here.

      Does Mover support Microsoft Teams?

      Microsoft Teams will appear and operate the same as a SharePoint Online site.

      What is the item limit for SharePoint Online?

      Many sites claim that SharePoint has a 5,000-item limit. This is not true. The SharePoint 5,000-item limit applies to how many items are displayed in a search list view: a maximum of 5,000.

      SharePoint sites do have file size and number limits, which are covered in detail here: SharePoint Online limits.

      Some list view options may prevent search list views with more than 5,000 items from displaying.


      Setting Up the Migration

      Authorizing Amazon WorkDocs

      To authorize or add an Amazon WorkDocs account as a Connector, follow these steps:

      1. Find Your Amazon Region

      In the AWS Console go to the WorkDocs service. In the top right-hand corner in between the account’s email address and the “Support” link, click the Region selector and note which region is highlighted.

      Note Your Region

      Use this table or the Amazon documentation page to get the Region Code for your WorkDocs installation.

      Code Name
      us-east-1 US East (N. Virginia)
      us-east-2 US East (Ohio)
      us-west-1 US West (N. California)
      us-west-2 US West (Oregon)
      eu-west-1 EU (Ireland)
      eu-central-1 EU (Frankfurt)
      ap-northeast-1 Asia Pacific (Tokyo)
      ap-northeast-2 Asia Pacific (Seoul)
      ap-southeast-1 Asia Pacific (Singapore)
      ap-southeast-2 Asia Pacific (Sydney)
      ap-south-1 Asia Pacific (Mumbai)
      sa-east-1 South America (São Paulo)

      2. Find Your Directory ID

      WorkDocs is backed by Amazon’s Directory Service. Each WorkDocs installation will have a Directory Service instance. We will need the Directory ID for the WorkDocs installation in order to grant the user access to it.

      • Click the Services Menu in the AWS Console and select “Directory Service”.
      • Find the Directory Name that corresponds to your WorkDocs installation. If you created the WorkDocs installation with the default “Simple AD” the name should be something like “corp.workdocssitename.com”.
      • Note the Directory ID in the first column or click the item and copy the ID from the details page.

      Details page:

      Find Your Directory ID

      3. Set Your IAM Access Policy

      The user you will create to give us access to your WorkDocs installation will need to be granted full access. This is accomplished using an IAM Access Policy.

      • In the AWS Console select “IAM” from the Services menu
      • Click “Policies” in the left-hand column
      • Click “Create Policy”

      Set Your IAM Access Policy

      • Click the “Select” button next to “Create Your Own Policy”
      • Enter a policy name (e.g. “WorkDocsFullAccess”) and description
      • Copy and paste the following into the “Policy Document” section:
      • Replace directory_id with the Directory ID noted earlier.
      • Click “Validate Policy”
      • Click “Create Policy”

      Apply Policy

      4. Create an IAM User

      We need to create a user that will have access to WorkDocs in order to complete the migration. This user’s key and secret will be shared with our app.

      • In the AWS Console select “IAM” from the Services menu
      • Click “Users” in the left hand column
      • Click “Create New User”
      • Enter a user name. E.g. “workdocs_migration_access”

      Create User

      • Click “Create Users”
      • Click “Show User Security Credentials”
      • Note the “Access Key ID” and “Secret Access Key”. The “Secret Access Key” will not be shown anywhere in the AWS Console again, but a new key and secret can be generated if needed.

      Access Key

      • Click “Close” or “Download Credentials” to save a CSV file with the key and secret of the user created.
      • Click on the new user in the list of users
      • Click the “Permissions” tab
      • Click “Attach Policy”
      • Find the Policy created earlier (“WorkDocsFullAccess” if you used the suggested name)
      • Click “Attach Policy”

      Attach Policy

      The user should now have full access to WorkDocs.

      5. Authorize With Us in App

      1. In the Transfer Wizard click Authorize New Connector.
      2. Auth New Connector
      3. Find Amazon WorkDocs in the Connector list.
      4. Click Authorize.
      5. Amazon Connector List
      6. A new window (tab) will open. Name your Connector (Optional).
      7. Enter your Access Key ID and Secret Access Key.
      8. Enter your Region and Directory ID.
      9. Amazon Name Connector
      10. Click Authorize again, and voila!

      Authorizing Office 365

      Warning: To fully authorize the Office 365 Connector, a Global Admin is required to grant permissions to the Office 365 Mover app within the Azure Portal.

      The Global Admin must grant these permissions AFTER the Office 365 Connector is authorized within the main Mover app.

      The instructions below show you how to complete the authorization steps in the right order.

      Some steps in the authorization process can be completed by a Global Admin or an SPO Admin. At the beginning of each step, we indicate who can complete it.

      1. Global Admin or SPO Admin: Log into the main Mover app via app.mover.io. In the Transfer Wizard, select Authorize New Connector.
      2. Note: Whether the Office 365 Connector is your source or destination connector (or both), you’ll need to go through this authorization process.

        Authorize New Connector
      3. Global Admin or SPO Admin: In the Connector list, find Office 365. Click Authorize.
      4. Authorize Office 365
      5. Global Admin or SPO Admin: A window with an Authorize button pops up. It asks you to give your Office 365 Connector a Display Name (optional).
      6. Click the Authorize button.

        Authorize Window
      7. Global Admin or SPO Admin: Follow the on-screen instructions. You will be redirected to a Microsoft login screen where you will log in with your Microsoft admin privileges and continue to authorize the connector.
      8. Global Admin or SPO Admin: After authorizing the connector, you will be redirected to the Mover Transfer Wizard and see an error like the one below. This means it is now time for a Global Admin in your tenant to grant permissions to the Office 365 Mover app in the Azure Portal.
      9. If you're an SPO Admin: Point your Global Admin to aka.ms/office365moverauth to grant permissions and finish the authorization process (steps 6 – 9).

        If you're a Global Admin: Continue with steps 6 – 9.

        Authorize Error
      10. Global Admin: Log into the Azure Portal via aka.ms/office365moverauth. You’ll see a list of Enterprise Applications.
      11. Enterprise Applications List
      12. Global Admin: Find and select the Office 365 Mover app. A page will open that provides an overview of the app.
      13. Office 365 Mover App
      14. Global Admin: In the left menu, find and open Permissions. From there, select “Grant admin consent for Mover.”
      15. Office 365 Mover App Permissions
      16. Global Admin: This opens a pop-up window that guides you through the rest of the permissions process. It will close automatically when finished. Once this is done, your Office 365 Connector is fully authorized and ready to go.

      Troubleshooting an Office 365 Connector

      Application Access Error

      If you encounter an error on authorization, try signing out of any Microsoft accounts and attempt to authorize the Connector in an Incognito Window.

      Global Admin Account Provisioning

      Your Global Admin user must have an Office 365 account provisioned in order to administer other Office 365 accounts. If you create a service account for our app, please ensure you also assigned an Office 365 license and walked through the Office 365 setup process.

      User Provisioning

      Are your Office 365 users provisioned? All Office 365 users need to have logged in to their Office 365 and opened up Office 365 in order for us to be able to transfer into their accounts. You can also provision Office 365 accounts via Windows PowerShell using the following commands (replace your URL and email appropriately):

      Connect-SPOService -Url https://example-admin.sharepoint.com -credential user@example.com

      Request-SPOPersonalSite -UserEmails “neverloggedintest@example.onmicrosoft.com”

      Office 365 Permission Requirements

      The app requires a Global Administrator for authorization. Here is a detailed list of the scopes we require:

      Permission Details
      Create, edit, and delete items and lists in all your site collections Allow the application to create or delete document libraries and lists in all site collections on your behalf.
      View your basic profile Allows the app to see your basic profile (name, picture, user name)
      Maintain access to data you have given it access to Allows the app to see and update the data you gave it access to, even when you are not currently using the app. This does not give the app any additional permissions.

      Connecting Your Source Amazon WorkDocs Account

      If you are not already connected after you have authorized your source, click Amazon WorkDocs and load the connector. An icon will appear and show you how many users you are migrating.

      Select Amazon WorkDocs Source

      Connecting Your Destination Office 365 Account

      If you are not already connected after you have authorized your destination, click Office 365 and load the connector. An icon will appear and show you how many users you are migrating.

      Select Office 365 Destination

      Creating a New Migration

      Click Continue Migration Setup and the app will move to the Migration Manager.

      How to create a new migration

      The next step is to create a user list of who is transferring.

      From your newly created migration in the Migration Manager there are two ways to add users:

      • Click the Add Users button.
      How Add Users Button
      • Or, click Migration Actions, then Add to Migration.
      How Add Users Dropdown

      You will now be able to select one of two options:

      1. Auto Discover Users.
        • Click Automatically Discover and Add Users and the app will automatically find your users and attempt to match them up.

      2. Upload Migration CSV File.
        • Either drag a file into the designated space or click Choose a file to upload and add a customized CSV file for your Migration.

      Note: CSV creation is covered in depth below.

      How to add users to migration

      Note: You will still get to finalize your migration before any data moves!

      Creating a New Migration from a CSV (Optional)

      Sometimes you have thousands of users and a complicated directory schema that you wish to import. In these cases, it's desirable to plan out your migration in a spreadsheet.

      In these cases, we hope the CSV upload option is useful. This allows you to lay out all your users and directories and then give it to us in a .csv format for us to create your migration.

      Users to migrate

      Please note your CSV file must follow this format:

      A heading for the source and destination, followed by the paths, and optionally tags on each line.

      Source Path,Destination Path,Tags
      user1@example.com,user__1@corp.example.com,"Pilot, IT"
      user2@example.com,user__2@corp.example.com,"Pilot, Sales"
      user3@example.com/src dir,user3@example.com/migrated,"Pilot, IT"
      Source Shared Drive,user4@example.com/Team Folder,"Pilot, Sales"
      https://TENANT02.sharepoint.com/sites/SiteName/Shared%20Documents,user5@example.com,"Marketing, Sales"

      Note: Ensure your CSV has no spaces after each comma separated value. Values that require commas must be wrapped in quotation marks.

      Download an example CSV here:

      Note: When URL mapping to SharePoint Online you must remove everything after /Shared%20Documents or else the URL will fail.

      For example, this full URL won't work:
      https://TENANT01.sharepoint.com/sites/SiteName/Shared%20Documents/Forms/AllItems.aspx

      It should be changed to:
      https://TENANT01.sharepoint.com/sites/SiteName/Shared%20Documents

      Example_CSV_Map.csv

      Creating your CSV in Excel

      If you are using an Excel spreadsheet to create your CSV:

      1. Ensure you have two columns, one titled Source Path, and one Destination Path.
      2. List the relative paths, domains, and usernames on the subsequent rows.
      3. Export your spreadsheet as a CSV
        1. Click File
        2. Click Save As
        3. Select CSV from the File Format options

      Reviewing Your Users

      Checking Paths

      Confirm that the users in the Amazon WorkDocs source match the users in the Office 365 destination. Usually the emails/usernames will match up, but it depends how you structure and name your users. Be diligent during this step!

      Editing

      Be aware that Users can only be edited if they haven't been scanned or had a transfer run.

      To edit a user source entry:

      1. Select a user row by clicking the respective checkbox on the left side of a row.
      2. Find User Actions on the right and directly above the user rows or right click on the user row you wish to edit the source path of.
      3. A new side panel will open allowing you to edit the Amazon WorkDocs source path.
      4. Double-click to select your parent source path and click Save to complete your edit.
      5. Edit user prompt

      To edit a user destination entry:

      1. Select a user row by clicking the respective checkbox on the left side of a row.
      2. Find User Actions on the right and directly above the user rows or right click on the user row you wish to edit the destination path of.
      3. A new side panel will open allowing you to edit the Office 365 destination path.
      4. Double-click to select your parent destination path and click Save to complete your edit.
      5. Edit user prompt

      You can also choose to edit your user entries via CSV, though this is a fairly in-depth process. If you are simply looking to make a handful of edits to your paths we recommend using the above method.

      To edit or update your current existing user pairings:

      1. Click on Migration Actions near the top right of the Migration Manager.
      2. Click on Update Migration.
      3. You will then be able to upload your .csv file. Tips for creating the CSV:
        • The CSV needs to follow this format:
          • ID, Source Path, Destination Path
          • id12345, /first.last@example.com, /f.last@example.com
        • The ID column is required to specify the existing row in the Migration Manager, whereas the source and destination path are optional - as in, you don't need to enter both if you only wish to edit the destination path, for example - and leaving both of those columns blank mean no changes will be made.
          • To get the ID for each row:
            • Find and click on Migration Actions
            • Select Customize Columns and click on ID
            • You'll now be able to see the ID appearing in each row. Please note that if you refresh the page, this information will disappear unless you select Save Column State .
          • Download an example CSV here: Example_Path_Edit.csv
      4. Adding column id

      5. Once you've created your CSV file using the above instructions and format, you can drag and drop the file into our app or click on Choose a file to upload. Changes to your user pairings will be implemented immediately.

      Update migration prompt

      Adding

      If you missed users in your original CSV upload, or simply wish to add new user entries to the current migration, you can add them via CSV. All entries added in this manner will be appended to the current migration, meaning this won't modify existing rows and it is possible to create duplicate entries alongside the ones that already exist.

      To add new users:

      1. Click on the gear icon near the top right of the Migration Manager.
      2. Click on Add to Migration.
      3. You will then be able to upload your .csv file. Tips for creating the CSV:
      4. Once you've created your CSV file using the above instructions and format, you can drag and drop the file into our app or click on Choose a file to upload. Changes to your user pairings will be implemented immediately.

      Add to migration prompt

      Duplicating

      At any time you may duplicate a user in the Migration Manager list. To duplicate a user entry:

      1. Select a user row by clicking the respective checkbox on the left side of a row. You may select more than one entry at a time.
      2. Find User Actions on the right and directly above the user rows or right click on the user row you wish to duplicate.
      3. Click Duplicate # User in the context menu.
      4. You will be prompted to click OK and a new user entry will appear. From there you can change the directory, schedule, or even the entire user.

      Duplicate user prompt

      Scheduling

      You may set an hourly, daily, weekly, or monthly schedule for each user, even after they have been run.

      To create or edit a schedule:

      1. Select the user pairing(s) you would like to schedule.
      2. Click the User Actions dropdown menu.
      3. Select Schedule # Users.
      4. Configure your Hourly, Daily, Weekly, or Monthly setup, including the timing and day of the week (where applicable).
      5. Click Apply Schedules to X Users.

      Deleting

      Be aware that users can only be deleted if they haven't been scanned or had a transfer run.

      To delete a user entry:

      1. Select a user row by clicking the respective checkbox on the left side of a row. You may select more than one entry at a time.
      2. Find User Actions on the right and directly above the user rows or right click on the user row you wish to delete.
      3. Click Delete User in the context menu.
      4. Note: This is permanent and cannot be undone unless you create a new entry.

      Delete user prompt

      Reviewing Your Permission Map

      The permission map is a very important part of your migration.

      When a user is migrated we will transfer files and folders and share any required data. We already know who is copying data, but we also need to know who might have content shared with them, even if they don't copy data.

      In order to stay organized, we'll provide a secondary list of your users called a permission map. This list includes everyone who could possibly receive sharing permissions to any files or folders that might be migrated. This even includes users who are not migrating data.

      Another important thing to consider is that usernames and emails aren't always consistent across platforms, and the permission map helps us line everyone up.

      Example: jane@example.com is actually j.smith@example.com

      We will automatically detect users and handle perfect matches. Any inconsistencies need to be manually reconciled. The permission map can be continually updated, because with each incremental pass of the migration, permissions will be reapplied.

      1. To view your permission map, click Migration Actions, located in the top right of the Migration Manager, then select Edit Permission Map from the dropdown menu.

        Edit Permission Map button

        You may either auto-discover or upload a permission map file. We automatically pair perfect matches. If a user or group in Amazon WorkDocs does not have a perfect match in Office 365 you may correct it in our interface.

      2. Click Auto-discover Users.

        Permission map auto-discover prompt

      3. You may view and edit your permission map at any time.

        Permission map overview

      Note: A blank destination entry will automatically cancel any permissions sharing for that user or group.

      Note: Adding a new line for a specific users - ie. user01@gmail.com to user01@hotmail.com - that perfectly matches auto-discovered permissions by the domain - ie. @gmail.com to @hotmail.com - will be automatically removed; as the application marks these as redundant entries.

      Uploading a Permission Map (Optional)

      You may upload a permission map in CSV format. This will overwrite any existing permission map, so please be careful. In an ideal world, all users will be matched. If there are a few unmatched users, you may manually add names to the Destination field from the web interface.

      Permission map overview

      Please ensure that your permission map follows this strict format:

      A heading for the source and destination, followed by domain names, groups, usernames, or emails.

      Source User, Destination User
      example.com, example.com
      corp.example.com, example.com
      user@example.com, differentuser@example.com
      group, group

      Permission maps should have two specific entries:

      1. Any domain names that will be wildcard matched. Eg. example.com, example.com or contoso.com, corp.contoso.com. This will instruct our app to match any users with those domain names in their source email to their new destination email domain.
      2. Imperfect matches. Users that are differently named between the source and destination domains need to be explicitly listed. Eg. firstname@contoso.com, firstname_lastname@contoso.com
      3. Groups can also be included for most connectors. These are explicitly required and are not matched with a domain wildcard. Eg. Sales Team, Global Sales Team .
      4. Please note that we will strip all leading and trailing spaces from each path value, unless it is wrapped in quotation marks.

      Download an example CSV here: example_permission_map.csv

      Creating your CSV in Excel

      If you are using an Excel spreadsheet to create your CSV, ensure you have two columns, one titled Source User, and one Destination User, and check the spelling on the domains, usernames, and groups listed.

      For example:
      Source User, Destination User
      example.com, example.com
      eric@example.com, ewarnke@example.com
      joshua@example.com, jbadach@example.com
      Sales Team,Global Sales Team

      Excel CSV overview

      Exporting a Permission Map

      You may export a permission map in CSV format.

      1. Click File
      2. Click Save As
      3. Select CSV from the File Format options

      Saving as a CSV in Excel


      Migration Manager Overview

      The Migration Manager is the key part of the application itself and the main screen you will be interacting with during the data migration process:

      Migration Manager Mover

      Migration Manager Dashboard

      One of the important points of the Migration Manager is the dashboard, which gives you a summary of your overall migration; this is covered in depth here.

      Main Menu Bar

      This is the application's main navigation bar.

      It will allow you to switch between the Migration Manager, Transfer Wizard, and your Account details; as-well-as contact support if you run into any issues during your migration.

      Migration Manager Top Menu Mover

      Migration Selection

      The Migration Selection bar allows you to navigate between separate multi-user migrations as-well-as individual Normal Transfers.

      From here you are also able to edit and personalize the names of each multi-user migration.

      Migration Manager Editing Mover

      Migration Actions

      The Migration Actions menu allows you to access things such as: the permission map and the migration reports, to the columns displayed and the overall layout of your migration to better suite your personal needs.

      Migration Manager Actions Mover

      Filters

      The Active Filters Bar allows you to search your migration for specific key terms or custom tags you have applied.

      Filter gif

      You can also view more in-depth instructions by clicking the info button directly to the right of the Active Filters search bar or by viewing the Active Filter List.

      Filter gif

      User Display

      This is the central focus of the Migration Manager and displays all the users in the current migration.

      This section of the application provides you with a column-by-column breakdown of each individual user in a migration. Here you are also able to duplicate and edit source/destination paths of a user; as-well-as view the logs of any scanned or completed transfers.

      Migration Manager Users Mover

      User Actions & Finalization

      This area of the screen contains the User Actions dropdown menu, the Scan User and Start Migrating Users buttons.

      Migration Manager Finalization Mover

      User Actions opens a new dropdown menu that allows you to interact with a selected transfer.

      Migration Manager User Actions Mover

      Scan # Users will perform a scan of the selected users; this will help identify any problematic files, folders or connectors.

      Start # Migrating Users will open a side-tab that will allow you to finalize and begin the migration.

      Migration Manager User Actions Mover

      Running the Migration

      Scanning

      Scanning your source data is key to running a smooth and stress-free migration. For the full list of key data necessary for a smooth migration, refer to this checklist.

      Note: Scanned data will be marked as "Skipped" as scanning does not transfer data, it simply counts the data that we would normally transfer from the source.

      Note: Once a transfer is scanned the source/destination are effectively "locked in", please be sure to double-check that they are correct and not left blank.

      Running the Scan

      You now have a list of users appearing in the migration, complete with destination set up.

      Start the scanning source data process by selecting all user(s). (This is done by selecting the checkbox located at the top of navigation bar).

      Once all users are selected, click Scan X Users

      scan users

      Once the scan has successfully completed the users will appear green. The scan time will vary depending on the data amount in the source.

      Once users appear green, yellow, or red, click on Migration Actions on the top right hand side of your screen and select Scan Report

      Note: If your scan encounters an error or crashes the application will automatically rerun the scan up to three times to attempt to resolve the issue.Scan report

      The Scan Report is covered in-depth in the Reports section under the Scan Report section of the guide.

      Migrating Users

      We recommend starting slow. Test one user, then three to five. If it looks good, and you see data being downloaded and uploaded, start queuing everyone and stage the rest of your users.

      1. Select a user(s) by checking their row's respective checkbox.
      2. Click Start Migrating X Users
      3. Review your migration summary. This tells you which user is being copied, where they are transferring from and where to; as-well-as when the transfer will begin.
      4. Review and agree to our terms and conditions, then click Continue. Your users will immediately be queued for migration.
      Migration summaryNote: If your transfer encounters an error or crashes the application will automatically rerun the transfer up to three times to attempt to resolve the issue.

      Cancelling Users

      To cancel a currently running transfer:

      1. Find the transfer(s) you wish to cancel and select them. A running transfer will be blue and have a status of Running or Queued.
      2. Click the User Actions dropdown for multiple users, or right-click on a single user.
      3. Click Cancel X Transfers.

      This will stop the transfer as soon as possible (usually within a few seconds).

      Rerunning Users

      The best way to resolve any issues with a transfer is to rerun it. This will check over all the files in your destination, compare them to the source, and then transfer over the new or modified files.

      All transfers take advantage of our incremental feature and will only transfer new or modified data differences between Amazon WorkDocs and Office 365.

      As long as a transfer is not running, you may re-queue a user to restart a transfer.

      To rerun or restart your transfer, complete the following steps:

      • Select the or user(s) you would like to rerun.
      • Click Start Migrating X Users at the top right to run the users again.

      Transfer Status Messages

      Here is some extra info on each transfer status message from the Migration Manager:

      Status Message Definition
      Running pre-checks Our servers checking a few things and sending your transfer to the queue. Almost there!
      Queued to start, please be patient Your transfer will run as soon as possible. You may close your browser, and you will receive an email on completion. There is no limit to queued users.
      Success. No files copied We have skipped all of your files without error and have detected no new or modified files.
      Success. Some unsupported files not transferred We have skipped all of your files without error and have detected no new or modified files. Files unsupported by the source or destination were skipped over.
      Some upload errors, please retry We were able to download everything from the source, or skip files that already existed in the destination, but some files didn't make it into the destination.
      No files copied. Some upload errors, please retry We were able to download everything from the source, or skip files that already existed in the destination, but no files made it into the destination.
      Some download errors, please retry We weren't able to download everything from the source, but some files made it into the destination successfully.
      No files copied. Some download errors, please retry We weren't able to download anything from the source!
      Some download and upload errors, please retry There were errors with both downloading and uploading files, although some incremental files may have been skipped successfully.
      General failure, please retry We don't have a particular reason why your transfer failed - maybe we were having trouble connecting to your source or destination properly, for example.
      Connector auth failed One of your connectors isn't authorized correctly.
      Crashed, please retry We don't have a particular reason why your transfer failed, but generally this is due to server issues on our side or with the source or destination connectors. Please contact us if you encounter a crash.

      Post-Migration Troubleshooting

      General Troubleshooting

      The best steps to follow if your migration is having issues:

      1. Rerun users. Select one or more users and click Start Migrating on the top right of the Migration Manager to rerun them.
      2. View your most recent transfer log by clicking on the user row you wish to view. This will open the Transfer log sidebar. From here click the View Log button on the most recent transfer.
      3. Logs Side Bar

        Alternately you may select multiple users and from the User Actions dropdown menu you may download their most recent collective logs in a zip file that provides them in both HTML and CSV formats.

      4. Check if your failed/unsupported files are too large to go in to Office 365.
      5. Ensure you have enough storage space in Office 365 to accommodate the data you're moving in.
      6. Think files are missing? Check out our list of Unsupported Files per Connector.

      Incremental Feature

      Our incrementals are delta operations which compare files in your Amazon WorkDocs to files in Office 365. Using this comparison, we copy anything that is new or has changed. This enables us to keep Office 365 data up to date when the very final cutover of users occurs. These incremental passes are an important part of our process.

      Technical clarification: We compare what you have in Amazon WorkDocs to what is in Office 365 and we only transfer anything that doesn't already exist, or has a newer timestamp.

      “Lost Files”

      During a transition where sharing paradigms change, there will be many users who claim “My files are lost!”

      This is common if they are not clearly communicated with about how the sharing structure from Amazon WorkDocs will change when they log in to Office 365. This can be mitigated with a clear communication strategy.

      Waiting for Microsoft

      Once all your files have been uploaded to Microsoft the status of the transfer will change from "Running" to "Waiting for Microsoft". We must wait for Microsoft to complete their processing.

      It is normal for this process to take a few hours and will ultimately depend on how much data there is.

      Document Parser Error

      Large HTML or XML documents (256MB+) will fail to be transferred if the Document Parser is enabled for the destination site during the migration.

      The following error will appear:

      File too large for Microsoft Doc Parser. Please contact Microsoft support and request the Doc Parser be disabled for this site.

      If this error message appears, you will need to contact Microsoft support directly to disable the Document Parser on the target site for the duration of the migration.

      If you require assistance with your communication strategy, please ask us for help!


      Transfer Logs

      Viewing Your Logs

      Viewing your logs is an excellent way to troubleshoot transfer issues. They tell you each action we performed on each file and folder. If we run into any problems, you will receive an error message next to the file with a description on what happened.

      During a migration, sometimes a file will fail to download or upload. All failures are fully logged so you may address them.

      Note: we will attempt to copy a file 3 times before considering it a failure. We only log a failure if we are unable to properly transfer it 3 times.

      You can view a user's transfer logs by doing one of the following:

      1. Click on the user row, this will open the Transfer log sidebar. From here click the View Log button on the any previous transfer log for the selected user. Logs Side Bar

        Note: Clicking View Log will open a Transfer log in your web browser with built in sorting and filter features.

      2. Select multiple users and click Download Logs (zip file) from the User Actions dropdown menu or the Actions menu in the side tab. As the label implies, multiple log files are zipped together for download. Multi Log download

        Note: The zipped file will provide logs in both CSV and HTML formats for only the most recent transfer of each user.

      View an example CSV log or in your browser here:

      example_user_log.html

      Interpreting a Log File

      • Status: Whether an action was a success or a failure.
      • Size: File size in bytes, or that it's a folder being created/operated on.
      • Name: File, folder, or action being acted upon.
      • Additional Info: More information about the particular action performed. You can find out more about those below.
      Message Definition
      Failed to download file successfully This is an issue with the Source Connector.
      Failed to upload file successfully This is an issue with the Destination Connector.
      Unknown error of type 400 This is a "bad request" error - it could be a problem with the Source (File Download) or Destination (File Upload). Typically, this means that something has changed client-side or server-side and could be resolved by the next time you run the transfer.
      Unknown error of type 404 This is a "server not found" error. Typically, this means that the Source (File Download) or Destination (File Upload) server is down or experiencing a temporary outage.
      Auth failure: attempt to renew authentication successful Authorization is failing either on the Source (File Download) or Destination (File Upload) Connector.
      Backoff used: # Usually seen after an action listed as 'throttle' - this means we've made too many requests of that Connector, and must wait before trying whatever action we were trying to complete again.
      Folder Already Exists We went to create the folder, but we've already created it in a prior transfer, or it already exists in the destination.
      Skipping because of incremental Not an error by definition; it's just our incremental process at work.
      Scanned Not an error by definition; it's just our scanner counting your data.

      Troubleshooting Errors

      Message Definition
      Error: "The Office 365 connector has not been authorized in the Azure Tenant yet." Authorize the connector by granting admin consent in the Azure Tenant for the "Office 365 Mover" App.
      Error: "The Office 365 connector has not been authorized in the Azure Tenant yet." Authorize the connector by granting admin consent in the Azure Tenant for the "Office 365 Mover" App.
      Error: "Authorization failure" shown on the connector. Confirm that the connector is fully authorize or Reauthorize the connector.
      Error: Migration failing while using a .csv file as source/destination reference Confirm that the User Transfer Row has the correct syntax for both source and destination paths
      Error: "Please retry" during migration. Review log and confirm source/destination paths for user; check syntax if user transfer row was uploaded via .csv
      Error: "Cannot claim this folder as it is claimed by owner" in migration logs. User does not have explicit ownership of this folder and it is simply shared to them.
      Error: Migration crashes Review log data and determine the issue. Reauthorize the connector and rerun the migration.
      Error: Transferred files show SYSTEM as "owner" and "last modified by" Ownership is dependent on, and set by, the connector data is being transferred from. Consult the guides file authorship section for your specific connector.
      Error: Can't set permissions Confirm the syntax of the user permissions being set, check that the users exist in source/destination and that the User Row being transferred has explicit ownership over the data and it is not simply shared to them.
      Error: "Refreshed OAuth Authorization Token: 404 Not Found" - "itemNotFound: The resource could not be found" Reauthorize (or delete and recreate) the connector and ensure that you have administrative privileges when authorizing.
      Error: "A file with the name x already exists. It was last modified by  y ." The app itself encountered an error while attempting to access the file. Rerunning the migration should clear this error.
      Message: "Waiting on Microsoft batch Processing", Migration freezes  failed files not shown in logs The data has not finished propagating yet for the logs, contact support if the migration doesn’t complete in 24 hours.
      Error: Migration quickly says "complete", but the data didn’t transfer. Ensure that the user has ownership of data in the source path and all data is not simply shared to them.
      Error: "Unsuccessful HTTP response: Unable to update users. Required heading not found: id" The ID column of each user needs to be the first column of the .csv in order to change already existing User Transfer Rows.
      Error: "Transfer failed because the target folder for one of your connectors could not be set." Ensure that there is no syntax errors for the destination path and that the folder does exist in the destination directory/account
      Error: Stuck on “Loading Application” during account verification in IE Browser. Use Chrome, Edge or Firefox browsers
      General: How to stop and restart a migration after recovering from an error... Check the box on the left of an User Transfer Row and then click "Start Migrating x User" this will create an incremental transfer to pick up where you left off.

      Reports

      Dashboard Overview

      The dashboard statistics given at the top of the Migration Manager provide a visual summary of your overall migration. This includes the number of users in the current selected migration, the number of files scanned or transferred, and the amount of data scanned or transferred; as-well-as any issues, errors or failures that may have occurred:

      Visual summary

      Transfers

      The Transfers section of the Migration Manager dashboard gives a brief run-down of all user transfers and scans.

      • New: The number of individual users that have yet to be scanned or transferred.
      • Running: The number of users that are currently running either a scan or a transfer.
      • Complete: The number of users that have successfully completed scans or transfers.
      • Issues: The number of users that encountered errors during a scan or a transfer.
      • Failures: The number of users that failed to scan or transfer.

      Note: The total Transfers number is from all users regardless of status.

      Visual summary

      Files

      The Files section of the Migration Manager dashboard provides a total of all files scanned and transferred across all users in a migration.

      • Complete: The number of files that have successfully scanned or transferred.
      • Issues: The total number of files that have encountered issues and failed to scan or transfer

      Note: The total number of Files is from both scanned and transferred users; be aware that scanned files are marked as "Skipped" as they have yet to be transferred.

      Visual summary

      Data

      The Data section of the Migration Manager dashboard shows the total of all data scanned and transferred across all users in a migration.

      • Complete: The total amount of data that has been successfully scanned and transferred.
      • Issues: The total amount of data that encountered issues and has failed to scan or transfer.

      Note: The total amount of Data is from both scanned and transferred users; be aware that scanned data is marked as "Skipped" as it has yet to be transferred.

      Visual summary

      Active Filter List

      Here you will find the list of all current Filters that be applied to the "Active Filter" search bar:

      Note: Applying the filters will change the statistic shown in the Migration Dashboard.
      Filter Label Label Effect
      Status Filters by status [ie. Failed, Success, User Does Not Exist etc. etc.]
      Files Filters based on files transferred, failed and skipped.
      Data Filters based on data that has transferred, failed or skipped.
      Success Displays all successful Data and Files transferred.
      Failed Displays all Data and Files that have failed to transfer.
      Skipped Displays all data and files that were skipped.
      Schedule Displays all users with scheduled transfers [ie. Hourly, Daily, Weekly, Monthly]
      Path Filters for specific source or destination path [eg. path:username]
      Destination Filters for specific destination path [eg. path:@domain.com]
      Source Filters for specific source path [eg. path:foldername]
      Destination path Functions the same as "Destination".
      Source path Functions the same as "Source".
      Tags Lists transfers with previously implemented custom tags.
      Notes Filters by keywords in previously implements custom notes.
      Code Filters for specific status codes.
      Destination name Displays transfers with a specific destination name.
      Source name Displays transfers with a specific source name.

      Scan Report

      For more information on the scanning process see the Scanning section of the guide.

      Once the scan report is downloaded and opened, the key things you should look for are:

      1. Users with a failed status. It is recommended to rerun the scan for these user(s).
      2. Users with 1 file or less. Note: Sharing permissions will still be transferred.
      3. Users with the most data. You can use this information to decide on a data distribution strategy that suits your needs. More info on data distribution can be found
      4. here.
      Scan report

      Migration Report

      The Migration Report provides an in-depth overview of your entire migration, including (but not limited to) speed and time statistics, totals for files and data transferred, and info relating to the latest run.

      To download this as a CSV, select the gear icon at the top right of the Migration Manager and click on Migration Report.

      This CSV report will give you the following information for each user pairing:

      Header/Statistic Definition
      Schedule ID Our internal reference unique to the user pairing created.
      Source The source directory path.
      Destination The destination directory path.
      Tags If you have used our tags feature, you'll see them here. You can use tags to differentiate operational departments, to flag specific users, etc.
      Notes If you have added notes to user pairings in the Migration Manager, they'll appear here - ie. "Remind me to check the logs on this user" or "Weird folder problem - ask support"
      First Run Start When the first transfer on this user pairing began.
      Files Transferred Total files transferred.
      MB Transferred Total data (MB) transferred.
      Times run Total number of times this user pairing has been run.
      Total Duration The total duration of each time this user pairing has been run.
      Average File Velocity (files/hour) Files transferred divided by the total duration.
      Average Data Velocity (MB/hour) Data (MB) transferred divided by the total duration.
      Last Status The last status of the user pairing - this is also reflected by the colour of each row in the Migration Manager. Examples include "Success", "Some Problems", "Failure".
      Last Status Code Internal reference number referring to the last status of the user pairing.
      Last Skipped The number of skipped files in the last run.
      Last Files The number of files transferred in the last run.
      Last MB The volume of data (MB) transferred in the last run.
      Last MB Skipped The volume of data (MB) skipped over in the last run.
      Last Failed Files The number of files that failed to transfer in the last run.
      Last Folders Listed The number of folders that we opened/created in the last run.
      Last Folders Failed The number of folders that we failed to open/create in the last run.
      Last Run Start When the latest transfer on this user pairing began.
      Last Run End When the latest transfer on this user pairing finished.
      Last Run Duration How long the latest transfer on this user pairing took to complete.
      Last File Velocity (files/hour) Files transferred divided by the total duration for the last run.
      Last Data Velocity (MB/hour) Data (MB) transferred divided by the total duration for the last run.

      Download an example CSV here: example_migration_report.csv


      Migration Table Report

      The Migration Table Report generates an overview of your entire migration based on the custom designated columns you have set.

      To edit report columns click Migration Actions. in the Migration Manager and select Customize Columns. Here you can set and reorganize which Columns you wish to display when you download the CSV report.

      To download this as a CSV, select the gear icon at the top right of the Migration Manager and click on Migration Table Report.

      Migration Table Image

      Download an example CSV here: example_migration_table_report.csv

      Migration Error Report

      The Migration Error Report generates a simplified Migration Report that focuses on any problematic files, folders, permission errors or general errors.

      To download this as a CSV, select the gear icon at the top right of the Migration Manager and click on Migration Error Report.

      Migration Error Image

      Download an example CSV here: example_migration_error_report.csv


      Post-Migration Tips

      We are stewards of your data. Our approach in all things is to see you successfully cross the finish line. We provide full service support and will be ready to solve any problem and communicate on any issue.

      Communication

      • Follow-up with employees after your migration to ensure they know where to access their data.
      • Provide a link to set up their new Office 365 accounts. Be ready to answer any questions or concerns, as it is common for users to complain about a new system.

      Example Email

      Subject: *ATTENTION: Login to Office 365*

      Message: Over the weekend, we migrated our team from Amazon WorkDocs to Office 365.

      All files and folders were transferred without any issues. Please follow this link to set up your new Office 365 account.

      Your username will remain the same, however you will need to create a new password.

      From now on, please log into your Office 365 account rather than your old Amazon WorkDocs account.

      Please let me know if you have any questions or concerns.