Full CloudFormation to Terraform Migration

My AWS estate is currently defined through a collection of CloudFormation stacks that cover compute (EC2, Lambda), storage (S3, EBS), and networking layers (VPCs, subnets, route tables, etc.). I now need every one of those stacks—both the template logic and the live resource configurations—translated into Terraform code.

During the migration we will also refine the setup rather than lift-and-shift it verbatim. Tagging standards, naming conventions, and a few parameter values have to be updated so the resulting Terraform matches current best practices and my team’s evolving standards. I will share a short change log and we can iterate on anything that surfaces while you import the state.

Deliverables
• Terraform files (HCL) organised modularly and covering all existing resources
• A repeatable migration plan outlining the exact terraform import commands used and any manual steps required
• Remote state (backed by S3 + DynamoDB) or an equivalent backend configured and documented
• A concise README explaining how to deploy, destroy, and extend the new codebase

The work will be considered complete once I can run terraform plan and see no drift between the newly generated state and the live AWS environment, and all agreed adjustments are reflected. If you have previous experience moving mixed CloudFormation workloads to Terraform with zero downtime, your expertise will be highly valued.