Quest On Demand Migration Reviews

I am working for a consultancy company, and we help customers migrate from one tenant to another. For example, in a situation, where B2B is being merged, we help a customer realize the business case technically. We help to move a few users from one tenant to another or merge tenants. Quest is ideal for that because it has one interface, and it's very easy to use.

It supports multiple workloads from one place. It's very nice. It's very fast. Depending on the license that you have, you can combine anything in parallel. There are certain limits, and you can't oversize certain workloads, but it's possible. That's what I like about it. I did a migration for a whole tenant with 100 users just over a weekend. It's easy. This support for multiple workloads is very important to me because otherwise, I'd have to probably schedule with a client and tell him when we're going to move each workload. Because I can move in parallel, currently, all I need from them is accounts. If I have the right accounts and the source and the target, I can start in the background, which makes my job a lot easier.

It encrypts the communication between two tenants while I migrate. I'm not 100% sure about how encrypted it is. It's probably SSL 1.2 and TLS 1.2 encryption, but I'm very certain of the security, and I feel very safe. When I start migrating, or before the migration, I have to create the organization and the project, and I can choose the location. That's the first part that makes me feel safe. I know we're within the European Union, and from the architectural model, I know that it's encrypted. That is sufficient for me.

It's ISO-certified, which is important to me. Whenever I propose a solution and offer certain tools, I have to make sure that they're ISO certified. That's basic security. It's one of the base requirements for me.

It's crucial that it supports the migration of Microsoft Teams, including Teams chats. If it didn't support that, I probably wouldn't choose it. It's nice if you can do SharePoint and if you can do Exchange. If it can't support Teams and especially chat, I wouldn't suggest it to my clients, and I don't think any client would choose it.

I don't have to reach out to IT too often for support for migration. The number of support cases IT had to respond to as a result of the migration is not more than three or four. Most users don't notice that they were migrated after we completed a migration. Once in a while, they do notice, but we do communicate that there is a migration. Usually, they don't notice. With good migrations, they don't notice that there's been a change in the environment.

What I like is that for each use case, I can choose a module or a different combination of modules. For example, for a merge for a use case, all I have to do is just order a different license, and that's it. I like the migration module because it's straightforward. I can use it for all services within Office 365. That's what I like about it.

It's very easy to use. What I like is that if there is an error, for each task, I can find out what actually went wrong. If I'm lost, I can contact Quest support. They're very reactive. They're very helpful, but generally, it's straightforward.

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.

I have been using it for three years.

It's very stable. It's usually very fast. 

It's scalable. I know that there is one that's running on Azure, and it's automatically scaling. Whether I'm migrating 100,000 users or whether I'm migrating 10 users, I can do it very fast. So, I assume it's scalable. Because it's a SaaS solution, I can't look into its technical details, but it's always as quick as I need it to be.

We're a very small company. There are only 10 of us. Previously, I worked at a larger company where I used it as well. It does support multi-geo, and it's very good. Our clients are small to medium enterprises. Previously, they were medium enterprises. I switched just a few months ago. So, I've used it for small customers, and I've used it for larger environments as well. There is an upcoming project where I'm supposed to migrate 15 tenants into one. That'd be a rather large migration, and I'm going to use Quest On Demand Migration for that.

I don't have to interact with them much. There is not much ticketing. Usually, when I open the ticket, I put in the diagnostics that they need, and I either get a response straightforwardly or we just have a quick call. There is not much interaction going on. There are not more than three or four email exchanges until a case is resolved. Their support is highly qualified, and that's why I very much appreciate them. They're very helpful at the same time. I would rate them a ten out of ten.

Positive

I did use ShareGate for a while, but ShareGate is not as good with Teams migration as Quest is. That's why I switched to Quest.

I have not used any other solution from Quest. I know that they're there. Once in a while, I use Nova, which is their multi-tenant solution. I've recommended it to one of the customers, and that's it.

It's on the cloud. That's what I like about it. One of the nice things is they have a web interface. So, there's nothing to install and no agent to run. I can run agents if there's any local Active Directory involved, or if you're doing Active Directory to Active Directory migration, but the core solution is only on the cloud. It runs on Azure as far as I know.

I'm usually the one setting it up. There's not much to do. It's straightforward. You just need to put in two credentials, which are the local admin of one tenant and the local admin of the other tenant, and you need to consent to a few grants that they're asking for with a few services, and that's it. It doesn't take more than 15 minutes.

It requires maintenance once in a while. One of their pages tells you whether there's a service that's been degraded or if there's any maintenance going on. They're straightforward with that, and I very much appreciate that.

I have seen an ROI. If I wouldn't have been able to use it, we wouldn't have kept some of the customers that we now have. So, customer satisfaction from the prime migrations is my return on investment.

It is quite cheap. Previously, I used to work for a big company, and they get quite a good deal, and now, I'm working for a small company, and even they get quite a good deal. So, its pricing is quite fair.

I've not looked at all the products on the market. I've looked at bigger ones like AvePoint Fly and ShareGate. I chose Quest because I knew it previously and it's fast. I do like its troubleshooting possibilities. Whenever there's an issue, it's very straightforward to see what the issue is. It's easy to use, and it's quicker than multiple solutions on the market. This is my impression.

I would recommend using it. If you've done a few migrations with this, and if you use another product, you definitely learn to appreciate the tool.

It has made my life easier. It's very possible to script everything with PowerShell, but you would need quite a deep knowledge of PowerShell and Microsoft Stack. Since Microsoft 365 is a fast-changing environment. It would make your life easier if you choose a well-known solution such as Quest On Demand Migration rather than just trying to script everything because it takes quite a bit of work to get it all running with the script. Life is easier if you don't have to do it.

I would rate Quest On Demand Migration a nine out of ten.

We use the solution for M&A - Office 365 tenant mergers.

We can migrate all of our users/shared mailboxes/OneDrives/MS Teams/SharePoint Online into one dashboard! 

We can connect a source tenant in seconds, perform an initial discovery, and work out the number of licenses we need (and the volume of data that needs to be moved). This allows us to accurately plan and allocate the necessary resources to the project from the outset. 

We can rapidly provide high-level plans with confidence to key stakeholders.

ODM has given us the platform to rapidly support our M&A activities and tenant consolidation from the get-go. We're able to pre-stage all of our users' data from the various O365 services and minimize the cutover window from tenant to tenant. ODM saves time by not having to continually monitor migration processes through the use of task scheduling and email alerting.

The comprehensive user guide allows you to self-skill or works with the Pro Services team for knowledge transfer. Quest genuinely is flexible and you can do what works for you.

It's a "one-stop shop" for tenant-to-tenant migration, negating the requirement for various tooling and additional license costs. We can easily and simply work out the cost for any migration work that is required with the licensing model.

The ease of use is great. We can begin skilling multiple members of the team to support concurrent M&A migrations to offer better support to our businsses ambitions around growth.

Being able to migrate on-prem directory synced accounts/shared mailboxes to cloud-only is a huge plus point for those wanting to move away from the traditional Active Directory.

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.

I've used the solution for two months.

Collections offer you the ability to run concurrent tasks and logically group your migrations.

They have an excellent and attentive support team!

Positive

We did not previously use a different solution.

The setup is super straightforward. You can set up your accounts in each tenant and simply sign in.

You have to apply some thought to splitting your migration workloads into collections to concurrently run tasks and be optimal with the Microsoft limitations/throttling.

We implemented the solution in-house, leaning heavily on the ODM-publicized documentation.

We looked into various other options, including:

• Avepoint
• Bit-titan
• Sharegate

Each had its own "issues," which meant they didn't quite work for us in their current states.

Most use cases for Quest On Demand Migration are when a customer has an old tenant, and for some reason they have to migrate their data to a new Office 365 tenant.

I'm an independent consultant working with products from Quest, and doing projects with those products for my customers. Certain customers organize their licenses themselves, because they have their own dealer. In some cases, I also organize the license and resell products to the customer.

On Demand Migration is a cloud product, software as a service.

The bottom line is that using On Demand Migration results in less effort for my customers to bring data over or to work with the data at a new location. It's not only less effort but there is less complexity and less cost involved. If they would have to do this type of work manually or build their own solution, that would cost them endless money. Quantifying how much they save by using the solution is very difficult, but building something like this on their own would require spending five or 10 times what they invest for the licenses for the product.

The time savings are similar, on the order of five to 15 times less when using the solution as compared to building one on their own.

The solution is really stable when it comes to mailbox migration and all of the following work very well:

• the mail content 
• the OneDrive for Business content
• migrating all Azure AD objects.

These three parts are really solid.

It's really easy to configure and you don't have to deal with errors. It's migration that I would call "fire-and-forget."

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.

I have been using Quest On Demand Migration for about one and a half years, but I have been working with Quest products for about 15 years.

It's potentially solid. Mailbox and Azure AD object functionality are very solid. It's the Teams stuff, especially, that is not that solid. It has also to do with the interfaces to other manufacturers' products, among other things; it's not that solid and stable at all.

There is also a part called Public Folder which is a pain. You can solve issues with it, as a consultant, behind the scenes, but never show to a customer how painful that is.

It's quite scalable. But the more you have to scale, the bigger the project is, the more you need to automate. One problem with the product is that we, as independent consultants, do not have access to the automation components, which exist, apparently. If I had to do a really large project and automate, I think I would drown in trouble. It would make life complicated and would take more effort. I know from Quest consultants that those automation interfaces are around, but we are not allowed to use them at the moment, unfortunately.

It's scalable for small and mid-size projects, but when it comes to large stuff it could be complicated.

In terms of increasing our usage of the solution, if the projects are around and they are increasing, I would definitely increasingly use it. When you're familiar with something, you aren't interested in using another product.

My experience with Quest technical support has been very good. They are also human beings, so they can't necessarily help with every case, but they really are okay. They are helpful.

In this field, you don't really have many options. There is the SharePoint Migration Tool, which I have used. And it has happened, at times, in the past, that I have used tools from other vendors.

Setting up On Demand Migration is very straightforward. Depending on the customer's environment it usually takes three hours, perhaps half a day.

The implementation strategy always involves talking to the customer to make sure I understand what kind of security setup they have. That's the most important thing to get it working.

I'm not very familiar with other similar solutions because I'm really focused on Quest. But in terms of how long the setup takes, you don't have hundreds of thousands of settings to configure. It's really easy to use.

Sometimes Quest Support is involved in the setup. If the standard procedure does not work, if there are errors I'm not familiar with, then I involve Quest support. In most cases, it's a standard procedure and you don't have to involve anybody. But it does happen.

Its price-to-value ratio is quite okay. It's much better than it was one year ago.

The solution is on the more expensive side, when you compare it not only to BitTitan but to other tools in the cloud market. Of course, you receive things like Quest's support organization. 

Licensing is not really easy. You don't have the option to buy a very small license to just migrate certain stuff. You always get pushed to use enterprise or big licenses, which include things that the customer never uses. I miss granularity on price at times.

I have had hands-on experience with Metalogix, when it comes to SharePoint, and I have done one project with BitTitan.

It's difficult to compare Metalogix with On Demand Migration because they are completely different, including the architecture. BitTitan is quite similar to On Demand Migration in a lot of areas. BitTitan is really its closest competitor.

The big feature that is most spoken about when it comes to On Demand Migration is the ability to migrate Microsoft Teams, SharePoint, and 365 Groups content, and public folders. I use those features, but they are more complicated and not that stable at the moment. Still, they are useful and helpful.

The user-friendliness is okay. In most cases, my customers don't really use the product. They just tell me, "Do it. Use this product," so they cannot say if it's user-friendly or not. The end users almost do not see anything directly in the product.

Anybody who is using the product should have a look at the current limitations. The documentation is very up-to-date, so have a look at what the product is capable of doing and what it's not capable of. Quest is really transparent. 

Compare prices with other vendors' products. Keep in mind that the support from Quest is really good so you should include that when looking at the prices and costs. That's quite important. 

Most importantly—and here is the consultant in me speaking—if you're a Quest customer, don't use it on your own. Get somebody involved who has already used it to help you. It will work much better.