hello everyone and welcome to av points virtual lab where we're going to this time talk about teams chat migration using the av point fly solution my name is ron delaney i am the director of product knowledge here at halfpoint and i am joined today by tom tom you want to do a quick intro for yourself please sure hey ron um and everybody else out there my name is tom gazinski i'm our vp of solution engineering here at av point based out of chicago so for those of you that are current customers or maybe future customers i'm sure you've talked to myself or somebody on my technical solutions team here in north america so pleasure to be here today looking forward to this one excellent thank you tom our short agenda for this session we are first going to talk a little bit about av point fly in particular for tenant to tenant migrations uh for those of you who have migrated with us previously or are currently in the process of a migration you'll know that we have two different fly solutions one we call fly server and one we are simply calling fly which is hosted in aos for those of you who maybe this is the first time that you're you're looking at some of the migration options that we have available we're going to talk primarily for our on the one that is hosted because that's going to be our focus for tenant to tenant and once we talk a little bit about that we're going to focus for the rest of the session on the latest migration option migration type that we've added to our solution thank to thanks to some recent changes microsoft has made to their apis which is chat migrations for microsoft teams so we're going to get a chance to talk about why that is important what we're hearing from our different customers why you might find some value in that a little bit about how that setup actually works and some of the options that you have decisions you can make around how your chat actually is going to be migrated from one tenant to another and we'll finish up with some a little bit there on on what we call our just migration results what's going to be expected so once you actually start executing on these migration jobs what are you going to see in the destination environment is it going to be exactly the way it was originally is it going to be determined by some of the choices you made with the the option that you have available through the tool the answer to both of those things is yes maybe with a little asterisk next to it so tom and i will talk through um why those results look the way they do uh and again where that kind of comes from right please keep in mind as we go through our content here today that we do provide tons and tons of resources for everyone on havepoint.com you can go there and sign up for your free point portal account which gives you access to our case studies all the user guides for our various products of course release notes as we do releases every few months and upcoming webinars access to ebooks and so on so we want to make sure that you have plenty of resources for you as you start looking into performing these types of jobs so first let's get into tenants to tenant migration through fly uh hey tom so obviously f point's got a really really long history of doing sharepoint migrations from you know on-prem to on-prem on-prem into cloud but this is really our first kind of offering that we've rolled out that is fully hosted in clouds can you talk a little bit about you know what you've heard from customers and prospects when they were getting ready to do this type of migration yeah i think for a number of the customers across north america here um these migrations specifically it has to be something that's you know it's got to be quick to launch quick to prep quick to go right to move that data around as quickly as they need just based on some of the activities whether it's you know a merger and acquisition really trying to consolidate what they're what they're doing from an i.t perspective and that's really where the fly offering comes into play for those organizations today yeah yeah i would agree it's it's we've spent 10 years you know kind of moving to the cloud right and so we're at this point uh and people on the call will know this i'm not not saying anything you guys haven't sure thought about but basically we've spent 10 years moving to the cloud and if i'm already in the cloud i probably don't want to have to set up a server on the network to do an install for instance so we expect things in 2022 like you said to be hosted because it's quick it's easy get me in get me working as everything is ron yeah and so we released fly in half point online services back in january of this year with a specific focus on tenant to tenant migrations which is something that has become way more popular over the last couple of years like tom mentioned for things like mergers and acquisitions as an example a couple of companies decide to get together well you both had a m365 tenant originally with your name on it but now you want to combine all that data data into a new company entity right an organizational entity great set up a third tenant migrate everything into there and then you can decommission the old two tenants but how do i do that tenant to tenant migration and of course focused on our big data stores like exchange teams of course and so on all the way down through one drive for business so some specific things we're hearing about these types of migrations from our customers capability to bring over as much content as i can well sure that makes total sense keeping uh keeping with it the most fidelity as possible and so we're going to remember we're going to focus on chats here so think about that we've had the ability to do things like teams migrations for a while but we focused on well teams meaning the channels and the content and so on but what about the one-on-one chats what about the group chats right so we're gonna focus more on that and then for things like divestitures in this particular case you're splitting off maybe a part of your organization well when we migrate in that scenario some of the people you had worked with and and chatted with originally in teams are not going to be coming with you but you still might want to bring out those chats along for the ride for archival purposes right i need to be able to refer back to this conversation i had a year ago before everything i do got moved over to this new tenant in this new entity so there's a few different reasons it could be with reason one this idea of full fidelity as i was chatting with somebody before well in the new environment i want all of that stuff preserved and i want to be able to continue those conversations um a little little you know real world on this i mean tom you you and i and um for folks you never get to see the name but the folks that support us in these virtual labs and webinars that we work with um for instance someone in caroline who's who's on call and monitoring right now we all work together not within a team when we plan for these right we it's all a group chat because we don't have a dedicated team we're not sharing files we're basically scheduling and planning these out so we go to a new environment right we're going to want to bring those conversations over there with us tom does your anybody on your team do or working with maybe even members of other departments working in you know one-on-ones or or group chats i feel like at that point we use those almost as much if not maybe even more than formal teams uh constructs yeah the the team structure itself is great for the very formal conversation yeah i think for everybody else that's out there right even on on this call today or listening in the future the idea that everything takes place in there just isn't realistic it might not be quick quick enough to the draw for all of us to get this done so being able to have that reflexive you know that reflex type chat going on where something's getting talked about shared ideas are being brought to life then you move more or less the summaries of that into a formalized structure right over time but for us if i were to lose some of my group chats it would it would hurt right it wouldn't be it wouldn't be ideal for me or my team going forward honestly and that's really the purpose of the fly solution itself today in this structure is how different work has become over the last few years we talked about the the fidelity right ron you mentioned that just a minute ago and now it's not just the fidelity of the files and the structure but the other parts the nuanced behaviors within m365 that we also have to think about going forward yeah yeah absolutely hundred percent um and you're right you know it's people ping each other on the side we we share files directly and we know where those files go they go into the one drive when you share them through chats but yeah it's it's a it's a very continuous type of collaboration that people do this notion of you know back in the day what we call the iming i haven't heard anybody call it that in a while but that's essentially what you're doing it's like hey hey tom do you have that deck or hey caroline where's where's the link to that you know the overviews i can read through and this is all going on in chats and so if i'm going to do a migration 100 i need to bring that stuff along with me uh we have a question that's come in how do you handle thank you colleen for the question by the way how do you handle microsoft's throttling of data transfers oh colleen that is a big question i love the question yeah lovely yeah thank you anytime any kind of migration comes up this is a great question to ask i'm going to give you the the only answer i can probably within the time frame that we have here and that is we follow all of microsoft's best practices and we are constantly uh optimizing data transfer and just making sure that we're staying aligned with their apis working through apps distributed apps versus service accounts essentially everything that microsoft says here's how you minimize your chances of being throttled we do all of that we follow along with all those guidelines yep thank you for the question all right so with all what we're just saying in mind when fly first came out back in january these were your source and destinations exchange teams onedrive sharepoint groups and so on but with our recent release our may release you can see we have now added teams chat and let me be clear here we're not talking about the conversations that go on within a team those were being migrated before so if you have a sales team a marketing team an engineering team and you migrated the whole team you were not only getting the files you were getting the chats what we're talking about here are those one-on-one direct user to user and potentially group chats that happen outside the team as tom and i were just alluding to and if you're wondering well why didn't you have this in release or or why didn't you have this maybe even before in the other version the fly server version well it's because we know as customers of microsoft that even microsoft is continuing to evolve their functionality and so there were recent changes made to microsoft's apis that allow now for the chat migration this is a big screen of configurations here if you haven't used these products before these things obviously look a little different for you so don't worry about memorizing what you're seeing but for those who maybe haven't used one of our products one of the things you do early on is you set up what we call connections and connections is simply pointing the tool at your source and your destination well one of the things that microsoft is now going with is what's called the delegated app and a delegated app it has to do with the way the permissions work and the context in which the permissions are are given over to the application but essentially thanks to this change with delegated apps again some changes to apis we can now do chat to chat migrations so thank you microsoft for making that update it's been something we've been asking for for a while our customers have been asking for for a while and you'll notice though down a little bit further the lower right of your screen you see there's mention of something called a placeholder account here's one thing for those on the call who are technically minded for those of you who are maybe business focused and you just want to see that chats can be migrated congratulations right that's what we're talking about here that stuff is a big yes okay a big yes for those who might be a little technically minded the placeholder account is there because though we can migrate the chats now you cannot migrate one to one chats the way that it works is you can migrate your chats into group chats so for instance if it was just tom and i we can migrate that but when it gets to the destination it technically has to be a group chat which is going to require at least three users now this is again not from us this is based around microsoft's api so we're working within that framework uh we have another question what happens when the chats for users that are no longer with the company and get cleaned up get cleaned up during the migration good question i'm going to show you some of the chat options that are actually available in the tool and one of the things that you can do is you can do user you can do user mappings so you can still migrate those chats over um but in your in the scenario you're describing there michael what you're you're probably talking more about would be like an archival function like let's say i left the company but tom tom wants his and my chats when we migrate to the new tenant he and i are not going to be actively chatting any longer because i'm not with the organization but he wants it for archival purposes so that is supported it's uh it has to do with the membership we're just not going to reactivate the membership in the chats yep so let's let's get into that we'll talk about that as we get to a few more options here great questions reminds me a lot of the uh the older sharepoint on-prem to m365 questions that we would get and i think ron which you've got coming up here will will really help create some clarity around that yeah you're absolutely right tom it's this it's the same question right it's hey i had a user in sharepoint and his name's all over this content but he's not here anymore you know and so when i move the sharepoint stuff there is no rondolini in the destination environment right we we had ron delanian on prem there's no ron delaney now in m365 so how does it map those permissions how does it map that content yeah you're absolutely right tom it's it's the same it's the same thing what do we do with that right yeah so let's talk about some migration options here and give everybody a peek into what the ui is going to look like again now please keep in mind this is the hosted version of fly which runs in half point online services if any of you are curious about this you can visit afpointonlineservices.com and if you don't already have an account you can go ahead and spin yourself up a trial very very easy pick a data center tell it that you want to trial fly fill in a little bit of your info submit and you'll get an aos tenant with fly in there for 30 days in about five minutes so if you're curious you can go in there and take a look at that it'll also get access of course to the user guide uh as well so you can look at things like how to set up connections and so on but essentially you're going to create what we call a project if anyone's used our fly server product the on-prem install we call it a plan same thing it's a little wizard that's going to walk you through your setup and teams chat is its own dedicated type of migration and here here's the option that i was describing a minute ago advanced mode versus archive mode and you can see chat membership is migrated so this is going to be that scenario when you want the chat to be active in the destination so tom and i are both at that point halfpoint's gonna move tenants tom and i want to continue to chat after the migration that means we both have to be registered we have to be members of that that chat right so that's going to be the mode you're going to want to go with in that scenario that's the default so you don't even have to make a change the archive mode though is where you migrate everything over it's still visible in the destination but technically those people are not enrolled in that chat so it's still there right i'll be able to go in and see ron and tom and when i click on that i can see all of our historic conversations but i'm not chatting with tom in that sense right so back to michael's question what about people who are not here anymore no problem right that's the archival mode now of course keep in mind you have to think about what you're migrating if i want to migrate everybody and once then that if i choose archive mode then i'm literally doing the whole organization so tom i think this this thing comes up a lot in migration conversations kind of like you know big bang versus staged right like this is some old migration terminology but big bang is like i'm just gonna do everything in one shot versus i i plan things out and i make more selective choices as necessary yeah i mean 100 ron right i mean i think it's a matter of how you want to run this project but at the end of the day knowing that it's supported in both ways just makes everything a whole lot easier to make that decision around yep yep absolutely so what are you trying to do with that particular chat yep some additional options as well you can determine the scope do you want to migrate everything or do you want to just migrate within a particular date range do you want to migrate your attachments now remember as i mentioned earlier when you have a one-on-one or a group chat and somebody shares a file where does that go that goes into that person's onedrive so can you just migrate the one drives well you could but then you don't have the links to those things in the chats and tom i don't know about you but half the time when i share files with people i don't go and do it you know through sharepoint or through onedrive i do it in teams in that direct chat and same thing goes the other way right so i go back and when if i'm looking for that thing i remember tom shared it where do i go i go to the chat i'm smiling and nodding yes that is 100 correct i don't think i i don't think anybody really goes out of their way to share the other the other route so yeah even when you're going to look through that data right and find that information even if you get to the chat you know do you have to scroll through all the time no that files tab will help you too i know even for like this slide deck today it's where is it shared right where am i going to be able to pull that from specifically yeah yeah absolutely we're getting a couple questions coming in here can you do a staged migration where you do older prior to a specific date and then do a delta to get any new chats after that date you can do only what you're seeing here colleen you can do all or you can do chats later then so no there's no there's no mechanism to say i'm going to do it today and then i'm going to do it again later but i mean realistically you could because you have the ability to go through the tool and let's say you migrate today and then wait a week you could go back in at that point and then say okay well i'm gonna migrate chats later than last week when i did my initial migration so if you're if you're thinking kind of a standard um like a standard incremental migration it's a little bit more clicky than that uh as you can see what's what's going on here in the ui yep and we have one other question too uh thank you dennis will the chat migration work with a slack to teams migration currently in the aos version of flying dennis we are doing tenant to tenant so microsoft 365 but we do support fully support slack to teams migration through our fly server product and have for some time now too ron so it's not something that's that's new to market for us either it's something that's been around for a little bit of time and has continued to improve as something like this api that we're leveraging has become more and more available so has you know what is possible through that slack to teams migration yep yep absolutely absolutely um and just to put a ribbon on this so you notice there is a check box to mat to matt to my i tried to say migrating chat and i said matt to migrate the chat file attachments for users so could you do a onedrive migration and then migrate the chats and bring over the links you could or you could actually migrate the files at the same time if you wanted to in the other person's onedrive so that's great and it goes back to what tom and i were saying a moment ago about making choices right how do you want to run this we've even got some choices around sensitivity labels you need to have that that's part of that full fidelity that we were talking about earlier no labels if the labels exist remove them apply the same labels and so on and that down towards the bottom there's that user mapping so going back to the question that was asked a little bit earlier that's your other option for saying okay here's a user in the source map that to a different user in the destination if you need that right if you need that now with all that said right that's the wizards very straightforward you create your connection to your source and destination tenant you tell it all right i'm going to do a chat migration you do the advanced mode if you want live if you will chats in the destination you do archive mode in that scenario and what i didn't show you guys was the part where you actually get to pick and choose what users so you could do everybody in one shot or you can say all right i'm gonna migrate everybody in one specific team internally group of people and do it more staged and maybe maybe there's some very specific chats you got to handle them one at a time so it's up to you how you want to map that out and how you want to do it i didn't show that because that's standard to all of our migrations the source to destination mapping so i want to focus on the specific chat options there but now that we understand what some of those chat migration options are going to be what's the expected behavior so first a little bit of a roundup so what are we talking about here and this goes again back to to dennis's question a minute ago teams chat migration okay so this is an aspect of an m365 tenant to tenant migration which is what fly in aos currently supports the chats can have active membership or not and that's your archive mode if you will you can do all the chats in a range you can do the attachments or not as necessary and we can cover sensitivity labels that are applied to those attachments but here's something that's new messages will post under the service account name so this is what we wanted to to kind of wrap with here for today to show you guys what's the expected behavior now this is a little bit technical on why this is the case but essentially again this is this goes back to the api this goes back to the fact that there was a in the source it was a one-on-one chat let's say between tom and i between tom and caroline for instance in the destination you need to have it as a group chat so that was what that placeholder i mentioned was before that's okay literally you just make like a service account doesn't have to be an actual user they're going to need to be part of this chat when it lands in the destination but then they could be removed if need be but we also specify a service account and again this is just with we're us working within the framework of the api so tom when i say a service account is going to quote unquote post the chats and what we're seeing here on the screenshot right can you do a little bit like just describe to folks kind of what we're seeing yeah so i i like that at least in these screenshots we're using something that doesn't say admin for those of you that have looked at our environments over the past few years but when i would be doing migrations in the past as a actual administrator i would actually have a service account out there just an account that has access to these services specifically that would be called like this is chat placeholder or migrated chat account right or migrated data so then that way people weren't necessarily curious as to who this was but it was something that they were able to easily understand as to what's going on so in this event what is great about this and ron we spent a lot of time talking about it is although the actual conversation is brought over i can still see that isaiah was the one that posted it what time right i have that date stamp as well as the message content or subject specifically right the context is still there yeah what's important to understand about this then ron is as it continues to move forward all of that type of information is actually something that you can surface through that lovely search bar that's directly above so if i were to be searching for something with isaiah and marketing campaign that same information would bubble back to me because it's still indexed and still something that can be searchable throughout teams yep yep absolutely so essentially what we're saying is this this service account i'm just for those of you that have seen microsoft demo accounts right we just use the global admin in this because it's easy but this this service account that's being used as tom said has full access to that service in m365 and what does that mean that means it can go in and it can post the data that we're pulling from the source environment so it might look a little odd you say well so the service account is going to be in the header to tom's point it will be for the migration but now this is a live migration so if if megan just starts chatting with isaiah you never you don't see that it's only in the historical part so it's it's it's it's one of those things that in accordance with the way the api kind of demands the way we can access that information that we do to get this over here but historically when you scroll back up okay you can ignore it isaiah is searchable hey megs is searchable volunteer like all the stuff that's in there you'll be able to go in there and find that jump right to it and just carry on it's just as if it's a brand new conversation going forward we can remove the placeholder accounts even if we need to and business as usual but initially the stuff that gets brought over is going to have that service account name at the top yep because of the access megan doesn't have full access to the team service we're not working within the context of megan even though this is could be megan's chat or isaiah's chat that's just kind of one of the caveats yep all right go ahead tom i was about to say we had that slack or that slack question earlier yeah very similar as to what that would look like even from that point of view too just to be clear right so as that content is brought over the chat brought over right the files and everything else that you might need to bring with those are the things that we can actually grab as we do this yeah that's a great point it's because again it's just the way the apis allow for it right so if i was bringing isaiah and megan's chat from slack then okay but it's still neither of those two people have that elevated level of access to the team service to be able to just go in there and write these things in that way so we use that same context we need that global level of access if you will it's basically full access to the teams the team service to the mailbox to the sharepoint site um just to be able to get it in regardless of the source yeah 100 correct thank you tom for adding that exclamation point on the end there i appreciate that um a question from marlin will this team's chat migration be available on fly server version 4.8 so good question marlon it is not available as of right now but it is being worked on i don't have an exact uh release for you for that we just put out the 4.9 and the chat is not supported in the 4.9 as of yet but it is being worked on yep all right if you need help marlon getting up to date to 4.9 feel free to reach out to your av point sales rep or customer success representative and we can help you with that process as well too just to take advantage of some of the the new functionality in fly49 yeah absolutely and and that's a great segue for us here tom because i was going to talk about that stuff as well but yeah marlon in your particular case look if you can't wait right if you're in the middle of your migration project and you're saying hey i've been migrating with fly server and it's doing everything i need but wow i i love the idea of being able to migrate my chats you guys didn't let me do that a month ago i was like you're right we didn't because we couldn't do it a month ago and now we do right you know what marlon you could potentially just use flying aos just to do the chat migration so yeah definitely reach out to your customer success rep reach out to your account manager follow up with them on that and they'll be able to either give you more information about maybe when it's going to be available in fly server but if you're in it right now your best bet might be do everything the way you're doing it right but when you want to get to those chats you know talk to us we can help you out maybe get it done just through the aos version yeah for you good so that's going to wrap us up today everyone please as a reminder if you haven't already done so definitely go to afpoint.com to sign up for your free portal accounts to gain access to all the resources we talked about and then building off of marlin's question and tom's response yes absolutely anything more you want to know about this if you haven't used it before if you'd like to get set up for a demo to take a look if you want to start a free trial by all means talk to somebody here at halfpoint and we're going to help you get going with that beyond that i want to thank everyone for attending our session today thank you tom so much for your great contributions as always and i hope everybody has a great day thanks everybody you