Bailey
My feedback
-
2 votes0 comments · ShareGate migration tool Suggestions » 09- Tasks, Migration reports & Scheduled tasks · Flag idea as inappropriate… · Admin →
-
2 votes0 comments · ShareGate migration tool Suggestions » 07- Explorer · Flag idea as inappropriate… · Admin →Bailey
supported this idea
·
-
5 votes2 comments · ShareGate migration tool Suggestions » 09- Tasks, Migration reports & Scheduled tasks · Flag idea as inappropriate… · Admin →
-
2 votes1 comment · ShareGate migration tool Suggestions » 14- Connect to SharePoint and Office 365 · Flag idea as inappropriate… · Admin →Bailey
shared this idea
·
-
1 vote0 comments · ShareGate migration tool Suggestions » 09- Tasks, Migration reports & Scheduled tasks · Flag idea as inappropriate… · Admin →Bailey
shared this idea
·
-
3 votes1 comment · ShareGate migration tool Suggestions » 08- Quick Actions · Flag idea as inappropriate… · Admin →Bailey
supported this idea
·
-
27 votes11 comments · ShareGate migration tool Suggestions » 04- Reporting · Flag idea as inappropriate… · Admin →
LP Lavoie
responded
We understand this need, but seeing as it is fairly trivial to do in SharePoint Management Shell, for the time being we’re concentrating our efforts on more complex scenarios that have no easy alternative.
An error occurred while saving the comment
As a non-developer I would also like to express the need for reporting such as this as it would be fairly important during a migration to have the listing of email enabled libraries and the email address assigned so that we could provide that information to the end users so they would know which processes would break due to the email address conflict. I would also be helpful to know in general so that we may gauge inbound email impact (across the farm) if something were to break.