FAQ: Migrating from DeployBot to DeployHQ

Welcome to DeployHQ! We're excited to help you transition from DeployBot and experience the enhanced features and reliability of our platform. This article will guide you through the migration process, ensuring a smooth and efficient switch.

Migration Process

We offer flexible migration options to suit your needs:

• Full Account Migration: We can migrate your entire DeployBot account to DeployHQ in one go.
• Individual Repository Migration: For larger accounts with numerous repositories, we highly recommend migrating in batches. This allows for thorough verification at each stage and minimizes potential disruption.

Key Considerations:

• Project Location: By default, new projects created during the migration will be located in our UK infrastructure zone.
• Automatic Migration: The majority of your resources, such as repository links, server configurations, and deployment scripts, will be migrated automatically.
• Manual Configuration: Depending on the complexity of your DeployBot setup, some manual configuration may be necessary after the migration. We'll highlight these areas below.

Pre-Migration Checklist

Before we begin the migration, please ensure the following:

• DeployHQ Account: You should have an active DeployHQ account. You can easily sign up for a trial if you haven't already.
• Billing: During the migration process, you will only be billed for your active DeployBot account. Once the migration is complete and confirmed, you can cancel your DeployBot subscription, and your DeployHQ account will become your active billing account.

Post-Migration Checklist

Once the initial migration is complete, it's crucial to verify everything is working correctly. Please follow these steps:

1- Verify Migration:

• Navigate to the specific project view in DeployHQ.
• Go to Settings.
• Click the Run Tests button. This will check the connection to your repository and your configured servers.
• Important: Please confirm with our support team once you have successfully run the tests and verified the connections. If you are migrating in batches, we will proceed with the next batch upon your confirmation.

2- Run a Deployment: DeployHQ does not retain historical deployment data from DeployBot. To ensure your deployment process is functioning as expected, you have two options:

• Full Deployment: Initiate a full deployment to all your configured servers as outlined in our Starting a Deployment. This is the recommended approach for a clean and reliable start on DeployHQ.
• Incremental Deployment (Use with Caution): You can attempt an incremental deployment. However, please be aware that this might not include all the commits deployed previously on DeployBot, potentially leading to inconsistencies. You can find more information about incremental deployments here.

3- Backup Plan: Rest assured, nothing will be altered within your DeployBot account during the migration. If any issues arise on DeployHQ, your fallback plan is to simply run your deployments again using your existing DeployBot setup.

4- Finish Migration: Once you have thoroughly tested and confirmed that everything is working as expected on DeployHQ, you can safely cancel your DeployBot subscription. You will then be invoiced solely by DeployHQ for your active account.

Points Not Covered by Automatic Migration

While we strive for a seamless transition, certain configurations require manual intervention:

• Build Pipeline Configuration:

  • The commands defined within your DeployBot Build Pipeline will be migrated to DeployHQ.
  • However, the runtime environment configuration (e.g., Node.js version, PHP version) will need to be manually set up within your DeployHQ project settings.
  • Alternatively, for project-specific or dynamic runtime configurations, you can utilize a .deploybuild.yaml file in your repository. You can find more details about this here.

• Server Firewall Settings:

  • If your servers have firewall rules in place, you may need to update them to whitelist the DeployHQ IP addresses. This is essential for DeployHQ to successfully connect to your servers. You can find a list of our IP addresses here. If the connectivity tests fail, this is a likely area to investigate.

• Configuration Files:

  • Any custom configuration files you were utilizing within DeployBot will need to be manually migrated to your DeployHQ environment. This typically involves copying and pasting the file contents to the appropriate locations on your servers.

• Integrations:

  • Integrations you had configured in DeployBot (e.g., Slack notifications, POST Requests, Sentry error tracking) will need to be reconfigured within your DeployHQ account. Please refer to our integration documentation for specific setup instructions for each service here.

We are here to assist you throughout this migration process. If you encounter any questions or require further assistance, please do not hesitate to reach out to our dedicated support team. We're committed to making your transition to DeployHQ a success!