HashiCorp's license change in August 2023 prompted a significant shift in the infrastructure-as-code (IaC) space. The transition from the Mozilla Public License (MPL) to the Business Source License (BSL) raised concerns among platform teams relying on Terraform, leading to the emergence of OpenTofu. This open-source fork reinstates MPL 2.0 governance under the Linux Foundation, addressing fears of vendor lock-in and restrictive licensing. OpenTofu maintains command-line compatibility with Terraform, allowing teams to shift with minimal disruption while ensuring a truly open-source model. Key differences between Terraform and OpenTofu revolve around licensing, governance, and security. OpenTofu's MPL 2.0 allows unrestricted commercial use and modification, contrasting with Terraform's BSL, which limits competitive use and redistribution. OpenTofu's governance structure, led by a Technical Steering Committee, ensures that no single vendor can unilaterally change the licensing terms again — a vital safeguard for organizations wary of future disruptions. Moreover, OpenTofu includes native state file encryption, enhancing security by protecting sensitive data, which is essential for compliance in regulated environments. Migrating from Terraform to OpenTofu involves straightforward technical adjustments, such as replacing the Terraform binary and updating CI/CD pipelines. However, the real challenge lies in organizational change management. Teams accustomed to Terraform will need to adapt their documentation and training materials to reflect the new tool. A phased adoption strategy is recommended, starting with non-critical infrastructure to minimize risk while updating training and runbooks concurrently. Overall, the choice between Terraform and OpenTofu hinges on aligning with governance needs, risk tolerance, and existing workflows.