On Demand Migration Reviews

I have actually two tenants in O365, and I have migrated user mailbox, OneDrive, SharePoint, Teams chat, and Teams channels—all perfectly. Overall, it's a very good tool, and if I require another migration in the future, I will definitely go with this tool only.

It would be great if Quest could include features for different tenant migration such as Google Workspace to O365 or O365 to Google Workspace.

For O365 to O365, it's a very good and easy tool, so I can recommend anyone using O365 to O365 tenant migration to go with On Demand Migration.

Overall, I find it to be a very good tool for O365 to O365 tenant migration, with a very easy and user-friendly interface.

There are specific features that I find the most valuable in it.

The user-friendly interface of On Demand Migration in navigating complex migration tasks is very easy, making it suitable even for first-time users who can do quick migration with this tool.

As of now, I have not observed any issue that could be enhanced in this tool.

I have been working with On Demand Migration for about six months.

I'm not certain about the stability and scalability aspect; I have to explore that.

I'm not certain about the stability and scalability aspect; I have to explore that.

The initial setup process was good, and Quest support was helpful during the first tenant integration. I faced a little challenge, but the support team guided me, and the documentation also helped me.

I rate the tech support of Quest as excellent, as they reach me whenever I raise a concern over a ticket, getting it resolved on time.

Positive

I have worked on BitTitan in my earlier organization, which is also good for Google Workspace to O365 migration.

The initial setup process was good, and Quest support was helpful during the first tenant integration. I faced a little challenge, but the support team guided me, and the documentation also helped me.

I don't have knowledge about the pricing part since my boss from directly USA is handling that.

I believe Quest can do Google Workspace to O365 migration, but I'm not certain about that.

I think Quest only features support O365 to O365 tenant migration, while BitTitan was used for my previous organization's migration from Google Workspace to O365.

I'm currently working with On Demand Migration solution from Quest.

I am providing feedback regarding my experience with On Demand Migration.

I have used automated scheduling in On Demand Migration.

I can run immediate migration or schedule it as per my convenience, but I have used the run immediately option because I needed it on an urgent basis.

The effectiveness of On Demand Migration detailed reporting in managing migration progress is quite good, as there is a report option where I can see what migration got successfully completed, which failed, and even the problem ID and event ID, allowing me to troubleshoot easily on the demand portal.

I have not explored the data filtering options.

I have not explored data filtering for filtering the data.

In terms of data security, we are using independent DLP for data protection in our organization.

I have not explored features such as AI functionality or additional security aspects, as I have explored only On Demand Migration for mailbox, Teams chat, Teams channel, and OneDrive.

For O365 to O365, it's a very good and easy tool, so I can recommend anyone using O365 to O365 tenant migration to go with On Demand Migration.

My overall rating for this product is 9 out of 10.

We move M365 workloads. We migrate Teams chats. We migrate SharePoint data. We migrate OneDrive data, and we migrate people's mail.

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.

You can batch up large groups. You can tell it to move everything for 200 people, and then it just goes. Once you get things set and configured, it is pretty easy. I can hand it off to people more junior to me who are less trained on the product, and they can be successful.

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.

I have been using their products on and off for 10 to 15 years. I have been using Quest On Demand for two years. It was six months after it started existing. It is a very new product for them.

It has not slowed us down. It happens every now and then. Most of it is throttling on the tenant or the customer side. A couple of times, I have seen some announcements of instability or problems, but fortunately, we were not doing migrations at that time. Coincidently, just an hour ago, they communicated that they are having stability problems with SharePoint migrations. They just sent out a worldwide announcement, but we are not doing SharePoint migrations, so I am not too worried about that. For mailboxes and everything else, it is pretty cool. It works very well.

We do not do tens of thousands, but I am confident if we needed to, we could do it. We are in the low thousands. I am comfortable with it. I see everything I would expect to see.

They are very responsive. Whether I open a case through support@quest.com or click on Generate Case in the tool, I get somebody who owns the case within minutes. Before I open a case, they recommend articles that fix the problem, so I do not even need to open a case. It is pretty good. I have also got a connection through our partner. I have never had service problems, but if I did, I know I would have the support I need.

I am using their regular support. Premier support would be something for which you need to pay, and I do not think any of my customers pay for that. They just buy regular licenses.

I would rate their support a nine out of ten. They can always be slightly better, but I do not know what they can do better.

Positive

I tried to use another solution once, but I could not even get it to authorize, so I gave up. It was surprising. I have just used other Quest products that provided a similar service, but they are all end-of-life products. They were on-premises products. Other than scripting around it, I have not come across other products.

I do not use other solutions from Quest for auditing, recovery, group management, or license management. I am not on the infrastructure side. I do more security, but I know that other parts of my company do use other Quest products.

I have not used Microsoft native migration tools. I know they have got some things, but they are not viable at this point. 

The deployment is pretty easy. We have a more difficult time getting the customers to provide credentials. Quest requires certain privileges, and sometimes, it is just a matter of explaining to the customer why they have to give these privileges to the product. It is a strict requirement of the API from Microsoft. It has nothing to do with Quest. It just requires some education. There are pretty good guides from Quest explaining the security model.

For us, the migration environment is 50/50. Sometimes, we have to do AD migrations, which require the on-premise agent for AD sync, and sometimes, we just do the SaaS. We only do O365, so it is 50/50. We have on-premises and cloud migrations.

We are an integrator. We are consultants. We do it all on behalf of clients.

For deployment, you can have one person if that person knows what he or she is doing. We usually have two people for deployment and training. You have four eyes, and you can prevent mistakes.

It is more than fair for what you get.

We did not evaluate other options. We have got a partnership with them. The pricing is very transparent. I know who my partner manager is. I know some of the sales guys. I can get quotes and I can buy directly from the website, but that is not the only way it would work better. Sometimes, we need to talk to the sales guys. We are getting closer and closer to them, so it is getting easier and easier to turn things around.

My advice to new users would be to be patient. In the training material, one of the very first slides says to be patient. The price for SaaS is that some aspects of it are slower than the on-premises solution. In the on-premises solution, the Quest server is sitting right next to the infrastructure servers, so you can measure things in milliseconds or in seconds. If something takes longer than a minute, you are like, "What is going on?" With the SaaS solution, the default cycle time on something like an AD sync is about 15 minutes. The first time, you are not sure if it is ever going to end, but you need to understand what you have got to point it at, and you need to scope things as tightly as you can. After that, be patient. It will do exactly what you tell it to do. Take the training whether or not you think you need it.

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

At the moment, I work for a university as a technical officer. Since two institutions were combined into one , All ofour current systems must be transferred to the new tenant. Microsoft systems, apps,clinet machines and other resources have migrated from one domain to another. For that, we deployed the well-managed Quest on Demand migrating solution, which could accommodate all of your migrating requirements.

Quest transfers all user data, including profiles, apps, and other data pertaining to Microsoft programmes, in the event that a user's data needs to be moved from one tenant to another. The interface of the Quest Migration Tool is user-friendly and effectively manages resources. You have the option to sync and migrate several versions of files across the tenant when transferring OneDrive data, in addition to the ability to move the entire Microsoft Suite data. The metrics of every single user's email content are visible to us. The results from the Quest migration tool are updated and very clear, containing information about users and any problems pertaining to data that was acquired.

You can migrate Teams data and chats. We have migrated all the Teams channels and thier files , but we have not migrated individual chats. I think there is an option to migrate an individual chats but it is limited to only 30 or 90 days prior to the migration.

About 90 percent of our users were satisfied with the migration. About 10 percent could not migrate fully because of few mailbox issues with thier rules & corrupted folders. Due to that mailbox folders did not appear on the new tenant. We need to re-migrate those mailboxes individually.

Quest allows you to customize your migration. For example, you can opt only to migrate Microsoft Teams and the related data or you can migrate all of Office 365. You can also choose to migrate accounts and mailboxes. Sometimes, we don't want to migrate SharePoint data, or we only want to migrate specific users. 

Quest's support for multiple workloads is critical, especially when dealing with large volumes of data. Once you've linked Exchange, Teams, and OneDrive, you can easily implement a policy for the workloads and migrate them all simultaneously. 

The interface is easy to use. They have a project card for each or each tenant. We are merging two universities, so each has its own project card to manage users or devices. The interface is clear, so you aren't confused about where you are going or which department you are migrating to. The project cards are nicely displayed on the interface. The workflows or desktop agents that are interlinked with the policies are given a separate module where you can see all the policies or workflows that you can set up for migrating the environment. 

Their support interface might use some improvements as raising a ticket requires you to go through multiple links. There are instances when there was a downtime and the UI freezes. They notify us in well advance prior to the down time or any issues with a particular region.

We have used Quest On Demand for one year.

I rate Quest support nine out of ten. They always respond in less than 24 hours. We contacted them about an issue with the desktop agent on all the desktops we are trying to migrate from the old tenant. That did not work as expected. It was the only case that took several days to resolve. For all other queries and small issues like agent updates, they have provided a solution within 24 hours.   

They send regular emails about outages and planned maintenance. Quest support is nice, and the notifications are accurate. They keep us informed about every issue and whether the notifications are relevant to us. When you log into the portal, you can immediately see an upcoming service interruption, and plan accordingly for the migration.

Positive

The initial installation went fine, but we had limited time to discuss the project with the Quest team once it started. They gave us an overview of the Quest tool but did not discuss its entire technical side. The deployment went smoothly. All the data has to be migrated at the same time. We started with mailboxes and Teams. Once that was done, we migrated Microsoft groups.

The licensing model is nice. You don't need to assign everyone the same role or subscription for each administrator of each project project card. There are different roles and you can pay for a license based on how many features they can access. I don't know how much it costs, but the licensing is easy to understand. I'm also unsure whether you can get government discounts or if there is some flexibility to negotiate. 

It's critical that Quest is an ISO-certified solution because all the universities are managed by the government. We have strict requirements for data security Demand everything has to be done accordingly. We have an SLA with an IT services provider and they deal with Quest. In 2022, we started looking at Quest on Demand because other universities already use it. That's why our IT consultan recommended it. 

I rate Quest On-Demand Migration nine out of ten. Before implementing Quest, I recommend auditing the configuration of your on-prem and cloud environment. Once you decide to purchase Quest, you should determine what subscriptions or licenses you have in case there are any updates of any features or the agents. You need to be careful when managing it and have a proper deployment team that can communicate to the end user what's going on.

We utilize Quest On Demand Migration for transferring directories, emails, and computer configurations seamlessly between environments. Our primary focus lies in enterprise migrations, with a significant emphasis on Active Directory. These projects typically involve migrations from on-premises to on-premises setups or from on-premises environments to Office 365 on Azure.

The solution seamlessly supports various workloads such as Teams, Exchange, SharePoint, and OneDrive, all within a single platform. It serves as an all-in-one solution that continues to enhance its capabilities.

The solution's overall user-friendliness, particularly its dashboard, stands out as highly intuitive. While it comprises two components with slightly different user interfaces, both are exceptionally easy to navigate and use.

It provides very good security. I've never had an issue where there was any data leak or anything like that.

The benefits we've experienced include the fact that it's a SaaS product, eliminating the need for installation within the customer's environment. This streamlines deployment significantly, making it faster and easier. While certain components may interact with the environment, the overall solution is primarily SaaS-based, which tends to provide customers with a greater sense of reassurance.

It's crucial for us that the solution facilitates the migration of Microsoft Teams, encompassing team chats, as this is the primary mode of communication and collaboration for our customers. During mergers or acquisitions, preserving this capability and retaining historical data is paramount to ensure uninterrupted collaboration for our users.

Concerning Teams, the solution ensures the seamless transfer of all necessary elements to maintain collaboration among our users.

Quest On Demand Migration helped us overcome several challenges, particularly regarding its SaaS nature. Previously, many customers faced difficulties rolling out new servers promptly, which hindered email migration. This posed a significant challenge as project timelines relied on customers preparing everything beforehand. Any delays meant project start delays. However, the fast deployment of this solution proved instrumental in overcoming such obstacles.

The solution's comprehensive nature, encompassing various functionalities within a single platform, has significantly saved time. Previously, managing different workloads might have necessitated multiple engineers. However, with this solution, one engineer can efficiently oversee the entire migration project, covering tasks such as email, Active Directory, computer migration, domain moves, and other operations within the scope of Active Directory.

The success rate of migrations using Quest is determined by the number of support cases IT had to address as a result of the migration, which has been very low, indicating a high level of success. 

The user experience during migration varies depending on the workload. For computer migrations, the process is typically seamless. Users leave for the day, and we migrate their computers overnight. When they return in the morning, they sign in as usual, often unaware of the migration due to its smoothness.

However, migrations involving Teams and SharePoint present a different scenario. During a period of coexistence, where some users operate in the new environment while others remain in the legacy one, there's a noticeable adjustment for end users. While collaboration remains possible, users need to adapt their contact methods. Instead of simply entering a contact name, they must now input the entire email address to reach users in external organizations. This adjustment has presented a learning curve for end users.

The greatest asset is its nature as a SaaS product, offering exceptional scalability and flexibility, which are invaluable to us.

The standout features of the solution that proved most advantageous during our migration process were its robustness and the capability for coexistence within the same product. This was particularly beneficial for our phased migration approach, as it ensured smooth transitions and accommodated our long-term project requirements effectively.

The security features of the solution effectively fulfilled our data protection requirements. Quest prioritizes security, offering a comprehensive security guide that addresses any concerns customers may have. This resource helps clarify how all aspects of security are managed within the tool, reassuring our clients about the safety of their data.

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.

We have been working with it for four years.

In its early stages, like any product, it faced some challenges during development and maturation. However, through iterative improvements and adherence to best practices, the product has become highly stable and reliable. I would rate it ten out of ten.

The size of our clients' businesses varies significantly. The smallest migration I've handled involved seventy users, while the largest migration comprised over two hundred thousand users globally. If I were to rate scalability on a scale of one to ten, I'd give it a ten with Quest. The SQL aspect of the product is managed by Quest, ensuring smooth scalability. However, there may be a threshold, as evidenced by a recent customer with approximately seven thousand users opting for an on-premises solution over ODM. While I'm unsure of the exact limitations, adding new environments to ODM has generally been straightforward compared to deploying server agents for each environment in the on-premises solution.

The support provided is excellent. Response times are typically within the hour, and the support team is highly knowledgeable. They consist of Quest support engineers who possess deep expertise in the product. If necessary, escalations are directed to the development team, who have an intricate understanding of the product and can swiftly resolve issues, including reconfiguring the tool to suit the customer's environment if needed. Overall, they are very responsive and professional, and I would rate them ten out of ten.

We utilize Premier Support within our organization, which grants me access to all resources and ensures rapid responses. Similarly, when our customers contact Quest support, they often report receiving prompt responses as well.

Positive

For the better part of my career, the primary tools I've been working with were Binary Tree and Quest. Recently, Quest acquired Binary Tree, leading to the integration of the two tools into On Demand Migration. This merger effectively combined the strengths of both tools into a single solution. Previously, each tool had its own advantages and disadvantages, but their consolidation has resulted in a highly effective and beneficial solution. My primary focus revolves around On Demand, specifically utilizing Migration Pro for AD, the on-prem solution, as well as Migration Pro for Exchange, and Migration Manager for Notes. The role of these solutions in pre and post-migration success is highly significant. They boast excellent reporting capabilities, which contribute greatly to the overall success of the migration process. Additionally, the Quest engineers' approach involves thorough discovery and planning phases before deploying the tool, ensuring a comprehensive and well-executed migration strategy.

When comparing the workload supported by Quest to Microsoft's native migration tools, there's a notable difference in capabilities. Unlike Microsoft's native tools, Quest's solutions offer superior functionality. With On Demand Migration, multiple workloads can be managed simultaneously within a single platform, providing greater efficiency. While Microsoft's native tools are suitable for smaller migrations, they lack scalability for larger organizations with over seven thousand accounts or users.

The initial setup can be categorized as medium difficulty. While there are a few aspects that are not particularly intuitive, they do not present significant or overly problematic challenges.

The deployment time varies depending on the complexity of the environment. Typically, for a standard environment, it takes approximately three to four hours to configure and deploy once I have a thorough understanding of the customer's expectations, requirements, and overall goals. The deployment team typically comprises a Quest engineer alongside the project team from the customer's side. This usually includes a project manager, an AD admin or an Office 365 admin, and a security admin. Additionally, there is a project manager from our side involved in the process.

Occasionally, upgrades are necessary, although it's uncommon for customers to upgrade amid their migration project unless it spans six months to a year. Typically, we complete the project using the same deployment version.

I find the pricing to be cost-efficient for what you receive with the Quest product. Alongside the product itself, you also gain access to professional services, which include a robust methodology crafted by experienced Quest engineers and professional services architects. Their extensive expertise in migration, accumulated over years of experience, proves invaluable, especially when unforeseen issues arise in complex environments. With a dedicated support team behind them, navigating through challenges becomes quicker and more efficient. Essentially, by investing in a Quest product, you're not just acquiring a migration solution; you're also tapping into a wealth of support, resources, knowledge, and a well-defined methodology to guide your migration planning.

I would highly recommend Quest's migration solution, but it's crucial to conduct a thorough discovery session with someone experienced in migrations. Many of my customers embark on their first migration journey, and while they may have subject matter experts in areas like active directory administration and security, they often lack expertise in migrations. Therefore, organizations need to collaborate with consultants or experts in migrations, even if they don't ultimately choose Quest's tools. It's vital to gain insights from professionals who regularly handle migration projects. Overall, I would rate it nine out of ten.

We have one Microsoft 365 tenancy and three not-for-profit licenses from Microsoft. Microsoft changed the licensing model, so we could only have 300 licenses per tenancy for free, so we have to pay for the other 1200 users. We were running one tenant on behalf of lots of different entities. The tenancy with 1500 people on it, is the Scout County. Within the Scout County, there are eight districts, and then within each district, there are about 20 Scout groups. That's the structure. So we had one tenancy at the county level that we provided for everybody, and we provided support as well. However, under the new licensing from Microsoft, we couldn't do that. It was going to cost us a fortune. So each district has applied for and and now has its own tenancy with its own 300 licenses, which is enough. We then use Quest Demand, to migrate from our county tenancy into eight district's tenancies. 

The benefit to us was that it saved us an awful lot of money in licensing fees by having to do the migration. It allowed us to do a really difficult job quite easily compared to having to do it manually. 

It's completely web-based.

They have a demo version that you can test before you purchase it so you can see that it does what you need before you commit financially.

You can migrate different aspects of the tenancy in a structured way.

The interface is very good. It all makes sense. There's good logging and feedback. 

We only have the most basic license, so we only used it to migrate mailboxes. It does support the migration of Teams chats, etc. We haven't used that part of the product. However, it is good that it is doable.

The ease of use is pretty good. I did need some technical support. It did not work straight out of the box. The support was very good and very quick, so I could do what I needed to do. 

The data security the solution provides for tenant to tenant is good. There is an element of having to trust the solution. However, the conversation with their technical people gave me confidence in the security.

I didn't need to reach out to technical support too much. And the more I worked with the solution, the more I understood it. I barely needed assistance. 

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. 

We've been using the solution since September 2023. 

The solution is very stable. We had no problems. I'd rate the stability ten out of ten. 

Since we are not a company, we are a volunteer organization; it was only used by two users in two different areas. 

The solution seems capable of scaling, although we did not scale ourselves. 

Technical support is excellent. We just used the regular support services. 

Positive

The solution stands out based on its interface, free online option, and responsiveness of the sales and support teams. 

The initial deployment was straightforward. To get Quest up and running, it might have taken about an hour. We have two users using the solution. 

There is no maintenance needed. 

The ROI is difficult to quantify. Using the tool certainly saved hundreds of man-hours of work. Manually, it would take us 2,000 hours to do the process manually, and we were able to do everything in about 50 hours. 

The solution is pretty fairly priced. We got a good deal as we are a charity and got a fairly good rate. 

I'm a Quest customer. 

We do not use any other Quest products. 

I'd recommend the solution to others and do a trial and speak to technical support if you can't get it working straightway. Overall, my experience was positive.

I'd rate the solution nine out of ten. 

We use the product for data migration purposes.

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.

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

It is a scalable platform.

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.

Neutral

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

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

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.

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

We have evaluated BitTitan, ShareGate, and AvePoint.

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.

We are in the process of acquiring additional companies on the market. We will integrate the new IT organizations from those acquisitions. We integrate their internal IT staff to the shared service IT. For those cases, we will migrate the Microsoft 365 tenant. 

We are fast and have a high-quality migration team. 

The most valuable feature is that it enables to see any issues that may come up during the migration. 

We can handle multiple workloads using this since it connects with Microsoft 365. This is another feature we like. We don't know which our acquisitions will be using so it helps with that. It'll help us become more agile. 

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

I have been working with the product for 12 months. 

I rate the tool's stability a ten out of ten. 

I rate Quest On Demand Migration's scalability an eight out of ten. 

I'm quite happy with their support. We ran into a few issues but they got handled. It was mostly miscommunications problems, not software problems.

I would rate their support a nine out of ten. 

Positive

Quest On Demand Migration's deployment for a mid-size migration takes overall ten days to complete. 

We have need two people from our end and one person from our partners who help with the setup. 

Quest does not require maintenance. It's a one-time hit. We buy the license, it takes ten days to set up and that's it. 

By merging the m365 administration, this can be made more efficient and costs can be reduced.

We are fine with the tool's pricing. It's fair.

Microsoft Teams helps our team to collaborate. 

I would say to anybody implementing Quest that it's all about the preparation and communication before you start the migration. You have to be honest and clear about what you expect from the migration.

We work with a partner, Dr. Markus Morawietz. They're a ten out of ten. We work comfortably with them. We are discussing the next steps in going further with our partnership. 

We have no specific points where we are not like-minded with our partner. It's a reliable partnership. He's fast and his team is professional. They answer quickly and we are happy to have them on our side. 

They assisted us throughout the migration and they told us what steps we needed to take on our side. We had never done a migration of this type. This partner helped us initialize this migration. Now we're a little more comfortable so we can do some of the work but they are still there to help us. 

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

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 mostly use the solution for tenant-to-tenant migration of Microsoft 365.

The OneDrive email migrations are pretty solid. The solution supports multiple workloads. It is very important to us. The dashboard is pretty easy to use once we use it once or twice. The data is pretty secure. It uses Microsoft's back end, so it is probably as secure as it can be. It is a pretty robust migration platform.

We realized the benefits of the tool before deploying it. We researched well to find a good tool. It is very important to us that the product supports the migration of Microsoft Teams, including chats, when it comes to user and customer collaboration. Users want to migrate Teams. The product has everything that is needed for our users to collaborate. The success rate of migrations using Quest is pretty good. I only had a couple of issues where I had to open a case.

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.

I have been using the solution for two years.

I have seen stability issues, but it hasn't affected me. The vendor informs us about maintenance windows. I haven't seen any major issues.

The support's pretty good because we're a partner. We resell and implement the tool for our customers. The support team is pretty quick. I had some issues getting support on the weekend. We are using the regular support.

Positive

I have used BitTitan. Quest is a more complete solution for tenant-to-tenant migration. I have also used other migration tools like Active Directory Migration.

The product is cloud-based. The deployment was straightforward. I had a coworker who had deployed with it before. I could set it up pretty quickly. We are integrators. I usually do the deployment myself. Sometimes, I have a team of a couple of people, depending on what we're doing. Quest does not require any maintenance after the migration.

The tool does what it needs to do. It provides a lot more hands-on migration work. The return on investment is the speed and getting it done better and faster.

The pricing is in line with other products.

I haven't used the newer Microsoft migration tools. Microsoft tools get us close enough, but not really all the way. People who want to buy the solution should know how to migrate. It is not an end-user product. Overall, I rate the product an eight 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.