 All I have been tasked with doing a total reorganization of a team site for leadership consists of files and a wiki, so we found the one person still using wiki, need advice on how to keep current setup visible while I basically create the new version. Is there a sandbox option in Teams? I have been asked to keep the new one hidden while it's in production and make it visible all at one time, similar to a web page being in production until it is published. That's in the best way to handle. Don't give them permission to the team until it's ready. Really? That is your production playground. You don't need a sandbox option, you just basically create it. Don't add anyone. Exactly. It's like anything, it's like a SharePoint site. Once we've created our new internet site, then we start adding people to it. Is it because you want to, or bring people in and out to do just their component, you need them to actually create, but then stop, but yeah, no different. The hard part with doing that is that, again, I don't know how this site is being used, all used like the SharePoint migration example of restructuring and redesigning is that people are still in there in that live environment, so they're messing things up, they're moving things, they're adding things, and so how do you replicate that over as far as the content? That's just something that you'd have to go in and look at and say, well, what conversations happened? You could just let your organization know, and this is back with what we used to do before some of the third party tools improved upon that process, but we'd say as of Friday at 5 p.m., we're going to start migrating. Just realize we're going to migrate over the weekend, and that anything new or that's changed will be lost for the new system. Therefore, pause yourselves, and then we'll do the move, and then you restart up within the new environment. I don't know what that, because honestly, for teams of teams, migration for moving and reorganizing third party tools. I work for ISV that has one that does that, so I don't do the native experience, and it solves some of that problem by going in and automatically doing it in minutes rather than a lot of the manual steps through the native experience. Any other suggestions? I mean, besides just telling people, hey, take a pause, and then we're going to move everything over? Yeah, I think it all depends on the size. Do you need to retain the metadata on the documents themselves? If you need the create date, you're going to need some third party tools. If you just want to do a copy and paste, and some of that doesn't matter, and there's not a lot of rework, then frankly, copy it. Keep track of what you've copied. Again, I think absolutely doing that at a downtime, especially if it's a high active site, you're going to really want to make sure before you go ahead, turn one off and turn one on that you do that compare, the number of files, the number of documents, the number of lists perhaps that you might have in there to just confirm, make sure everything looks good, and of course, when you do turn one off, I would say hold on to it, give it about 30 days, maybe 60 days. Just in case anything gets missed, you can always go back to it, pull it on over. I suppose it would be starting from the things that they're not having to replicate today, at least having that piece ready to go, and so that you have a less amount of work when you've got to do the copy everything over to the new environment to once you have a look at what you've actually got, because yeah, that whole duplication of information, and if they're still working in the old environment, then what's the difference becomes just too complicated? Now you could go in, again on the SharePoint side, and you could in the old version once you cut over, you could make the old environments or all those list of libraries read only, so that you lock out the changes, they'd still be able to go in and chat and do kind of all the different pieces, so you just need to make sure you emphasize the communication, hey this is happening, this is where we're moving things across, and kind of for the last mile experience as part of the communication, kind of charge everyone who has access to see something, say something, if there's content that's missing, let us know, or manually move those things across. The downside of that though would be the confusion from the user around where they are to where they're going, that pain point that sits in between, that then gives from a change, you know, being in the change coms perspective, where you get all these friction points then of what's there, and then they just start working in the new, and if we're talking we're not wanting them to have access to the new, they effectively don't have access to the files of the read only, so you then get caught in that the rock in the hard place between the two, because really you don't want them in the new environment, so the permissions aren't there, so the docs in there, so that anything could do probably more in that third party tour where you can, or have it where you could do some automation even if you think about it, so if they create something here it automatically duplicates over to wherever it's going to, might be another one, it'll come down to what are they still working in, what could you go don't put anything in here now for the next two days while we move over in, yeah. Well, see that's what I like about the, you know, you do the read only on the old site, only when you've moved the content over, you think that it's ready to go live, and then everybody the new one put read only, so then if they see, hey, something's missing, then I can go back and I can see, hey, there's something that's there, that's locked down, I can't modify, that's not there, and then as the admin's going to control that, again, I'm just trying to think of how teams works a little bit differently, that what's messier about teams in that scenario, and I get what Christine is asking about, because it's not like an intranet, it's not a SharePoint site, it's much messier, right, with all of the chats, with all of the, you know, all of those other components, with the other automations, well, there could be a ton in the SharePoint site as well. So, you know, I wish it was just as clean as, hey, let's duplicate the structure, let's then just migrate the content. But it's a to do place, and this is the thing, it's the place to go to do, so if you're there, and you're in that mode, that then, at some point, someone has to stop being in the to do mode for you to be able to do what you need to do or be able to do it hard and fast. So that's always the complexity, and then on top of that, what are they needing to have access to in that team, because that's a whole nother, are they creating lists, are they creating planners, are they creating, is there one notes, and they're doing it all day every day in meetings and taking notes, so there's so many other components that plug in. That is not just about SharePoint, there's just, there's a lot happening, so you really don't know how complex they're working to do place is, to say, you know, hold a nice little production environment, if it's really simple, you know, if it's a simple environment, it may not be as messy, but the more complex it is in their working environment, then the harder it's going to be to do a production environment. Right. And it's interesting, after just looking at it a little bit more around a total reorg of a team site for leadership. So the files that are in a team site, I guess I would recommend creating a new team. You know, if I really think about it, I don't think I'd want to mess with the shared documents, because those are your channels. So if you start messing around with that, that could really screw up some of the architecture that that's already been given inside of teams. So my advice would certainly be creating a new team, creating the channels of the file structure that you want to see, and then moving your folder or your files into that new location or copying them. Yeah, start again, kind of have something fresh. Yeah, because yeah, yeah, when you're reengineering, it's not going to work the same. It's just, yeah. Yeah, depending again, yeah, depending on what they have, I mean, if it's just, if it's just a, you know, a team with four channels and some files within each one of those and the conversations around, you know, all the chats that are going on there that are that are, you know, the channel conversations around that. So what migrates, what do you lose with that with that move? That's where I mean, the third party tool will benefit can move a lot of those other digital assets that you can't do natively. But yeah, it, it I'll be the first to say it in this conversation. It depends. Right. So let's there. And then don't forget the last part, which is now you have to communicate what you've done. So if you've re-architected it, channels are a new name, maybe it's a new department name. You know, you just need to also in your general channel put the announcement. This is the old layout to the new layout. And this is where you can find things to make it easier for people who are probably used to doing the other way. Yeah. Good old coms. Welcome to my world. My world change. It comes training. Clean up the mess, clean up on aisle 14, coms. That's it. Exactly. Don't step in that oil at the moment. Should you step in there? You will slip. Oh, good.