Morning folks, I imagine this is a fairly frequently asked question. I have an existing metaplay project which has so far only been used for local development. This project will potentially soon need deploying to a (paid) cloud environment. I therefore need to move shift project's ownership from my private email address to my client's account, so that they can maintain it in the long term. Assuming the client creates a metaplay account, is it just a case of creating a new project on their side, editing

projectID

in

metaplay-project.yml

, and re-authing to the client's account with

metaplay auth logout

/

metaplay auth login

? Cheers

Hmm, I think the easiest is to just delete the metaplay-project file and run [metaplay init project-config](https://docs.metaplay.io/miscellaneous/cli-command-reference.html#metaplay-init-project-config-flags), keep in mind that if you have set up the environment configuration in Unity, you'll have to re-export the environment configs from the portal as per https://docs.metaplay.io/feature-cookbooks/unity-sdk-features/environment-configs.html#setup And of course, if you have any CI scripts, they will also still reference to the old project id

Ah cool, I hadn't clocked that I could init just the project-config, and not an entire project! Thanks. I have a couple of other edits to the yml that I assume I'll need to reproduce (namely, I 've changed the

sharedCodeDir

), but I doubt that will be be a problem.

Ah yeah, you'll have to re-apply those, there's also a update project config command but I'm not sure that lets you switch the project, I thnk it just refetches the config from the portal and applies it. But it's [here](https://docs.metaplay.io/miscellaneous/cli-command-reference.html#metaplay-update-project-environments-flags)

metaplay-init-config

successfully detected my changed SharedCode dir, impressive!