Why migrate to Gcore Cloud?
Easy data migration
Move your IT infrastructure to the cloud through a few simple steps, either manually or with the assistance of migration services.
Secure cloud
Gcore is GDPR, PCI DSS, and ISO/IEC 27001 compliant. Our data centers are Tier III & Tier IV certified.
API and Terraform automation
Gcore is GDPR, PCI DSS, and ISO/IEC 27001 compliant. Our data centers are Tier III & Tier IV certified.
Flexibility and scalability
Scale your cloud resources up and down as needed with a pay-as-you-go model.
Global presence
Choose from over 50+ locations in Europe, Asia, the US, and Latin America.
Integrated services
Use a single cloud solution with next-gen CDN, Streaming Platform, Object Storage, and other services.
Architecture examples of migration
Here we present three common migration schemes: image replication, data replication, and direct connection. However, there are more options for migration architectures than these. We can implement any custom architecture to meet your needs.
Image replication
Image replication is the most common scenario, where you move your infrastructure using images that you prepare in advance. Here’s how it works:
- Prepare images of your VMs or bare-metal servers that are located on-premises or in another cloud.
- Load the images into our object storage or an equivalent service.
- Create VMs or bare metal servers from these images in our Cloud.
- Switch traffic from the old infrastructure to the new.
Data replication
This scenario is appropriate when any interruption of service is unacceptable. It is also the most automated scenario of the three. Here is how it’s executed:
- Install a replication agent on your source machine.
- Install a replication agent on a receiver machine in our Cloud and set the connection between two infrastructures.
- Start the data replication from the source machine to the receiver. This happens in the live background mode.
- Switch traffic from the old infrastructure to the new.
Direct connection
This scheme is suitable for migration and backup of your infrastructure. Here’s how it works:
- Configure a direct connection between your infrastructure and the Gcore Cloud.
- Duplicate all the data to the new Cloud and synchronize two infrastructures.
- Switch traffic from the old infrastructure to the new one if you want to migrate completely. Or, use the Gcore Cloud for cases like disaster recovery.
Common steps to migrate to Cloud
Planning
Select the migration scenario to the Gcore Cloud. Plan the migration process in detail.
Preparation
Prepare your new infrastructure in the Gcore Cloud. Deploy the VMs, bare metal instances, and other services as needed.
Data replication
Copy business applications, metadata, and server settings to the new infrastructure.
Testing
Test a "light" version of your system in the Cloud to measure all important technical and business metrics.
Piloting
Perform piloting for a few weeks to understand how the system behaves.
Final changeover
Move to the new infrastructure in a short, predictable timeframe and with a plan for future maintenance.
Cloud migration checklist
To learn more about important aspects of migrating to the cloud, check out our Cloud migration checklist. This step-by-step guide will help you plan your migration thoroughly and execute it smoothly. The guide also contains some practical migration scenarios that may be useful for you.
Success stories
The Gcore solution allows us to quickly launch our services. Tests have shown that any of the customers can receive the necessary information instantly, and the infrastructure itself is available in all geographical jurisdictions where we operate. Each country has restrictions on the work with personal data, and, as a rule, we must store it within a specific country. Gcore makes it easy for us to solve this problem. That’s why we chose this company as our cloud partner.
Nukri Basharuli
Aggregion
For security and scalability reasons, we decided right away that we wanted to entrust the delivery of our customers’ videos to a reputable CDN provider. We settled on the infrastructure of Gcore and don’t regret our choice.
Nathan Ihlenfeldt
Stage Audio Works
With Gcore, we have managed to standardise our global expansion and cover regions where it would have been very difficult to gain a foothold on our own. The cloud provider has the expertise we need in low latency and high server performance. In addition, it knows the needs of a game hoster in expanding our online business worldwide and has the necessary structures for on-site implementation.
Marcel Bößendörfer
Nitrado
We are trusted
Frequently Asked Questions
Cloud migration involves moving an organization’s IT infrastructure, including servers, storage, and networking, to a cloud computing platform—like the Gcore Cloud. This can mean moving the entire infrastructure or migrating only a subset of workloads or applications.
More and more companies are migrating to the cloud because they see the obvious associated business benefits, such as flexibility and ease of infrastructure management, a convenient payment plan that helps them save money, and the ability to provision infrastructure for any task in minutes.
The main advantages of migrating infrastructure to the cloud include:
- Scalability: Cloud computing resources can easily scale to meet changing needs, mitigating concerns about overprovisioning or underprovisioning IT resources for organizations.
- Performance: The cloud provides performance comparable to traditional on-premises IT infrastructure. It is especially useful for applications that require high availability or massive processing power.
- Cost savings: The cloud can be more cost-effective than traditional on-premises IT infrastructure, especially for organizations that need to scale resources quickly.
- Security: Cloud computing providers ensure a high level of security for their infrastructure and data centers. They also often possess more expertise in security than an average organization.
It depends on your project and goals. You can use our Cloud migration checklist to learn more about common migration strategies and choose the most appropriate one. You can also ask our solutions architects team to consult with you and help you choose the better strategy; contact us to discuss your project.
Yes. When deploying services in the cloud, there are two common approaches:
- If you want to migrate your infrastructure and applications to the cloud as is, you can use “lift and shift.” This works well for predominantly monolithic applications.
- If you want to take advantage of the scalability, elasticity, and distributed nature of cloud infrastructure, you can apply a cloud-native approach. In this case, you re-architect your monolithic application using a microservices architecture. This divides the application into small, separate services that interact through an API. The cloud-native approach is more complex than “lift and shift,” but it is advantageous for modern cloud applications.
You will be charged on a pay-as-you-go basis only for the cloud services (e.g., virtual machines, S3 storage, load balancers) you actually use. Note that if you use Gcore VMs, you don’t pay for egress traffic; you only pay for it when using Bare Metal.
Yes. We protect our customers’ services and data on multiple levels:
Physical security:
- Compliance with GDPR, PCI DSS, and ISO/IEC 27001
- Tier III and Tier IV certified data centers
Infrastructure security:
- Virtual Private Cloud with secure access to virtual instances. The Gcore team doesn’t have access to your VM operating system or data
- Intel SGX instances support to protect your sensitive data better
Network security:
- L3, L4, and L7 DDoS protection with real-time alerts
- Web Application Firewall (WAF)
Not that some security features, such as advanced DDoS protection or WAF, may not be necessary depending on your particular business use.