It supports multiple workloads—such as Teams, Exchange, SharePoint, and OneDrive—all from one place. This is important for us. I would not use it otherwise. They have one or two competitors that I assume perform multiple workloads concurrently. It provides data security for tenant-to-tenant migrations, but I do not deal with that. If they can do DCC, that is good enough for me. The only thing I am worried about is the security. They have got SOC 1 and SOC 2. They have got every single thing my customers ask for. They are transparent about their data processing. I am reasonably certain that I know where the data is going, and it is not sticking around, so I am not worried about that. The fact that it is ISO-certified is not important to me, but it is important to my customers. They ask about this from time to time. For me, it is just a tool, like a toolbox, like a hammer or a saw. I know what it does, but every now and then, one out of ten customers—their lawyers or their compliance department—asks a bunch of questions. I just point them to all the certifications. They can decide whether they trust it or not. As far as I am concerned, they have got everything covered. We could realize its benefits right after deployment. It moves pretty quickly. Once you get it connected to two things and you link the things, it is pretty obvious that it is going to do exactly what you want. I used the old product back when it required a SQL Server. It took a month to install, whereas now, I can start working in days or even hours if I have the right privileges and I am not fighting for the infrastructure and trying to get the customer to give me resources and install all the things in their environment and get connected to the Exchange Server. It is all SaaS now. It supports the migration of Microsoft Teams, including Teams chats, when it comes to our customers’ collaboration. It is the most difficult thing for them to migrate. It does not come across as the cleanest, and I understand why. There is a limitation of the API, but it is an important functionality. It is a necessary evil. When customers want it, I have to deliver it, but I make every attempt to scope it down. They want all the chats for all the time, which is not practical, so I tell them that I can give them the last 15 days or 30 days, and then they can use some kind of archiving utility on the source side to capture everything for compliance reasons, but I cannot bring across everything. The tool is not made to bring across everything. So, it is important, but it needs to be used appropriately. It is not like mail where they can ask to give them absolutely everything. Quest On Demand Migration moves everything, but it is not always obvious where they are. That is the problem, but it is not their fault. They have done everything possible to bring things across. A common thing is that people are looking for recorded meetings, which are in the OneDrive store of the user who initiated the recording of the meeting. Before you migrate the data, you can go into a Teams chat and click on a meeting, and it will start playing the meeting no matter where you are and no matter which participant you are. Post-migration, when it is on the other side, you have to be the person who recorded the meeting because it comes across through the OneDrive migration, so it is hard for it to recreate the exact chat state with all its full feature functionality on the other side. I understand that there is a limitation of the API. For us, it is just about training the users. We tell them that if something is absolutely important, then back it up themselves. We tell them where to expect things because not everything comes across as clean as they might hope. We have a 99.9% success rate with migrations. Everything comes through as we would expect. When it does not, we open a support case. It might indicate one giant file in somebody's email that did not come across because there is a 25 MB limitation. Everything is explainable. Every support case I have opened has explained if there is any throttling going on, if there is an outage, or if there is some type of problem. No support case that I have opened has gone into a black hole. They are pretty responsive. I am not worried about that. The users are aware of migrations because we do a lot of high touch. We are giving them a new laptop. We are moving the laptop from one domain to another, and it takes a while for their mail to download on the new Outlook client or a new profile. There is always some type of indicator. It is a matter of how disruptive it is or how much time it takes, and that is where we come in and try to make that as minimal as possible. We also handle more complex migrations where other products are involved, such as two-factor authentication, MFA, Duo, Okta, and things like that, and the authentication might not be purely on Azure. Whenever we do that, there is a lot more hand-holding or what we call a white glove type of service. So, they are never totally unaware, but we try to keep it minimal. If we can get them in and out in fifteen minutes, and they are working, that is awesome.
