Converting Classic Department Sites to Modern Sites with Microsoft Teams

%3CLINGO-SUB%20id%3D%22lingo-sub-1072947%22%20slang%3D%22en-US%22%3EConverting%20Classic%20Department%20Sites%20to%20Modern%20Sites%20with%20Microsoft%20Teams%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1072947%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Everyone%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'd%20like%20to%20get%20some%20feedback%20on%20my%20proposed%20general%20direction.%20I%20shall%20first%20lay%20out%20the%20current%20landscape%20and%20then%20describe%20the%20plan%20going%20forward.%20Any%20feedback%20is%20welcome%20and%20thank%20you%20in%20advance.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECurrent%20State%3A%3C%2FP%3E%3CUL%3E%3CLI%3EWe%20have%201%20Office%20365%20subscription%3B%20however%20it%20appears%20as%202%20tenants%3CUL%3E%3CLI%3EThis%20is%20because%20we%20began%20online%20services%20back%20in%20the%20day%20(2009%2F2010)%20with%20BPOS%20(Business%20Productivity%20Online%20Suite)%20which%20was%20the%20precursor%20to%20Office%20365.%3C%2FLI%3E%3C%2FUL%3E%3C%2FLI%3E%3CLI%3EBecause%20we%20were%20early%20adopters%2C%20our%20tenant%20is%20oddly%20comprised%20to%202%20domains%3CUL%3E%3CLI%3EOur%20old%20site%20collections%20begin%20with%20xxxxxx-%3CSTRONG%3Eportal1%3C%2FSTRONG%3E.sharepoint.com%3C%2FLI%3E%3CLI%3EOur%20newer%20site%20collections%20begin%20with%20xxxxxx.sharepoint.com%20(no%20portal1)%3C%2FLI%3E%3C%2FUL%3E%3C%2FLI%3E%3CLI%3EThis%20also%20means%20we%20have%202%20root%20sites%20(portal1%20and%20non%20portal1)%3C%2FLI%3E%3CLI%3EOne%20issue%20I%20have%20seen%20with%20the%20dual%20domains%20is%20that%20we%20cannot%20utilize%20the%20create%20a%20list%20from%20an%20existing%20list%20option%3CUL%3E%3CLI%3EIf%20I'm%20in%20a%20xxxxx.sharepoint.com%20site%2C%20I%20cannot%20create%20a%20list%20from%20another%20list%20that%20lives%20on%20a%20xxxxx-portal1.sharepoint.com%20site%3C%2FLI%3E%3CLI%3EIn%20the%20past%20I%20had%20issues%20creating%20powerapps%20from%20xxxxx-portal1.sharepoint.com%20sites%20as%20well%3CUL%3E%3CLI%3EI%20believe%20this%20have%20since%20been%20resolved%3C%2FLI%3E%3C%2FUL%3E%3C%2FLI%3E%3C%2FUL%3E%3C%2FLI%3E%3CLI%3EUnfortuately%2C%2099%25%20of%20our%20data%20lives%20on%20the%20old%20xxxxx-portal1.sharepoint.com%20sites%20and%20sub%20sites%3CUL%3E%3CLI%3EAdditionally%20that%2099%25%20of%20data%20is%20nested%20in%20sub%2C%20sub-sub%2C%20sub-sub-sub%20sites%20within%20a%20single%20site%20collection%3C%2FLI%3E%3C%2FUL%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3EWhere%20I'm%20trying%20to%20get%3A%3C%2FP%3E%3CUL%3E%3CLI%3EThe%20plan%20is%20to%20create%20new%20site%20collections%20for%20each%20functional%20area%20(Technology%2C%20Marketing%2C%20HR%2C%20etc)%20in%20their%20own%20separate%20site%20collections%3CUL%3E%3CLI%3EThe%20new%20sites%20would%20have%20the%20xxxxxx.sharepoint.com%20domain%3C%2FLI%3E%3CLI%3EWe%20would%20eventually%20deprecate%20all%20xxxxxx-portal1.sharepoint.com%20sites%20after%20the%20data%20is%20copied%20to%20the%20new%20locations%3C%2FLI%3E%3CLI%3EWe%20will%20utilize%20Hub%20sites%20for%20each%20functional%20area%20to%20share%20general%20info%20with%20all%20staff%3B%20however%2C%20each%20function%20area%20within%20a%20major%20arm%20of%20the%20company%20will%20also%20have%20its%20own%20modern%20Team%20site%20where%20they%20do%20day%20to%20day%20work%3C%2FLI%3E%3C%2FUL%3E%3C%2FLI%3E%3CLI%3E%3CFONT%20color%3D%22%230000FF%22%3EOne%20of%20my%20major%20questions%20with%20this%20is...should%20we%20attach%20Microsoft%20Teams%20to%20those%20functional%20Team%20sites%20or%20should%20Microsoft%20Teams%20NOT%20be%20used%20for%20permanent%20type%20situations%3F%3C%2FFONT%3E%3C%2FLI%3E%3CLI%3E%3CFONT%20color%3D%22%230000FF%22%3EAnother%20major%20question%20is....what%20happens%20if%20we%20do%20attach%20a%20Microsoft%20Team%20to%20a%20functional%20area%20and%20they%20decide%20they%20don't%20want%2Fneed%20a%20MS%20Team%3F%3C%2FFONT%3E%3CUL%3E%3CLI%3E%3CFONT%20color%3D%22%230000FF%22%3EAs%20I%20understand%20it%2C%20we%20cannot%20remove%20a%20Microsoft%20Team%20from%20a%20Team%20Site%20without%20deleting%20the%20entire%20site%20collection%20and%20its%20contents%3C%2FFONT%3E%3C%2FLI%3E%3C%2FUL%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%3CFONT%20color%3D%22%23000000%22%3EThank%20you%20for%20any%20suggestions%20you%20have.%20Also%2C%20is%20there%20anyone%20else%20in%20the%20same%20boat%20as%20us%20(early%20adopters%20with%20basically%202%20types%20of%20URL's%20in%20a%20single%20tenant%3F%20%5Bxxxx-portal1.sharepoint.com%20and%20xxxx.sharepoint.com%5D%20%3F%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1072947%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EBest%20Practices%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETips%20%26amp%3B%20Tricks%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Contributor

Hello Everyone, 

 

I'd like to get some feedback on my proposed general direction. I shall first lay out the current landscape and then describe the plan going forward. Any feedback is welcome and thank you in advance. 

 

Current State:

  • We have 1 Office 365 subscription; however it appears as 2 tenants
    • This is because we began online services back in the day (2009/2010) with BPOS (Business Productivity Online Suite) which was the precursor to Office 365.
  • Because we were early adopters, our tenant is oddly comprised to 2 domains
    • Our old site collections begin with xxxxxx-portal1.sharepoint.com
    • Our newer site collections begin with xxxxxx.sharepoint.com (no portal1)
  • This also means we have 2 root sites (portal1 and non portal1)
  • One issue I have seen with the dual domains is that we cannot utilize the create a list from an existing list option
    • If I'm in a xxxxx.sharepoint.com site, I cannot create a list from another list that lives on a xxxxx-portal1.sharepoint.com site
    • In the past I had issues creating powerapps from xxxxx-portal1.sharepoint.com sites as well
      • I believe this have since been resolved
  • Unfortuately, 99% of our data lives on the old xxxxx-portal1.sharepoint.com sites and sub sites
    • Additionally that 99% of data is nested in sub, sub-sub, sub-sub-sub sites within a single site collection

Where I'm trying to get:

  • The plan is to create new site collections for each functional area (Technology, Marketing, HR, etc) in their own separate site collections
    • The new sites would have the xxxxxx.sharepoint.com domain
    • We would eventually deprecate all xxxxxx-portal1.sharepoint.com sites after the data is copied to the new locations
    • We will utilize Hub sites for each functional area to share general info with all staff; however, each function area within a major arm of the company will also have its own modern Team site where they do day to day work
  • One of my major questions with this is...should we attach Microsoft Teams to those functional Team sites or should Microsoft Teams NOT be used for permanent type situations?
  • Another major question is....what happens if we do attach a Microsoft Team to a functional area and they decide they don't want/need a MS Team?
    • As I understand it, we cannot remove a Microsoft Team from a Team Site without deleting the entire site collection and its contents

Thank you for any suggestions you have. Also, is there anyone else in the same boat as us (early adopters with basically 2 types of URL's in a single tenant? [xxxx-portal1.sharepoint.com and xxxx.sharepoint.com] ?

0 Replies