# Transfer projects between organizations

`POST /organizations/{source_org_id}/projects/transfer`

Transfers selected projects, identified by their IDs, from your organization to another specified organization.

[Markdown for AI context](/guides/apis-sdks-reference-api-organizations-transfer-projects-from-org-to-org)

```bash title="REST API - curl"
curl "https://console.neon.tech/api/v2/organizations/$SOURCE_ORG_ID/projects/transfer" \
  -X POST \
  -H "Authorization: Bearer $NEON_API_KEY"
```

Also available in

::::tabs
:::tab{title="SDK"}
```typescript
import { createNeonClient, raw } from '@neon/sdk';

const neon = createNeonClient({ apiKey: process.env.NEON_API_KEY });
const { data } = await raw.transferProjectsFromOrgToOrg({
  client: neon.client,
  path: {
    source_org_id: process.env.SOURCE_ORG_ID
  }
});
```
:::

:::tab{title="Console"}
Console path: Organization → Settings → Transfer projects
:::
::::

## Parameters

Source org ID

`source_org_id`

string

The Neon organization ID (source org, which currently owns the project)

## Request body

**2 required** Required: `destination_org_id`, `project_ids`.

Destination org ID

`destination_org_id`

string

The destination organization identifier

Project IDs

`project_ids`

array

The list of projects ids to transfer. Maximum of 400 project ids

## Response

200

Projects successfully transferred from organization to organization

No example available.

## Errors

406

Transfer failed. The target organization has too many projects or an incompatible plan. Reduce projects or upgrade the target organization.

422

Transfer failed. Projects with active integrations (for example, GitHub or Vercel) cannot be transferred.

default

General error

This endpoint can return the standard Neon API error response.

Response fields

- `message` Required. Human-readable error message.
- `code` Required. Machine-readable error code.
- `request_id` Optional. Request identifier for debugging. You can provide one with the `X-Request-ID` header.

Retry guidance

If no response is returned, the request may still have reached the server. This is why retry safety depends on the method and status code.

Idempotent methods (`GET`, `HEAD`, `OPTIONS`) are generally safe to retry after a network error or timeout. Non-idempotent methods (`POST`, `PATCH`, `DELETE`, `PUT`) can change state, so avoid automatic retries unless your workflow can tolerate duplicate effects.

Responses with `423 Locked` or `503 Service Unavailable` are safe to retry. `423 Locked` means the resource is temporarily locked, usually because another operation is in progress.

## Related pages

- [Assign or update VPC endpoint](./apis-sdks-reference-api-organizations-assign-organization-vpc-endpoint.md)
- [Create organization API key](./apis-sdks-reference-api-organizations-create-org-api-key.md)
- [Create organization invitations](./apis-sdks-reference-api-organizations-create-organization-invitations.md)
- [Delete VPC endpoint](./apis-sdks-reference-api-organizations-delete-organization-vpc-endpoint.md)
- [List organization API keys](./apis-sdks-reference-api-organizations-list-org-api-keys.md)
- [List organization invitations](./apis-sdks-reference-api-organizations-get-organization-invitations.md)
- [List organization members](./apis-sdks-reference-api-organizations-get-organization-members.md)
- [List VPC endpoints](./apis-sdks-reference-api-organizations-list-organization-vpc-endpoints.md)
- [List VPC endpoints across all regions](./apis-sdks-reference-api-organizations-list-organization-vpc-endpoints-all-regions.md)
- [Remove organization member](./apis-sdks-reference-api-organizations-remove-organization-member.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.