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

```pulumi login
pulumi stack select dev
pulumi stack export --show-secrets --file dev.stack.json
pulumi login --local
pulumi stack init dev
pulumi stack select dev
pulumi stack import --file dev.stack.json```

<@UCU9C7W73> most like below, follow the document from <https://www.pulumi.com/docs/intro/concepts/state/#migrating-between-backends>

I found the "secrets_providers" in local state file was still point to Pulumi server.
```$ cat .pulumi/stacks/dev.json | jq '.checkpoint.latest.secrets_providers'                       0|PIPE|0 ✔  6s  
{
  "type": "service",
  "state": {
    "url": "<https://api.pulumi.com>",
    "owner": "weiliy",
    "project": "astarter",
    "stack": "dev"
  }
}```


You can use `pulumi stack change-secrets-provider` command to switch to another secrets backend also

<https://www.pulumi.com/docs/reference/cli/pulumi_stack_change-secrets-provider/>

<@UCU9C7W73> thanks. It works. But need one more step, if I am only login to the local server. It cannot migrate to new secrets-provider, because it did not have access to Pulumi server. I found that it can double login:
```pulumi login  // login to pulumi server
pulumi login --local // login to local server
pulumi stack change-secrets-provider -s dev passphrase  // migrate from default to passphrase```