I use this project because I work for an IT company in France and we perform a lot of migration work, and we often use OpenText Migrate. We perform a lot of migration of Microsoft Active Directory, of Microsoft Windows NT domain earlier, and a lot of migration with Exchange Server, and migration tenant to tenant now. I do some migration from Google Workspace to Microsoft 365 or similar projects. So, a lot of infrastructure and messaging infrastructure product migration work is involved.
General Manager at PanExcel IT Consulting and Services
Real User
Oct 22, 2024
We initially used Carbonite for cloud migration, specifically for moving data from one cloud to another. We moved from a RACS-based environment to VMware.
Enterprise Architect at a tech services company with 1,001-5,000 employees
Real User
Mar 23, 2021
The primary use is to monitor any type of migration. For example, if you have one landscape on the VML virtualization platform and the second on Hyper-V, then two different virtual environments are present. In this instance, you cannot use native tools for the migration in case an application path is present. You have to use a third-party tool, such as Carbonite Migrate, that can do the migration from one platform to another platform when you switch the setting. When B2B migration is also not possible through native tools, this tool can be used. In P2P migration, if you have a customer who uses the physical infrastructure, prior to migration you will need to create a similar environment in the other data center to which the data will migrate. Carbonite Migrate can be used for this purpose as well. We can then take an image of the current system and run it onto another system as a test. There are multiple use cases for this tool.
Solutions Architect at a tech services company with 10,001+ employees
Real User
Aug 9, 2020
Technically, we use this product in regards to cloud data infrastructure migration; however, these are all things that are driven by the customer. If they are interested in a solution, we make suggestions and provide recommendations. When it comes to cloud data infrastructure challenges, mostly we are attempting to achieve cloud migration from an infra point of view. That's where tools like Carbonite Migrate and RiverMeadow come in handy. We use Carbonite Migrate to migrate our customer's data. The migration of data refers to application data and application infrastructure resources — how many Physical/Virtual servers and CPUs, VM’s, Containers, etc. We also focus on Applications data server dependency. In other words, if your application has 10 different servers, then 10 individual servers need to be migrated Afterward, Carbonite Migrate creates an original migration plan for the new environment and lays out the steps to accomplish this. As data migration can be risky, often it creates an automated pathway in order to reduce migration risk. Let's say a customer has a data problem, we then use these tools to gain access to the customer's environment, run an assessment and come up with the best migration route, identify the blockers and in return, they can create a migration plan. That's how we use this solution.
OpenText Migrate streamlines data migration, ensuring a seamless transition across environments. It's designed for enterprises aiming for operational efficiency and reliable data transfer, eliminating downtime and data loss concerns during migration projects.OpenText Migrate supports high-volume data transfers with minimal disruption. It's widely used by enterprises seeking secure and efficient data migration. Its flexibility in handling complex migration scenarios makes it a preferred choice...
I use this project because I work for an IT company in France and we perform a lot of migration work, and we often use OpenText Migrate. We perform a lot of migration of Microsoft Active Directory, of Microsoft Windows NT domain earlier, and a lot of migration with Exchange Server, and migration tenant to tenant now. I do some migration from Google Workspace to Microsoft 365 or similar projects. So, a lot of infrastructure and messaging infrastructure product migration work is involved.
We initially used Carbonite for cloud migration, specifically for moving data from one cloud to another. We moved from a RACS-based environment to VMware.
The primary use is to monitor any type of migration. For example, if you have one landscape on the VML virtualization platform and the second on Hyper-V, then two different virtual environments are present. In this instance, you cannot use native tools for the migration in case an application path is present. You have to use a third-party tool, such as Carbonite Migrate, that can do the migration from one platform to another platform when you switch the setting. When B2B migration is also not possible through native tools, this tool can be used. In P2P migration, if you have a customer who uses the physical infrastructure, prior to migration you will need to create a similar environment in the other data center to which the data will migrate. Carbonite Migrate can be used for this purpose as well. We can then take an image of the current system and run it onto another system as a test. There are multiple use cases for this tool.
Technically, we use this product in regards to cloud data infrastructure migration; however, these are all things that are driven by the customer. If they are interested in a solution, we make suggestions and provide recommendations. When it comes to cloud data infrastructure challenges, mostly we are attempting to achieve cloud migration from an infra point of view. That's where tools like Carbonite Migrate and RiverMeadow come in handy. We use Carbonite Migrate to migrate our customer's data. The migration of data refers to application data and application infrastructure resources — how many Physical/Virtual servers and CPUs, VM’s, Containers, etc. We also focus on Applications data server dependency. In other words, if your application has 10 different servers, then 10 individual servers need to be migrated Afterward, Carbonite Migrate creates an original migration plan for the new environment and lays out the steps to accomplish this. As data migration can be risky, often it creates an automated pathway in order to reduce migration risk. Let's say a customer has a data problem, we then use these tools to gain access to the customer's environment, run an assessment and come up with the best migration route, identify the blockers and in return, they can create a migration plan. That's how we use this solution.