Terraform to Pulumiizer Map

Before you rewrite a Terraform project in Pulumi, you need an inventory of what has to change. The Terraform to Pulumiizer Map parses your pasted .tf and produces a clear table that maps every Terraform resource type you use to its Pulumi equivalent, including the Pulumi package you will need to import. It answers the question "what becomes what" before a single line of Pulumi is written, which is the first planning step of any migration and a good way to estimate its true scope. Teams that skip this step often discover late that a resource has no direct one to one Pulumi equivalent, so building the map up front avoids nasty surprises.

Like the converter, the mapper runs entirely in your browser using a real HCL parser, so your configuration never leaves the page. Each resource type appears once, even if you use it many times, so the table is a compact, deduped checklist rather than a noisy echo of your source. A built in map covers the popular AWS, Azure, Google and Kubernetes resources, with a best effort fallback that follows the provider dot class convention for anything unfamiliar. Use the table as the backbone of your migration ticket: paste the .tf, hand the map to the engineer doing the work, and let them tick types off as they translate them. The live stats panel confirms how many distinct types were discovered so you can size the effort, and the markdown output slots neatly into a planning document your reviewers can read without running any tool.

• Real HCL parse - discovers resource types with a client side parser.
• Type map - common aws, azure, gcp and kubernetes types mapped.
• Table output - Terraform type, Pulumi type and package shown in clean columns.
• Deduped - one row per resource type, no matter how many instances you declare.
• Fallback mapping - unknown types follow the provider dot class pattern so nothing is lost.
• Validation - clear errors on empty or unparseable input.
• Markdown export - copy, download or print a portable table.
• Live stats - see how many types were mapped and the output size.
• Browser only - fully client side and private.
• Sample loader - prefill a realistic example in one click.
• Package column - know exactly which import to add for each provider.
• Multi provider - mixes aws, azure, gcp and k8s in a single table.

1. Paste your .tf - include the resource blocks you plan to migrate.
2. Generate the map - review the table and the live stats panel.
3. Read each row - match the Terraform type to its Pulumi type and package.
4. Check the stats - confirm the mapped type count matches your expectations and find gaps.
5. Export it - copy, download or print the markdown table.
6. Use it as a plan - turn each row into a concrete migration task in your tracker.
7. Revisit - regenerate as the .tf changes so the plan stays current.

Simple config: a file with aws_instance and aws_s3_bucket yields two rows mapping them to aws.ec2.Instance and aws.s3.BucketV2, both from the @pulumi/aws package. Mixed cloud: adding azurerm_resource_group adds a row for azure.core.ResourceGroup from @pulumi/azure, so you can see at a glance which packages the target project needs to declare. Unknown type: a custom myorg_widget appears as myorg.Widget with a best effort package you can correct before coding. Count check: if the table shows fewer rows than you expected, you may have resources behind modules or for_each loops that expand at apply time, which is worth noting in the plan. The stats panel reports the total number of distinct resource types discovered, which is a good size estimate for the migration before you start writing code.

• Clear inventory - exactly what maps to what, in one calm view.
• Accurate - real parsing, with no guessing about which types you actually use.
• Portable - works for any provider you paste, public or private.
• Private - parses only in your browser, with no upload and no telemetry.
• Planning aid - the table becomes a ready made migration checklist for the team.
• Fast - a deduped map in seconds, even for large configs.
• Reviewable - the markdown export drops into a wiki or ticket for sign off.