The granting of consent for doing the different tasks is confusing. You have to go to a few different places. It's not immediately obvious. They need to either have better documentation or move everything to one place. It would save users from facing multiple error messages. 

One significant issue that often elicited complaints during domain migration was the need to set the primary UPN for objects once they were migrated to the target. Previously, customers had to handle this using PowerShell or other means independently, as the tool lacked this capability. However, it now includes the functionality to address this requirement.

If it weren't for the limitation imposed by the size of their environment, leading them to opt for an on-premises solution, I believe utilizing On Demand for all our customers would truly highlight the strengths of the product.

The cooperation with Microsoft regarding changes in their cloud products can certainly be improved.

There are certain tools or apps that are not supported at the moment, but as I know Quest, they'll be very fast in picking that up and very fast in adding on features. At the moment, it makes my life easier when I do a migration. We can do Teams and we can migrate the chat, but I do run into some features, such as Wiki and probably Whiteboard, that are not supported at the moment. Since Teams has grown and has become such a key app or service, sometimes, it's hard to explain to customers that we cannot migrate everything. If they would improve that, I'd probably be one of the happiest people on the planet.

One of the things that can be included is automation. For the matching and the migration process, they could put in some automation. I'm only allowed about 25 users at a time. If it's a large tenant, it takes quite a while to put them in the batches. If there is enough automation into that, that'd be perfect. Overall, I'm at a very high level of satisfaction, but it would be good to have these features.

We had some issues with migrating Teams. So, we make the customers aware of a few things early on. Some workloads are not moved. It would be nice if we could move all workload to Microsoft 365. The migration is not seamless. The user has to run the scripts during the migration. So they know when the migration is being done. Microsoft Teams is tough to migrate.

In terms of Microsoft Teams, the only disappointment for us has been how the chats are migrated. They just don't look exactly the same as they would if you were logging on as normal. Obviously, when it comes to the user experience, you want the look and feel of everything to be replicated identically, and chats is the only part of it that doesn't look identical. However, it's not a "car crash." It's a slight deviation from what people would expect. I had to explain that to the company this morning and no one raised an eyebrow or had any complaint or feedback about it. They just accepted that not every tool is 100 percent perfect. 

That is the only drawback and the only area that the tool doesn't seem to cover, but I don't think it's a limitation of the tool. I think it's a limitation of Teams. So we completely understand why, and maybe in the future they will work out a way to work with Microsoft to get that to look and feel a bit better.

Their support interface is not so great because you need to go through several links before you can raise the ticket. Sometimes the interface freezes up, and there is some downtime. They give us some notice. It says at the top of the interface that there will be scheduled maintenance in a given region or there is currently an outage. You can see upcoming downtime in the portal and plan accordingly. 

They could provide on-premises to online exchange components for the platform. It would be highly valuable.

It does what you think it would do in terms of the dashboard, but we are typically migrating a subset of the users, and it always shows us the macro view. If there was a way to scope it down to just the users that are in scope, that would be more useful. 

It would be more useful if I could scope the dashboard. I would like to be able to scope the users that I want to see to a much smaller list. When I am looking into a tenant with 35,000 accounts, and I am only moving 2,000 of them, I wish that the guys had been smarter about the discovery, and I could have only discovered those accounts, but there is not too much to complain about. They even have a button on the console saying Send An Idea, so it is hard to fault, but I wish they could do discovery through a pop-up dialogue.

I would like a drag-and-drop matching of accounts and mailboxes. I would like to be able to map multiple mailboxes from multiple sources to one mailbox.

They need to make the dashboard editable in the browser instead of only through CSV/scanning tenants. This would have sped up correcting any mistakes or changes to mappings.

They should introduce a module for migrating power automation for users.

There needs to be better handling of the various M365 group states instead of having to ensure you follow the exacting order for migrating them. Think M365 groups with/without Teams or with/without SharePoint sites attached.

Error handling resolution could be a little more helpful with some more tips/presenting the entire error front and center. That said, the support team is willing to help with any issues you may have with misconfigured source tenants!

We opted not to migrate chats due to how they are presented to the target users. The guide does say this is a Microsoft limitation.

Lastly, allow us to set the session timeout and be tab aware.

It's definitely the Microsoft Teams functionality that has a lot of aspects where improvements are needed. Microsoft 365 Groups are tightly connected to Teams and there are a lot of improvements needed there as well.

I see potential in the SharePoint functionality. But right now, when it comes to SharePoint migration, we often have to use another tool because the SharePoint part in On Demand Migration is like a kid; it's very young and not mature. I would get rid of other products and only use On Demand Migration for SharePoint, if I could. The capability is there, but it is not that strong at the moment. That could change in the future.