HCP Vagrant deprecation: important dates and migration guidance
Curated from HashiCorp Blog
If your team relies on HCP Vagrant for reproducible development environments, the clock is ticking. HashiCorp’s announcement signals the end of an era for this specific workflow, pushing you to reconsider how you provision local infrastructure. This isn’t just a minor update; it’s a fundamental shift in how you manage local development consistency. You need to evaluate whether migrating to Terraform-based local workflows, Docker, or other containerized solutions makes sense for your stack. Delaying this transition will force a rushed migration later, potentially disrupting ongoing projects. Take time now to audit your current Vagrantfiles and map out a migration path. Your takeaway: identify your most critical Vagrant-based environments today and draft a migration strategy before the deprecation dates hit, ensuring you have a tested alternative ready.
HCP Vagrant will be deprecated in 2026. Users should begin planning migrations as box creation, support, and operations are phased out.
— HashiCorp Blog