> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hoista.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Bring in an existing project

> Add projects that already run on your providers, without moving or redeploying them.

Importing adds resources that already run on your providers to a Hoista project. They keep their deployments, data and accounts. The project starts in **watching** mode, and nothing changes at the provider.

![Hoista finds the resources on your connected accounts and groups them by provider project. You review and import them as a watching project. Linking a source and switching to managed is a separate step you take later.](https://mintcdn.com/mirt-lab/xnVa5lZdCrkkDEzj/assets/diagrams/import-flow-light.svg?fit=max\&auto=format\&n=xnVa5lZdCrkkDEzj\&q=85\&s=26a81e553238b610d4401df1466a366d)

![Hoista finds the resources on your connected accounts and groups them by provider project. You review and import them as a watching project. Linking a source and switching to managed is a separate step you take later.](https://mintcdn.com/mirt-lab/xnVa5lZdCrkkDEzj/assets/diagrams/import-flow-dark.svg?fit=max\&auto=format\&n=xnVa5lZdCrkkDEzj\&q=85\&s=a0e7dcf3c5309e99f617066da0927237)

Importing reads what your accounts already run. The project starts in watching mode.

## Import from Desktop

1. [Connect](https://docs.hoista.dev/guides/accounts.md) every account that holds part of the project, for example a Railway account for the backend and a Neon account for the database.
2. On **Projects**, find **Found on your providers** and select **Review and add**.
3. Each provider project goes into a Hoista project of the same name. Change where it goes, untick what to leave out, or drag a resource to another project.
4. Import, then open the project and check its **Map**.

![The Import from Cloudflare dialog, listing two Workers with a checkbox and an Import into choice each](https://mintcdn.com/mirt-lab/bTbgaR1vteaGCpS-/assets/screens/import-review-light.webp?fit=max\&auto=format\&n=bTbgaR1vteaGCpS-\&q=85\&s=8fa7ada09c07f8d184da944ddd36723c)

![The Import from Cloudflare dialog, listing two Workers with a checkbox and an Import into choice each](https://mintcdn.com/mirt-lab/bTbgaR1vteaGCpS-/assets/screens/import-review-dark.webp?fit=max\&auto=format\&n=bTbgaR1vteaGCpS-\&q=85\&s=87f644962acf0d33172a1def77bf252a)

Importing from Cloudflare. Each provider project becomes a Hoista project of the same name.

If Hoista finds two projects that look like one app, it offers **Combine into** that project. Check the accounts first. Similar names do not prove that resources belong together.

## Import from the CLI

```bash theme={null}
hoist accounts add railway
hoist accounts add neon
hoist import --list
hoist import RAILWAY_RESOURCE_ID NEON_RESOURCE_ID --new my-app
hoist status my-app
hoist map my-app
```

In a terminal, plain `hoist import` lets you pick from a list instead. To add another resource later, run `hoist import RESOURCE_ID --project my-app`. A resource can belong to only one project.

To set aside resources you don't want, run `hoist import hide RESOURCE_ID`. List them with `hoist import --list --hidden` and bring one back with `hoist import unhide RESOURCE_ID`. Hiding only changes Hoista's list. It does not pause, delete or stop billing for anything.

## Fix the grouping

On a resource's page, use **Move to another project** or **Remove from project**. A removed resource goes back to **Found on your providers**. To drop a whole watched project from Hoista, use **Stop watching** in its **Settings**. None of these change anything at the provider.

```bash theme={null}
hoist resources move RESOURCE_ID --to other-app
hoist resources remove RESOURCE -p my-app
hoist projects merge old-app --into my-app
hoist projects remove my-app
```

## Manage the project with Hoista

Link the folder or GitHub repository the project builds from. In Desktop, open **Settings** and use **Source**. Then switch the mode from the CLI:

```bash theme={null}
hoist link my-app --folder ./my-app
hoist projects manage my-app
```

To link a repository instead, run `hoist link my-app --repo OWNER/NAME`, with `--branch` if it isn't the default branch. `hoist projects watch my-app` switches back to watching.

Linking a source does not switch the mode by itself. Keep your existing database and its data unless you have planned a migration.

## Ask an agent for an overview

```text theme={null}
Use Hoista to inspect my-app. Show its resources, providers and status.
Say which information is unavailable. Do not change anything.
```

The agent needs a [Hoista connection](https://docs.hoista.dev/agents/connect.md).

## Related

> [card] [Connect hosting accounts](https://docs.hoista.dev/guides/accounts.md)
>
> Connect, check and rotate accounts.

> [card] [Plan and deploy](https://docs.hoista.dev/guides/deploy.md)
>
> Deploy once the project is managed.

> [card] [How Hoista works](https://docs.hoista.dev/getting-started/concepts.md)
>
> Projects, resources, watching and managed.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.