Purpose

This article is to outline what needs to be considered and how to migrate from SAMBA to Google Team Drive

Process

Outline what should be allowed within the Team Drive

Take a moment to review the Team Drive Settings for how you wish to allow Members to be able to do things within the Team Drive.

By Default, Team Drive will have the following settings:

Members (Contributor or better) can share anything within the Team Drive to anyone outside of UCSB
Members (Contributor or better) can share anything within the Team Drive who are not Members of the Team Share
Commenters and Viewers can Download, Copy or Print anything within the Team Share

Outline your permissions

Take a moment to look at the Team Drive Permissions and who will need access to the various data that is in your SAMBA share.

If there are some folders within your SAMBA share that require specific or special permissions, you should consider that you will need to make a separate Team Drive for that specific folder based on those permissions.

It is recommended to consider having one Departmental Functional Account be given Manager permissions along with the person who will manage the Team Drive as a 'just in case' situation, such as emergencies or managers leaving and possibly forgetting to pass control over to the next person.

Note with regard to Departmental Functional Account

We recommend that for the Functional Account, it should be named <Department> Fileshare.

(IE: If the Department was CSI, it should be named CSI Fileshare)

This user account should be in the Department's Admin Records or available for the Connect Departmental Admin to reset the password in case there is a need to manage other Departmental Team Shares.

Outline Team Drive Structure

Due to Team Drive not supporting Folder copying, you should outline the folder structure that you will need to create once the Team Drive is first created to mimic what you have in SAMBA, keeping in mind that you are only covering the folders that should be accessed with the same permissions through out.

If you have folders that should be accessed a different way, as mentioned above, you will have to consider making that a separate Team Drive and not include that folder structure within the Team Drive you are working on.

Also, keep in mind that the Team Drive does have limitations, as noted here, Google Team Drive Limitations.

Create Team Drive

Follow the process to create the Team Drive here - Creating a Team Drive

Keep in mind to use the Settings and Permissions you outlined earlier when you create the Team Drive.

We also recommend, for ease of Identification, to name the Team Drive <Department> <Function>.

IE: If the department was CSI and the function of the Team Drive as General, calling it CSI General would help, especially if you are a cross department user, easier to identify which Department the Team Drive belongs to.

Create the Folder Structure

Taking the outline of the Team Drive Structure, start creating Folders to mimic the structure you outlined earlier in Migrating from SAMBA to Google Team Drive.

Copy Files to Team Drive

Once the Folder Structure is done, you can copy your files from SAMBA into your Team Drive.

Only copy the Files, not the folders, into Team Drive.

Team Drive currently does not support copying folders.

Optional Transfer

ECI can work on transferring the SAMBA share information to Google Team Drive, however, the process can take up to a couple of weeks depending on the amount of data is in the SAMBA share.