# move_site_code_to_modulify

Source: https://modulify.ai/docs/mcp/code/move-site-code-to-modulify

Copies the code of a site that lives in your GitHub back into a repository Modulify manages.

- Title: Move the code of a site back to Modulify
- Scope: `code:write`
- Access: Makes changes

This is the **Move back to Modulify** row of the site's **Repository** section, covered in [Move the code back to Modulify](https://modulify.ai/docs/editor/move-code-to-github#move-the-code-back-to-modulify). Modulify edits and publishes from its own repository again once the copy is confirmed. It works on every plan, including Free, and needs the **Transfer projects** permission.

It brings back the `preview` branch, the publish branch, which comes back as `production` if it was renamed, and Modulify's own `modulify/` backup branches, except the `modulify/chat-` branches of its chats. Branches and tags you created yourself stay only in your GitHub. A repository Modulify created in your organisation is archived once the copy is confirmed, and one you picked as an existing repository is left as it is.

It is refused while an AI edit or a publish is running, while the code is still being copied into your GitHub or is already moving back, and while Modulify cannot reach the repository. The response only says the copy started, with the repository in `returning`. Editing and publishing pause until it finishes, so read `get_site_repository` until `CustomerOwned` is `false`.

## Inputs

| Input | Type | Required | Description |
| --- | --- | --- | --- |
| `projectId` | string | Yes | The site id. |