No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

What is the best strategy to migrate resources from classic provider to native provider? IaC is existing built up with classic provider. Now keeping both providers side by side for slow migration.

<https://www.pulumi.com/registry/packages/azure-native/from-classic/|Migrate from classic Azure to Azure-Native | Pulumi Registry> I think it's recommended way

This is bit impossible when dealing with 400+ resources...even if I decide to migrate by components, still a lot manual operation.

I'm not from pulumi team, but if I would need to do such migration, I would start with identifying if I can drop some resources or drop and recreate. Then I would try mark all classic resources with RetainOnDelete flag, run pulumi, then I would list all resource IDs, add pulumi native items, run pulumi import in the loop and then I would remove all classic resources from code

Agree with <@U08MLSQ4PT8> - whatever can just be recreated/migrated, do that.

For the remaining resources that you need to import, if you're a Pulumi Cloud customer, Neo should be able to do a good job with this task. If not, I would use a local LLM like Claude Code.