 cross force migration to perform. It's a little complex though, and that I need to leave the source AD intact while also migrating everything to the destination for us. Long story short, too late, Andrew. It's a company split. The problem is that the source is server 2016 and the destination is 2019. ADMT seems a bit risky. Can anyone suggest a guide or a commercial software that will handle this scenario? Thanks. So I know that there are third party solutions that are available. That was how I would say that. I consider the details he's throwing out. There are largely distractions or red herrings. I mean, you're just trying to move data across selective set. I assume that's part of this separation and moving the data or copying the data across is not going to harm his 2016 environment or the domain. It really just comes down to go demo a bunch of third party migration tools and find one that you like that'll work for you that you can afford. There you go. Is that better, Christian? Thank you. Yes. You're welcome. That's all I was going to say is I would definitely. First of all, when anybody's migrating anything more than something that they can use the move tool for, especially if they're doing cross domains, cross tenants, anything you have to play in mapping for. Number one, I always recommend you at least engage a consultant to help you answer questions, just to make sure you're not going to lose data on the way or come up with something that's going to cause a big gap in the migration. But second of all, plenty of third party migration tools out there that can pick up that data in its entirety and take whatever you need so you get to the other side and you're not missing anything and it works the way it should and it maps to the users the way it should. New permissions don't go anywhere, things like that. There's something that I think is sound advice out there too. If you've talked about working with a partner, there are certainly people out there that do this for a living day in, day out and can provide a lot of advice. Microsoft also offers fast-track services as part of that. If you've been through that, if you don't need the basics trainings of what's available, if you already know that your scenario is beyond what the free tools, what the mover tool that Microsoft provides can handle. So I know on our services side, the majority of our migration customers are failed mover migrations. It's more complex, they need something more than that. But another thing is that you get advisory services part of fast-track and that's something that Microsoft actually covers the cost of. So you go take a look at Microsoft fast-track or work with the fast-track partner that does migrations as well and get those advisory services can actually help lead you down the right path and make sure that you're optimizing your project. But yeah. That was your gig a while ago, right Neil? It was. Yeah. So for the, I'm trying to dig into kind of read between the lines on the questions, whether it's an online migration that's up right here. For online migration, certainly fast-track can help, no question at all. Well, that's I guess that's no, it's SharePoint though, unfortunately. We don't do that. Oh, is that just? That's what I was kind of wondering. If it's online, covers going to online and this still correct. It does. Yeah. Yeah, we do. We do. The scenario here is like I've mentioned, there's two things right, the splitting and AD had a look of it. I've got to keep the existing one intact and I'm going to split to a destination. So they need to somehow replicate that whether they can just take some domain controllers from one and split it. But it's a new forest. So the AD migration tool that they're referring to there, you know, it's, it's, yeah, this is a bit risky, but it does work, right? You might just see some testing, but as you already said, there's other tools that can do it as well. The second portion, which looks like it's a, if it's a SharePoint migration from server 2016 to 2019, that's documented to help. Some great tools out there as we've already alluded to, but that process is very well documented. The underlying complexity is in the identity management piece. You know, there's a great piece of PowerShell, move SP user, which works exceptionally well, but you've got to script it and process it and make sure all the identities are mapped properly. But it's, you know, everything's, everything's there. It's just a case of going through the process and testing it. Yeah, don't try it for real the first time with your production environment. Really, set yourself up with a test server, you know, kick the tires a little. Yeah, so many of this. And I know like we're trying to push the third party services around this, but you know, you really need to weigh the options. Like you might have the technical ability to go in this, but be new to the migration world. What is that opportunity cost? It's your time and the effort and the risks associated with the versus going, bring somebody in who does this day in, day out. I'm just saying. Well, hashtag, I'm just saying. Christian, we were talking about the gray hairs earlier. Are those some of those from you that you're willing to share? I've been away from migration for a long, like directly involved for a long time. Like, but yes, that's when I started to go gray. Sean had thicker, fuller hair than I did when he got into migrations. I venture guest to say normed it too. Yeah, I don't know what you guys are talking about. I love migrations. I think it's making me younger. Take that wig off. I love migrations, but again, I learned something new from each one. And if it's your first one, I 100% agree. Even for myself, I realize is it worth my, everything's a trade off of time and money and frustration in this case too. And sometimes it's cost you less in the end to have somebody do it for you that has the skills and the experience. Yeah, it may cost you less in the end, but don't take it in the end. If you know what I'm saying. Yeah, Mike. Mike. I know what's going on, Mike. Mike. Yeah. I have an SPOD migration. So yeah, funny games. I always try to avoid taking it in the end, Sean. So yeah. I knew I liked you.