DESCRIPTION: Egnyte is a cloud provider at www.egnyte.com. The Egnyte (Admin Account) adapter enables you to transfer multiple Egnyte source accounts to another account on a target.
SUPPORTED POPS: All cloud POPs. Google Cloud recommended.
EGNYTE DOMAIN: Enter the domain only. So if you log into your Egnyte account at companyname.egnyte.com, enter companyname in this field.
Egnyte Source and Target Node Configuration
Source Node Configuration
SOURCE ACCOUNT LIST Most migrations can select an admin account only. The admin owns all data in Egnyte, so it is unnecessary to select other accounts.
SOURCE FILE/DIRECTORY This field will only be displayed if a single account is selected from the Source Account List chooser.
USE LAST MODIFIED AS UPLOADER When this checkbox is checked, the last uploader of the file from the source will be listed as the file owner in Egnyte target.
Set Source Owner Select this option to list secondary owners of files and folders in the mapping spreadsheet. If this option is not selected, the oauth admin will be listed as the owner of all data.
Target Node Configuration
TARGET ACCOUNT NAME: The account that will receive all files from the source. Note that if you select a team member, it will nullify any directives from the spreadsheet for account mapping. If you are running account mapping, this field should be left blank.
TARGET FOLDER NAME: Enter the folder name into which you wish to transfer your files on the target (destination) server. Cloud FastPath will create a directory with this name and will place your transferred file into that directory.
Account Mapping Considerations
Egnyte granular sharing is supported, so you can apply permissions through the file tree without regard to restrictions imposed by waterfall permission strategies.
Egnyte to Account Based Providers
The following best practices will ensure a successful migration to account based providers such as Dropbox and Box:
Select the Set Source Owner checkbox on the Egnyte source node. Secondary folder owners (i.e., Power Users) will be designated as the source owners rather than the Egnyte Admin group. You can only select a single account from the source; select an Egnyte admin account.
When you map users, map all Egnyte admins to a single account on Dropbox in the Users tab. Then, use the Target Owner column of the Paths tab to redirect specific folders to other Dropbox accounts, using the Dropbox Target account names. For example, if you have two Egnyte admins, Joe and Caitlin, map both of these accounts to “Joe-Dropbox-Account-Email” on the Users tab. Then, if you have a folder ‘Caitlin’s Folder’ on the Paths tab and you want that data to go to Caitlin’s Dropbox account, enter “Caitlin-Dropbox-Account-Email” as the Target Owner for that folder. These steps eliminate ambiguity incurred by the fact that individual Admins cannot own folders and files on Egnyte – only the Admin Group that they all belong to can own folders and files.
NOTE: If the source and target account email are identical – for example, if you enter an account “email@example.com” as the Target Owner in the Paths tab – CFP will treat it first as a target account if it can find that email in the list of valid target accounts. CFP will only treat “firstname.lastname@example.org” as a source account that needs a user tab lookup if CFP cannot find that email as a target account.
Transferring Native Google Docs from Egnyte to Google Drive
CFP supports transferring native Google Docs stored on Egnyte sources to Google Drive targets. In the job configuration, go to Advanced Fields and check the box for “Import to Google Docs types” under Target Node Fields.
Account Based Providers to Egnyte
Migrating to /Shared in Egnyte
If you are migrating multiple accounts to the same location in the /Shared folder, those accounts will be namespaced (a folder will be created for each account migrated, labeled with the source username, and that account’s folders will be saved to the labeled folder on Egnyte) for two reasons:
- top level files from source accounts cannot be saved to the root of the /Shared folder. Adding a namespaced folder ensures that there will be a folder for those files to go into.
- namespacing eliminates the conflicts incurred by two duplicate folders in the same location. If Joe and Caitlin both have folders called ‘Documents’ in their Box accounts, for example, namespacing ensures that the contents of those two folders will remain separate.
If you do not want a namespaced model for your data, contact email@example.com for additional information.
Migrating to /Private in Egnyte
You’ll need a list of the folder names in the /Private sector of Egnyte. You can generate a list by doing this:
- Create a job with Egnyte as the target. From the Accounts and Files screen, select the Select Directory button on the target.
- Your private folders will list. Select the Export List button to download a list of all your /Private folder names.
- Use path based mapping in your job to move data to the private folders. When specifying a private folder in the Target Path column of the Paths tab in your mapping spreadsheet, use the full path (e.g., ‘/Private/joeb’). Data from account-based providers, such as Box, can use path based mapping by entering a source owner in the Source Owner column of the paths tab, and the account root (which will be “/” for Box and Dropbox, “/My Drive” for Google Drive) in the Source Path column. Do this for each source owner:
Source Owner Source Path Target Owner Target Path firstname.lastname@example.org / email@example.com /Private/alyssa firstname.lastname@example.org / email@example.com /Private/colin
There are a few nuances on whether to enter the source or target Egnyte account in the Target Owner column. CFP support would be happy to cover these with you if you have any questions.
- Contact firstname.lastname@example.org with any questions you have about mapping to /Private or /Shared environments in Egnyte.
Suppressing Emails in Egnyte
During a migration to Egnyte, Egnyte can generate a lot of emails when folders are created, updated, or shared. To suppress these emails, an admin user can go to the admin console > Configuration > User Types & Roles and set “receive folder notification emails” to “never” for all applicable users. Check on the box for “users can override this setting” so that individual users can choose to receive notifications if they wish.
Unsupported Characters and File Types When Migrating to Egnyte
Paths, Folder, and Files Names that are Too Long
Two of the most common reasons for file transfer errors during Egnyte migrations are ‘Name too long’ and ‘Path too long.’ Egnyte has a limit of 245 bytes per path component (e.g., a file or folder name) and 5000 bytes for the entire path (including the filename). Microsoft Office imposes a 215 character limit on Office files.
Giving your target path a short name can minimize the incidence of path length errors. If you are moving your data to a specific folder on Egnyte, keeping the folder name short will likewise minimize errors and the need to rename paths to a smaller length. Renaming or restructuring paths is not advised once the migration has started, as duplicate data sets may result.
Running a Simulation prior to the actual data transfer will identify paths, folder names and file names that are too long. You can then adjust the paths prior to running the actual migration. Path renaming done after the map is generated can result in mapping errors and other issues with your migration, so re-running the map after renaming is recommended. Typically, data that has paths too long is clustered into a few folders, and is reasonably easy to address.
You can get a rough idea of paths that are too long by running an Analysis at the very outset of the project and then running a (LEN) function in Excel for all the paths in the Analysis report. Any character count that is > ~250 characters or so is in the risk zone for path too long errors.
File and Folder Names
Egnyte does not support file and folder names which include any of the below conditions. Please note the list below is not meant to be exhaustive and you should confirm with Egnyte directly about which characters and file types are accepted.
\ / ” : < > | * ?
- end with period(s)
- begin or end with spaces
- have control characters
- have Unicode characters with 4 or more bytes
- match one of the following exactly: .ds_store, .metadata_never_index, .thumbs.db, powerpoint temp, desktop.ini, icon\r
- end with: ., ~, ._attribs_, ._rights_, ._egn_, _egnmeta, .tmp, -spotlight, .dwl, .dwl1, .dwl2, .ac$, .sv$, *.~vsdx
- start with: ~ and end with: .doc, .docx, .docx (deleted), .ppt, .pptx, .pptx (deleted), .xlsm, .xlsm (deleted), .sldlfp, .slddrw, .sldprt, .sldasm
- are AutoCAD temp files starting with atmp and ending with four numbers, e.g., atm3829.
- are SAS temp files ending in .sas.b followed by two numbers, e.g., myFile.sas.b73.
- are PDF temp files starting with aa followed by a single letter followed by five numbers, e.g. aau38221.
- end with .$$$, e.g., myFile.$$$, and are uploaded from the Desktop App. Cloud FastPath recommends that you not attempt to upload these files to Egnyte to avoid future issues with the Desktop App.
- folder names that match one of the following exactly: .data, .tmp or start with .spotlight-
NOTE: Characters such as spaces, slashes, ampersands and unicode characters will all be converted in URL encoding, and the resulting encoding for a single character may be several characters in length.
- Uploading active database files is NOT supported e.g. Exchange, Quickbooks, SQL, Oracle or MS Access.