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

Unfortunately, you will need to move the code by hand.

While I've never tried to use aliases to move resources between projects and stacks, the definition of the Alias interface implies that you can, and you won't need to evict the resources from one project and import them into the other. The Alias interface allows you to specify the old resource's project and stack as well as type, name and parent: if project and stack work the same way as the other properties, then Pulumi should move the resource for you just by using the alias opt. You just need to look after the code.

Presumably, this requires that both the old and new projects are in the same backend.

<https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/pulumi/#Alias>

Thanks Paul. I will look Into this. I was afraid of that.