[DeployHQ](https://www.deployhq.com) is a powerful and reliable platform supporting passionate developers in automating their deployments smoothly and without hitches. With automated code deployment, [DeployHQ](https://www.deployhq.com) helps creators forget about repetitive manual tasks and allows them to focus on what truly matters: writing code. If your team is looking to change deployment providers, migrating to a new service with new and unknown deployment tools, bells, and whistles might look daunting. Fortunately, this guide is here to help you navigate the deployment migration process step-by-step. If you are ready to migrate to [DeployHQ](https://www.deployhq.com) and leave manual deployments behind, this guide is for you. ### Why Migrate to DeployHQ? [DeployHQ](https://www.deployhq.com) is a deployment service that automates boring tasks so that you can focus on creating. Its modern and intuitive UI, a far cry from old and clunkier tools, allows you to find what you need with ease and handle all of your projects comfortably from a single comprehensive dashboard. It offers a guided configuration for faster setup and a deck of deployment tools that can get your project up and running in minutes. And if you have code spread across several services, no problem: [DeployHQ](https://www.deployhq.com) supports popular stacks and integrates easily with the likes of GitHub, GitLab, and Bitbucket. [DeployHQ](https://www.deployhq.com) specializes in zero-downtime deployments, rollbacks, and flexible pipelines that adapt to your project, not the other way around. ![Automatic code deployment pipeline connecting a Git repository to multiple servers](https://blog.deployhq.com/attachment/a8163e12-8e58-4180-a336-ccf33ba67f59/img_s4s244a2rzjn.png) ### Migrating from DeployBot to DeployHQ [As of last year](https://www.deployhq.com/blog/exciting-news-deployhq-merges-with-deploybot), DeployBot and [DeployHQ](https://www.deployhq.com) are the same platform under one roof! As DeployBot is being fully merged into [DeployHQ](https://www.deployhq.com), migrating is in your best interest. Here is why: - Official migration path and long-term support: [DeployHQ](https://www.deployhq.com) is now the active product being developed and supported. All new development is happening in [DeployHQ](https://www.deployhq.com) only! - Upgraded UI/UX: [DeployHQ](https://www.deployhq.com) offers a sleeker and more intuitive interface with improved navigation, clearer logs, and an overall better development experience for managing multiple environments and teams. - New features: [DeployHQ](https://www.deployhq.com) has functional advantages over legacy DeployBot, including: - Reusable [pipelines](https://www.deployhq.com/blog/build-pipelines-in-deployhq-streamline-your-deployment-workflow) for multi-step deployment setups - Agent-based, more secure deployments from private networks - Custom notifications - Improved role-based permissions and audit trails - Improved CI/CD workflow integrations: [DeployHQ](https://www.deployhq.com) integrates with GitHub, GitLab, Bitbucket, and custom Git repositories. And much more. To migrate from DeployBot or any other service to [DeployHQ](https://www.deployhq.com) step-by-step and in no time, follow our handy guide in the next section. #### Case Study: A Smooth Switch from DeployBot to DeployHQ Ponderosa, a Leeds-based creative agency, transitioned from DeployBot to [DeployHQ](https://www.deployhq.com) with minimal disruption. They enjoyed faster deployments and greatly appreciated the clearer logs and improved UI during the move. [Read their story here.](https://www.deployhq.com/blog/case-study-a-smooth-switch-from-deploybot-to-deployhq) ### Migrating to DeployHQ: a User’s Guide Many teams currently use platforms like GitHub Actions, Jenkins, FTP scripts, Capistrano, or manual deployment processes. Migrating to a dedicated deployment service like [DeployHQ](https://www.deployhq.com) can boost your team’s deployment efficiency through automated deployment and free your development processes of the headaches of development operations right out of the box. Here is how to migrate to [DeployHQ](https://www.deployhq.com) in a few straightforward steps and get your project running in minutes: #### 1. Audit your current deployment workflow The first step should entail a thorough review of your existing deployment processes, regardless of whether they are manual scripts, FTP uploads, Jenkins jobs, GitHub Actions workflows, or others. You should identify key components such as repositories, deployment triggers, servers, and any build or post-deployment scripts. This audit ensures you know exactly what needs to be replicated in [DeployHQ](https://www.deployhq.com). #### 2. Set up your project and connect your repository If you haven’t yet, [create an account](https://www.deployhq.com/signup) on [DeployHQ](https://www.deployhq.com). Then create a new project and link it to your code repository (GitHub, GitLab, Bitbucket). Done! With this step, you can replace manual code transfers with hands-off integration, allowing [DeployHQ](https://www.deployhq.com) to monitor your repository and deploy code automatically or on demand, depending on your preferences. #### 3. Configure deployment environments and servers It’s now time for fine-tuning. Define your deployment environments (like Staging, Production, or QA) in [DeployHQ](https://www.deployhq.com), specifying branches or tags to deploy from. [Add your target servers](https://www.deployhq.com/support/servers/adding-a-server) by configuring connection credentials such as SSH keys or API tokens. [DeployHQ](https://www.deployhq.com) supports a number of server protocols, from DigitalOcean Droplets to AWS S3. #### 4. Migrate and adapt deployment scripts While deployment history cannot be migrated, you can manually transfer your existing deployment scripts into DeployHQ’s pre- and post-deployment hooks to recreate your workflows. [DeployHQ](https://www.deployhq.com) supports flexible scripting to adapt most deployment processes within the UI. #### 5. Test, automate, and go live Perform test deployments to verify everything is set up correctly. Once you are confident everything is working as it should, activate automatic deployment triggers such as deploying on every push to a branch or manual deploys via the dashboard. Finally, sunset your previous manual or tool-based deployment processes to fully transition to [DeployHQ](https://www.deployhq.com). Now that you are all set, it’s time for your first deployment: check out our [deployment setup guide](https://www.deployhq.com/blog/how-to-setup-your-first-deployment-with-deployhq). ### Best Practices for a Smooth Migration To best transition from your old service to [DeployHQ](https://www.deployhq.com), there are a few things to keep in mind. - Thoroughly audit your current setup It might be tempting to skip the first step of your migration by bypassing the auditing process, but please don’t do it! Before starting, review your existing deployment workflows, scripts, and server configurations, document triggers, environments, notifications, and any custom build or post-deployment steps. Failing to do so may result in missed configurations, broken deployments, or incomplete replication of your previous workflow in [DeployHQ](https://www.deployhq.com). - Backup existing configurations and scripts Backups are a critical step, so that you don’t risk losing something important along the way. Export or copy your deployment scripts, environment variables, and settings from your old service. This will help you accurately recreate your workflows once you are settled with [DeployHQ](https://www.deployhq.com). - Start small to get your feet wet When building your first project, it’s a good idea to test in a staging environment: Begin by migrating and testing one project or environment at a time, ideally a staging or QA environment. Validate the deployment flow before moving on to production to minimize disruption. - Take advantage of DeployHQ’s documentation and support Use DeployHQ’s guides, API docs, and support channels to map your current deployment processes to the new platform. And if you encounter edge cases or complex workflows, you can always reach out. ### Wrap-up: Your Deployment Workflow Deserves Better If you’ve been juggling scripts, outdated dashboards, or fragile workflows, it’s time to upgrade. [DeployHQ](https://www.deployhq.com) gives you a cleaner and more reliable way to ship code without the guesswork or manual steps. Whether you’re moving over from DeployBot or ditching DIY deployments, the switch is smoother than you think (and your future self will thank you). Ready to make the move? [Check out our pricing](https://www.deployhq.com/pricing) and start your migration. ### FAQs #### How do I migrate from DeployBot to DeployHQ without downtime? Migrating from DeployBot to [DeployHQ](https://www.deployhq.com) can be done with zero downtime. You can recreate your deployment configuration in [DeployHQ](https://www.deployhq.com) while keeping your existing tool active. Once tested, simply switch over your deployment triggers to [DeployHQ](https://www.deployhq.com) for a hassle-free transition. #### Will my existing deployment scripts work in DeployHQ? [DeployHQ](https://www.deployhq.com) supports deployment automation features like pre- and post-deploy hooks, environment variables, and custom scripts. While some syntax changes may be needed, most scripts from tools like DeployBot, Capistrano, or Jenkins can be adapted with minimal effort. #### What support is available when switching deployment tools to DeployHQ? [DeployHQ](https://www.deployhq.com) provides extensive documentation, a dedicated support team, and migration-friendly features. Whether you're moving from another CI/CD tool or setting up automated deployments for the first time, the [DeployHQ](https://www.deployhq.com) team can assist you through every step of the migration process.