How to Migrate from On-premises Desktop File Shares and Servers to Egnyte

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 File Servers to Egnyte, 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 File Servers to Egnyte.

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

File Processing Summary

When we transfer a file, a temporary copy is downloaded from File Servers to a temporary server and then uploaded to Egnyte. 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?

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.

This also applies for separate internal or external drives migrating to Egnyte Shared & Private Folders.

For example:

  • /C:\/Archive => /Shared/Archive
  • /D:\/Sales => /Shared/Sales
  • /D:\/User01 => /Private/User01
  • /C:\/User02 => /Private/User02

This qualifies as three separate "User Licenses", even though they are all going to the same destination. Egnyte's /Shared folder is considered one source, while every /Private folder is considered a separate source.

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 File Servers. Anyone that strictly engages as a collaborator in File Servers (i.e., they only share other users' content) will not have any data copied and therefore will not incur a fee.

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 File Servers and Egnyte 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 File Servers to Egnyte, you need to ensure all your users are active and accessible.

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 to Egnyte

Message: A few months ago, management decided we will transition to Egnyte. In Egnyte, 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 to Egnyte as our cloud storage provider.

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

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

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. Animation describing 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 File Servers, we will treat it as a brand new object. This can lead to duplicate files being migrated to Egnyte, 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.

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 File Servers to Egnyte 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.

Agent FAQ

Windows

The Windows Agent has two installers, one for the user-context and one for the service-context. The Windows Agent requires Microsoft .NET Framework 4.6.2 or greater.

The differences between Windows installers are as follows:

User-context installer

  • Click to download
  • Installs and is run as the currently logged in Windows user.
  • Automatically updates.
  • Has access to local drives.
  • Has access to mapped network drives.
  • Is not available if the user logs out of Windows, or your remote desktop session expires.

Service-context installer

  • Click to download
  • Installs and is run as a Windows service.
  • Must be manually updated.
  • Has access only to local drives.
  • Is always available, even if the current user logs out, or your remote desktop session expires.

Command Line Agents

The following Agents operate using command line interface versus a user interface.

macOS

  • Click to download
  • Navigate to the download location and Unzip the Mover Agent
  • Via the terminal, browse to the now unzipped moveragent folder and run ./agent
  • Copy the key from the line that reads [1] INFO ocess.BifrostService: Bifrost service initialized with connector key: <key>
  • Open our app and paste key into agent authorization box
Note: The minimum system requirements are macOS 10.12

Linux

  • Click to download
  • Navigate to the download location and Unzip the Agent.
  • Via the terminal, browse to the now unzipped moveragent folder and run ./agent
  • Copy the key from the line that reads [1] INFO ocess.BifrostService: Bifrost service initialized with connector key: <key>
  • Open our app in your browser and paste key into agent authorization box.

Windows Command Line installer (beta)

  • Click to download
  • Installs and is run as a Command Line executable.
  • Must be manually updated.
  • Built from the same code base as the Linux and macOS agents.

How does the Agent view users?

The Agent works with files and folders. All users who are separated into their own folders can easily be mapped to their new location in Egnyte.

A good example would be a large listing of home drives. Each home drive for a user could be transferred to their respective new user in Egnyte.

Windows Egnyte
  • F:\
    • Users
      • Eric
        • file.pdf
      • Jon
      • Amanda
    • Marketing Share
    • Sales Share
  • Private
    • Eric
      • file.pdf
    • Jon
    • Amanda
  • Shared
    • Marketing Share
    • Sales Share

Troubleshooting the Agent

Checking the Agent Version

Click the Help tab on the menu bar to check which version of the Server Client you have installed.

Agent Version

If you are using the Mac or Linux version of our Agent, follow these instructions to find out the version you are using: Show Agent Version.

Accessing Server Agent Log

To access the Agent Log navigate to the folder directory that you have installed the desktop agent on. Here you will find a .log file that you will be able to look over and send to our support team if an error should occur.

Note: The agent .log file default location is Windows\System(32/64)\config\systemprofile\AppData\Local\MoverAgent Log

Commands for Agent (Mac and Linux only)

Our Agent supports the following commands:

Start the Agent

To start the Agent use ./agent start

$ ./agent start
Mover Agent Starting
Mover Agent Key: 0000000000000000000000000000000
Ctrl-C To Stop

Start the Agent in the background

To start the Agent in the background use ./agent start &

$ ./agent start &[1] 8667
$ Mover Agent Starting
Mover Agent Key: 00000000000000000000000000000000
Ctrl-C To Stop

Stop the Agent

If the Agent is running in the foreground of the terminal, pressing Ctrl-C will stop the Agent

^CMover Agent Stopping

If the Agent is running the background or in another terminal session use ./agent Stop

$ ./agent stop
Connecting to Mover Agent
Sending stop command
Mover Agent Stopping
Mover Agent stopped
[1]+ Done ./agent start

Show Agent help

To get a list of commands and options use ./agent -h

$ ./agent -h
Mover Agent 1.0.6968.0
Usage: agent [options] [command]

Options:
-? | -h | --help Show help information
-v | --version Show version information

Commands:

  • connect| Connect to a running instance of the Agent and issue a connect command
  • disconnect| Connect to a running instance of the Agent and issue a disconnect command
  • monitor| Connect to a running instance of the Agent and monitor agent activity
  • start| Start the Agent
  • status| Connect to a running instance of the Agent and retrieve the current status
  • stop| Stop the Agent

Use "agent [command] --help" for more information about a command.

Show Agent Version

To show the Agent version use ./agent -v

$ ./agent -v
Mover Agent
1.0.6968.0 (Unix 18.6.0.0)

Check Agent status

To check the status of the Agent use ./agent status

$ ./agent status
Connecting to Mover Agent
Mover Agent Key: 00000000000000000000000000000000
Mover Agent Status: online

Disconnect the Agent

To disconnect the Agent use ./agent disconnect

$ ./agent disconnect
Connecting to Mover Agent
Sending disconnect command
Mover Agent disconnected.

$ ./agent status
Connecting to Mover Agent
Mover Agent Key: 00000000000000000000000000000000
Mover Agent Status: offline

Connect the Agent

To connect the Agent use ./agent connect

$ ./agent connect
Connecting to Mover Agent
Sending connect command
Mover Agent connected.

$ ./agent status
Connecting to Mover Agent
Mover Agent Key: 00000000000000000000000000000000
Mover Agent Status: online

Monitor Agent Activity

To monitor the Agent activity use ./agent Monitor. To stop monitoring Agent activity use Ctrl-C

$ ./agent monitor
Connecting to Mover Agent
Mover Agent Key: 00000000000000000000000000000000
Connected to bifrost.mover.io on ports 8081 and 4002.
Ready to transfer!Browse: /
Browse: /Users
Browse: /Users/mover
Browse: /Users/mover/AgentTestData
Browse: /Users/mover/AgentTestData/TestDocuments
Upload: /Users/mover/AgentTestData/TestDocuments/TestTextDocument.txt
Upload: /Users/mover/AgentTestData/TestDocuments/file.txt
Upload: /Users/mover/AgentTestData/TestDocuments/picture.jpg
^C

Egnyte FAQ

What is different about Egnyte?

Unlike other cloud storage providers, Egnyte has a Shared folder and a Private folder. When migrating into Egnyte, the app defaults to the Private folders when auto completing the user to user migration setup.

What happens to sharing links and permissions?

While we can transfer sharing permissions over to Egnyte, we don’t allow it by default in the app - it’s a little more complicated.

The app transfers data into Egnyte's Shared folder so we can transfer permissions from the source to Egnyte. If data is copied into users' Private folders, no sharing links or permissions will go through. If you attach a permission map, users who previously had access to files or folders in the source will maintain access to them in Egnyte. Those who did not previously have access in the source will not gain access to the data once it's in Egnyte. As the administrator, you will be the only user who can see shared data.

However, if you'd like to transfer data into each user's private folder, you can edit every schedule individually (change Egnyte's root from "Shared" to "Private") or upload a .csv with users' source and destination paths.

How will my paths look when Egnyte is my destination?

During the migration setup (described later in this guide), you can edit the path(s) to specify where in Egnyte you would like the data to go. From the root level of Egnyte, you can go into /Private which lists the individual users and their data, or /Shared which is the main shared data repository.

Most cloud storage providers will start the listing with a user such as /example@user.com/marketing data. Egnyte does not do this, so you would be looking at a path such as /Shared/marketing data if it's a Shared folder or /Private/example/marketing data if it's a Private folder.

Unsupported files and characters

The app automatically processes file and folder names to ensure they are accepted by Egnyte.

  • Leading or trailing whitespace is removed.
  • Trailing periods (.) are removed.
  • Files with a size of 0 bytes (zero-byte files) are not migrated.
  • The following characters in file or folder names are removed:
    \, /, ", :, <, >, |, *, ?, +
  • Non-printable controls characters are removed. Read more about Control Characters in this Wikipedia article.
  • File or folder names beginning with an open curly brace ({) and ending with a close curly brace (}) are not migrated.
  • Files with the following names are not migrated:
    • .ds_store
    • .metadata_never_index
    • .thumbs_db
    • powerpoint temp
    • desktop.ini
    • icon\r
  • Folders with the following names are not migrated:
    • .data
    • .tmp
  • Folders that start with .spotlight- are not migrated.
  • Files and folders that start with the following are not migrated:
    • ._
    • .~
    • word work file
    • _egn_.
    • .smbdelete
  • Files and folders that end with the following are not migrated:
    • .
    • ~
    • ._attribs_
    • ._rights_
    • ._egn_
    • _egnmeta
    • .tmp
    • -spotlight
    • .dwl
    • .dwl1
    • .dwl2
    • .ac$
    • .sv$
  • Files and folders that start with a tilde (~) and end with the following are not migrated:
    • .idlk
    • .xlsx
    • .xlsx (deleted)
    • .pptx
    • .pptx (deleted)
  • Files and folders that start with (~$) and end with the following are not migrated:
    • .doc
    • .docx
    • .docx (deleted)
    • .ppt
    • .pptx
    • .pptx (deleted)
    • .xlsm
    • .xlsm (deleted)
    • .sldlfp
    • .slddrw
  • Additional files not migrated to Egnyte:
    • AutoCAD temp files starting with atmp and ending with four numbers, eg. atmp3829
    • SAS temp files ending in .sas.b follwed by two numbers, eg. myFile.sas.b73
    • PDF temp files starting with aa followed by a single letter followed by five numbers, eg. aau38221

Timestamps

It is important to note the impacts on timestamps when migrating from File Servers into Egnyte. The 'last modified' date will be preserved, but the 'created' date will change to the date the file is first copied into Egnyte by us.

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.

File Authorship

It should be noted that when migrating from File Servers into Egnyte the "Last Updated" will be changed to the administrator.


Setting Up the Migration

Authorizing the Desktop and Server Agent

In order to enable swift and painless copying of data from on-premise desktop and server hard drives, we provide a very tiny agent that any Windows operating system can install.

Compatibility

  • Windows XP is not supported.
  • All other versions of Windows require the .NET Framework 4.6 in order for the Agent to function.
    • Download and manually install .NET Framework 4.6 from this link.

Security

The Agent may only initiate outbound communication with our own servers. All communication is via encrypted TLS and no service other than ours is allowed to work with the agent.

Windows Installation

For Mac and Linux the Agent folder will appear in your Downloads and is run through command line operations.

  1. Download the Agent .exe and click Run.
  2. Downloading the AgentRunning the Agent
  3. Agree to the Terms of service and select an install destination.
  4. Image of Open File - Security WarningMover desktop folder
  5. Navigate to the installed destination and click the Mover icon to run the desktop Agent.
  6. Open Agent Desktop
  7. Copy the Agent Key by clicking on File and Copy Key in the drop-down menu
  8. Copy Agent Key

Authorizing the Agent in our App.

  1. In the Transfer Wizard click Authorize New Connector.
  2. Auth New Connector
  3. Find Agent (Desktop or Server) in the Connector list.
  4. Click Authorize.
  5. Agent Connector List
  6. A new window will open and you will be asked to name your connector (this is optional).
  7. Enter your required Key that you copied from the installed agent (found via the File > Copy Key action in the Agent).
  8. Lastly click Authorize.
  9. Agent Name Connector

Additional Screenshots

Image of additional screenshots

Troubleshooting an Agent Connector

What operating systems are supported by the Mover Agent?

The Mover Agent supports many operating systems:

  • Windows Vista
  • Windows 7
  • Windows 8
  • Windows 8.1
  • Windows 10

Removing the Mover Agent

It's very easy to stop using the Mover Agent.

You may simply click Disconnect from Mover in order to stop the Mover Agent from connecting to Mover's servers.

To completely uninstall the Mover Agent please use the Windows program manager to uninstall.


Authorizing Egnyte (Multi-User)

Authorizing Egnyte as an administrator is straightforward. To authorize or add a Multi-User Egnyte account as a connector, follow these simple steps:

IMPORTANT! You absolutely MUST be an Administrator. A non-administrator will not work.

  1. In the Transfer Wizard click Authorize New Connector.
  2. Auth New Connector
  3. Find Egnyte in the Connector list.
  4. Click Authorize.
  5. Egnyte Connector List
  6. A new window (tab) will open. Name your Connector (Optional).
  7. Provide the Egnyte domain - i.e. if your Egnyte domain is companyname.egnyte.com, then just put in "companyname".
  8. Egnyte Name Connector
  9. Click Authorize.
  10. If you are not already logged in, you can use either your Egnyte credentials or a SSO account.
  11. Egnyte login access
  12. Click Allow to grant the App access to your Egnyte Account.
  13. Egnyte Grant Mover

Egnyte Permission Requirements

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

Permission Details
Create and manage bookmarks Allow our app to access and migrate bookmark data.
View and manage folder permissions Allow our app to access and create folder permission.
View and manage groups Allow our app to view all groups under in the available Egnyte Directory.
View and manage users Allow our application to view, edit and manage users under the available Egnyte Directory.
Generate audit reports Allow our app to generate and view reports available in the Egnyte Report Center.
Create and manage links Allow our app to create and manage internal links.
Read and write all files and folders Allow our application to view, edit, copy and paste all data from within the Egnyte available Directories.

Connecting Your Source Agent for Windows

If you are not already connected after you have authorized your source, click Agent for Windows and load the connector. An icon will appear and show you the folders you are migrating.

Select File Servers Source

Connecting Your Destination Egnyte Account

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

Select Egnyte Destination

Creating a New Migration

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

Image of 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.
Image of how Add Users Button
  • Or, click Migration Actions, then Add to Migration.
Image of 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.

Image of 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.

Paths 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
D:/Users/user1,user1@example.com,"Pilot, Home Folder"
E:/Share/Marketing,Marketing Team Folder/subdir,"Pilot, Department"

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:

Example_CSV_Agent_to_Egnyte.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 File Servers source match the users in the Egnyte 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 File Servers source path.
  4. Double-click to select your parent source path and click Save to complete your edit.
  5. Image of 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 Egnyte destination path.
  4. Double-click to select your parent destination path and click Save to complete your edit.
  5. Image of 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. Image of 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.

Image of 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.

Image of 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.

Image of 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.

Image of delete user prompt


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 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.image of 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.
Image of 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 File Servers and Egnyte.

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. Image of 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 Egnyte.
  5. Ensure you have enough storage space in Egnyte 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 File Servers to files in Egnyte. Using this comparison, we copy anything that is new or has changed. This enables us to keep Egnyte 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 File Servers to what is in Egnyte 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 will change when they log in to Egnyte. 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. Image of 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. Image of 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.

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:

image of 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.

image of 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.

image of 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.

image of 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.
image of 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 Egnyte 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 Egnyte*

Message: Over the weekend, we migrated our team to Egnyte.

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

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

From now on, please log into your Egnyte account.

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