Part 2/3 of our ebook How to Migrate to EFSS

Data transmission options:

  • User-driven: Users self migrate using sync clients and other tools. This solution is idle for small organizations, avoids user-customization and provides full control of process and time. However, for medium to large companies with complicated file servers this often ends in an unintentional hybrid state.
  • FTP/SFTP: This protocol transfers files over a network. While FTP/SFTP is inexpensive and can transfer at high-speeds, it doesn’t address security concerns, achieve permission mapping, provide detailed reports or manage the bandwidth used for data transmission. In addition, some EFSS platforms don’t support FTP/SFTP and when supported, features are limited.
  • Shipping Disks: Frequently IT experts will simply load data onto hard drives and send data to EFSS platforms. This avoids transmission errors and is useful for static data but, permission mapping and data organization can be expensive.
  • Desktop Synchronization Clients: Clients keep files synchronized across devices. While they easily upload small data sets and help users keep data synced with other devices, they are unable to sync large data due to client’s capacity, access data from a connected server or transfer data from one cloud service to another.