#Customized Features for Microsoft Teams Chat Migration

Fly provides multiple customized features for Microsoft Teams Chat Migration. Refer to the following information to use the features.

#Migration to Google Chat Space

Refer to the following instructions to use the feature for Microsoft Teams Chat to Google Chat Space migrations:

• CreateNewSpaceIfSpaceIsDeleted – Define whether to create a Google Chat space based on the project mapping during the migration if the destination space has been deleted after migrating the source Teams Chat to the destination.

  By default, this feature is disabled. If the destination Google Chat space has been deleted, the migration job will fail.

  If you want Fly to create a Google Chat space during the migration, you can add the CreateNewSpaceIfSpaceIsDeleted=true string to the Customized features section.

  To disable this feature again, you can change the string value to false.

#Migration to Microsoft Teams Chat

Refer to the following instructions to use features for Microsoft Teams Chat to Microsoft Teams Chat migrations:

• CreateNewChatIfServiceAccountIsLeave – Define whether to add the destination service account back to destination chats in the next migration job if the service account is removed from the chats.

  By default, if the service account is removed from destination chats after the migration job and the destination connection has an app profile, Fly will automatically add the service account to those chats in the next migration job. If you do not want to add the service account back to those chats, and want to create new chats in the next migration job, you can add the CreateNewChatIfServiceAccountIsLeave=true string to the Customized features section.

• DateTimeFormat – Configure this feature string if you want to define the format for the sent time of chat messages migrated to the destination.

  The default format of the sent time is yyyy-MM-dd h:mm:ss tt, and the sent time of chat messages will be displayed as 2020/11/25 13:50:08 in the destination. (tt indicates that AM/PM also needs to be displayed for sent time.)

  You can customize the format of the sent time by adding the DateTimeFormat=" " string to the Customized features section, and entering your desired time format as the string value. For example, enter DateTimeFormat=MM/dd/yyyy.

  Refer to the table below for supported time formats:

  Time Format	Display Example
  MM/dd/yyyy	05/29/2015
  dddd, dd MMMM yyyy	Friday, 29 May 2015
  dddd, dd MMMM yyyy HH:mm	Friday, 29 May 2015 05:50
  dddd, dd MMMM yyyy HH:mm tt	Friday, 29 May 2015 05:50 AM
  dddd, dd MMMM yyyy HH:mm:ss	Friday, 29 May 2015 05:50:06
  MM/dd/yyyy HH:mm	05/29/2015 05:50
  MM/dd/yyyy hh:mm tt	05/29/2015 05:50 AM
  MM/dd/yyyy H:mm	05/29/2015 5:50
  MM/dd/yyyy h:mm tt	05/29/2015 5:50 AM
  MM/dd/yyyy HH:mm:ss	05/29/2015 05:50:06
  MMMM dd	May 29
  yyyy-MM-ddTHH:mm:ss	2015-05-16T05:50:06
  HH:mm	05:50
  hh:mm tt	05:50 AM
  H:mm	5:50
  h:mm tt	5:50 AM
  HH:mm:ss	05:50:06
  yyyy MMMM	2015 May

  Date/Time Format Characters:

  • d – Date, from 1 to 31.
  • dd – Date, from 01 to 31.
  • ddd – Abbreviation of weekday (Example: Mon.)
  • dddd – Full name of weekday (Example: Monday)
  • h – 12-hour clock (Example: 1).
  • hh – 12-hour clock (Example: 01)
  • H – 24-hour clock (Example: 1)
  • HH – 24-hour clock (Example: 13)
  • m – Minute (Example: 1)
  • mm – Minute (Example: 01)
  • M – Month (Example: 1)
  • MM – Month (Example: 01)
  • MMM – Abbreviation of month (Example: Dec.)
  • MMMM – Full name of month (Example: December)
  • s – Second (Example: 1)
  • ss – Second (Example: 01)
  • t – Abbreviation of AM/PM (Example: A/P)
  • tt – AM/PM
  • y – Year (Example: 15, meaning 2015)
  • yy – Year (Example: 015, meaning 2015)
  • yyy – Year (Example: 2015)
  • yyyy – Year (Example: 2015)

• IsHandleCombineMarkCharacter – Define whether to migrate messages that contain combining characters. By default, this feature is disabled. The migration of messages that contain combining characters will fail.

  To migrate messages that contain combining characters, you can add the IsHandleCombineMarkCharacter=true string to the Customized features section. Note that with this customized feature configured, the migration performance will slow down.

• IsMigrateSystemEventMessage – Define whether to migrate the system messages (start recording message, recording saved message, meeting ended message, etc.) in all posts of the source Teams Chat.

  By default, Fly will migrate these system messages to the destination. If you do not want to migrate these system messages, you can add the IsMigrateSystemEventMessage=false string to the Customized features section.

• MigratePermissionsOnlyForSharePoint – Define whether to migrate the whole OneDrive sites or only migrate permissions of the OneDrive sites.

  By default, Fly will migrate the whole OneDrive sites of source chat users. If you want to only migrate permissions of the OneDrive sites, you can add the MigratePermissionsOnlyForSharePoint=true string to the Customized features section.

  To migrate the whole OneDrive sites again, you can remove the feature string or change the string value to false.

• TimeZone – Configure this feature string if you want to define the time zone for the sent time of chat messages migrated to the destination.

  The default time zone is Coordinated Universal Time (UTC). You can customize the time zone by adding the TimeZone=" " string to the Customized features section, and entering a number from -14 to 14 as the string value. For example, if you configure TimeZone=-8.5, the destination time zone will be UTC-8.5.

  NOTE

  If your defined time zones in the Define the time zone for messages option and this customized feature are different, Fly will use the time zone defined here.