---
title: "Discussion on \"Migrate from CloudFormation to Terraform\" | Hashnode"
description: "Discussion on \"Migrate from CloudFormation to Terraform\". Do you need to migrate from CloudFormation to Terraform? It's pretty simple! Find out how!"
url: "https://hashnode.com/posts/migrate-from-cloudformation-to-terraform/6488eadf0d6023cee5166528"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Migrate from CloudFormation to Terraform](https://tymik.me/migrate-from-cloudformation-to-terraform?utm_source=hashnode&utm_medium=feed)

Do you need to migrate from CloudFormation to Terraform? It's pretty simple! Find out how!

Jun 13, 2023 · 3 min read · tymik.me  
Read the article

-   [#terraform](https://hashnode.com/tag/terraform)
-   [#aws](https://hashnode.com/tag/aws)
-   [#cloudformation](https://hashnode.com/tag/cloudformation)
-   [#devops](https://hashnode.com/tag/devops)
-   [#infrastructure](https://hashnode.com/tag/infrastructure)

## Written by

[Jan Tymiński](https://hashnode.com/@tymik)

@tymik · Poland

  
[View profile](https://hashnode.com/@tymik)

♾️ DevOps ☁️ AWS 🐳 Docker, Terraform, Automation

I started my professional career in 2012 as Systems Administrator and continued it until 2018 to become DevOps Engineer. I work with AWS since 2016 and I am 5 times certified AWS Specialist.

## Responses 1

Markdown supported · ⌘↵ to post

[Adam Brodziak](https://hashnode.com/@adambro)

[Jul 3, 2023](https://hashnode.com/posts/migrate-from-cloudformation-to-terraform/6488eadf0d6023cee5166528/comment/64a2927f8db091c401037010)

I wonder why go with Terraform? You loose some traits CloudFormation gives you, e.g. rollbacks on failed deploy, no need to keep external state. Since CF was used I guess it was AWS-only, so Terraform's questionable universality does not matter. Then why?

[Jan Tymiński](https://hashnode.com/@tymik)

[Jul 3, 2023](https://hashnode.com/posts/migrate-from-cloudformation-to-terraform/6488eadf0d6023cee5166528/comment/64a2927f8db091c401037010#reply-64a297f08db091c401037181)

Thank you for the question!

The Tale of the CloudFormation is there to explain it a little - the CF code was built through years by many people that were more or less experienced with the CloudFormation and eventually it became really hard to maintain - unmaintained, not up to date, tons of drifts, etc... Then there was an internal team built for taking care of all the infrastructure, with expertise in Terraform and inability to dive into existing CloudFormation stacks in any reasonable time. Terraform has just some little inconveniences that the team is aware of and we decided it's easier for us to get rid of CloudFormation as it was easier to achieve than fixing all the stacks - especially when not being experts in them. To make things more complicated, there were parts of the infrastructure in Terraform too - but in a similar state as CF stacks and we decided to not reanimate them but build new code from scratch on what we actually see in the infrastructure.

[Adam Brodziak](https://hashnode.com/@adambro)

[Jul 20, 2023](https://hashnode.com/posts/migrate-from-cloudformation-to-terraform/6488eadf0d6023cee5166528/comment/64a2927f8db091c401037010#reply-64b99942af9957de8741171e)

Thanks [Jan Tymiński](https://hashnode.com/@tymik) for explaining. I was wondering why not use CDK and import existing CF stacks.

[Jan Tymiński](https://hashnode.com/@tymik)

[Jul 21, 2023](https://hashnode.com/posts/migrate-from-cloudformation-to-terraform/6488eadf0d6023cee5166528/comment/64a2927f8db091c401037010#reply-64ba37d42e3477ebf6133bd2)

I hope it's more clear now and I'm glad you asked!
