Try our new research platform with insights from 80,000+ expert users
Habib Bilfaqi - PeerSpot reviewer
Technology Evangelist at SNAH Technologies Inc.
Real User
Top 10Leaderboard
Has an easy data migration process, but they could provide on-premises to online exchange components
Pros and Cons
  • "The most valuable features of Quest On Demand Migration have been the M365 migration and Active Directory (AD) migration components."
  • "They could provide on-premises to online exchange components for the platform. It would be highly valuable."

What is our primary use case?

We use the product for data migration purposes.

What is most valuable?

The most valuable features of Quest On Demand Migration have been the M365 migration and Active Directory (AD) migration components.

What needs improvement?

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

For how long have I used the solution?

We have been using Quest On Demand Migration for three and a half years.

Buyer's Guide
Quest On Demand Migration
November 2024
Learn what your peers think about Quest On Demand Migration. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.

What do I think about the scalability of the solution?

It is a scalable platform.

How are customer service and support?

We contacted the technical support team many times. Sometimes, they provide good services. However, they usually take too long to resolve the issues. We can even figure out the solution with the help of our internal team within the same period.

How would you rate customer service and support?

Neutral

How was the initial setup?

The complexity of the initial setup varies depending on the specific project requirements.

What about the implementation team?

We take assistance from a third-party vendor for configuration and setup.

What was our ROI?

If we use the product at full capacity, it will generate around 80% ROI for us. The other 20% would be lost due to drawbacks related to Teams and SharePoint migrations. In some cases, the return on investment is worth it.

What's my experience with pricing, setup cost, and licensing?

The product had reasonable pricing until the beginning of this year. Now, the price is increased by 20%.

Which other solutions did I evaluate?

We have evaluated BitTitan, ShareGate, and AvePoint.

What other advice do I have?

The platform provides a single console to support multiple workstreams or workloads. However, it lags in SharePoint and Teams compared to other competitors. In terms of dashboard functionality and ease of use, I rate it a nine out of ten.

It is crucial to prefer ISO certification for every migration. It benefits in ease of data migration by managing issues from both sides. It is very important to utilize Quest for user and customer collaboration. However, it sometimes only migrates from one chart to another while using Teams.

Quest On Demand Migration needs to catch up in SharePoint and Teams migration speed and customization capabilities compared to ShareGate. 

The success rate of the migrations is about 60%, as we encountered while working with Teams and SharePoint.

I advise others to ensure proper licensing type for migration, understand the deployment methods, and configure Active Directory before purchasing the product.

I rate it a seven out of ten.

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: Partner
Flag as inappropriate
PeerSpot user
reviewer1929072 - PeerSpot reviewer
Cloud Infrastructure Engineer at SLR Consulting Ltd
User
Easy to use, a "one-stop shop" for tenant-to-tenant migration, and simple to implement
Pros and Cons
  • "We can easily and simply work out the cost for any migration work that is required with the licensing model."
  • "They should introduce a module for migrating power automation for users."

What is our primary use case?

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.

How has it helped my organization?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

I've used the solution for two months.

What do I think about the scalability of the solution?

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

How are customer service and support?

They have an excellent and attentive support team!

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

We did not previously use a different solution.

How was the initial setup?

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.

What about the implementation team?

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

Which other solutions did I evaluate?

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.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
rhrempel - PeerSpot reviewer
rhrempelPrincipal Product Manager at Quest Software
MSP

Hi,


Thanks for the positive feedback on the User Guide. I'm calling this out because we've put a big focus on keeping it up-to-date and user focused. We also provide a Strategy and Best Practices Guide.


Let me respond to some of the improvements you recommended.


1. Make the dashboard editable in the browser. This a very compelling idea. I can see other users wanting this, too.


2. A module for migrating power automation for users. Is this referring to using PowerShell rather than the UI? If so, we can discuss what you would like to see in PowerShell capability.


3. Better handling of the various M365 group states. We separated this handling for Teams; but still need to do this for Groups: SharePoint and Planner.


4. Error handling resolution. We would like to separate our current error messages into more than one column and add more filtering and sorting capability. We also plan to add error reporting for content migration issues only. That is, identify the content that failed to migrate and why.


5. Display of migrate chats. We are limited in how we can display migrated chats. First, we cannot impersonate users. Thus, we use an admin account to create private chat messages. Second, we recommend merging messages on the target because it is faster than not doing so. Third, we make it possible to migrate the last 30 days of messages and archive the remainder. We think these are reasonable compromises in the scope of the limitations we face and the tight timeline for migration. But let us know if you see room for more improvement.


6. Apply some thought to splitting your migration workloads into collections. We have some plans to improve how this works. We want to make it easier for users to migrate without being concerned about scheduling tasks.


We are always open to feedback to improve our products.


All the best,


Randy

Buyer's Guide
Quest On Demand Migration
November 2024
Learn what your peers think about Quest On Demand Migration. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.
Independent Consultant at Krebs IT-Services
Consultant
Saves time and reduces complexity when migrating data, but some features are not that stable
Pros and Cons
  • "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, and migrating all Azure AD objects."
  • "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."

What is our primary use case?

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.

How has it helped my organization?

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.

What is most valuable?

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."

What needs improvement?

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.

For how long have I used the solution?

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.

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

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.

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

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.

What about the implementation team?

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.

What was our ROI?

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

What's my experience with pricing, setup cost, and licensing?

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.

Which other solutions did I evaluate?

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.

What other advice do I have?

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.

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: Partner/Reseller.
PeerSpot user
rhrempel - PeerSpot reviewer
rhrempelPrincipal Product Manager at Quest Software
MSP

Hi Reto.


It was nice to finally meet you at Quest TEC in Atlanta this September. I recall that we met and discussed what needed improvement based on this review last year.


1. We separated the content migration in the Teams UI so that users could migrate different parts of a Team separately.


2. We added more details on the item counts for Teams content in the UI.


3. We continued to add to the scope of what ODM SharePoint supports.


4. We added more details on what is and is not supported to our user documentation.


5. Regarding automation interfaces, I recall that we discussed the use of PowerShell to as an alternative to the ODM UI.


And you provided an update after TEC this year. For anybody else who this could be helpful to, here’s what we discussed:


1. Request to migrate Mail-Contacts.


2. Migration of SharePoint subsites as part of Teams migrations


3. Adding collections to Teams chat migration


4. Continued priority on migration performance


5. Using Desktop Update Agent to simplify client reconfiguration


We are always open to feedback to improve our products.


All the best,


Randy