Server Migration

Product Support

Immediately speak to human concerning your migration dilema.

Contact Sales

Talk to Our Sales Humans

Thinking of moving to somewhere nicer than where you are? We are standing by!

Contact Sales
[et_pb_wpt_gravityform gravityform_id=”gf-3″ _builder_version=”4.19.4″ _module_preset=”default” global_colors_info=”{}”][/et_pb_wpt_gravityform]
New to migration?

Please make sure you have the proper details in order prior to your migration to make the process as seemless as possible while avoid data loss.:

Pertinent Information may include:

  • SFTP hostname and IP address
  • Server credentials, including MYSQL database access with login credentials
  • Advanced DNS access
How do I prepare?

Here are specific examples of the information that would be needed for a server migration:

  1. Server configurations: Information such as the server’s operating system, CPU, memory, storage, and network configurations.
  2. Dependencies: Information about any dependent software or services that are required for the applications on the server to function properly, such as database software or web servers.
  3. Applications: Information about the specific applications and services that are running on the server, including their version numbers and any custom configurations.
  4. Network infrastructure: Information about the current network infrastructure, including IP addresses, DNS configurations, and firewall rules.
  5. Authentication and security: Information about the current authentication and security mechanisms in place, such as SSH keys or SSL certificates.
  6. Backup and restore: Information about the current backup and restore procedures and schedules, as well as the location of the backup files.
  7. Data migration: Information about the data that needs to be migrated, such as database dump, file transfer protocol (FTP) or secure file transfer protocol (SFTP) credentials and the destination.
  8. Cloud provider information: if the migration is to a cloud provider like AWS, the necessary information such as access key and secret key, region, VPC and subnet, security groups, IAM roles and policies.
  9. Monitoring: Information about the current monitoring and alerting mechanisms in place and how to configure them on the new server.
  10. Communication plan: Information about how the migration will be communicated to users and stakeholders, and what steps will be taken to minimize disruption during the migration.

It’s important to have all this information well documented and up-to-date to make the migration process as smooth as possible.