Autoscaling Report: Production databases on Neon use 2.4x less compute and 50% less cost than if they were running on a provisioned platform.
/API reference/Users/Transfer projects from personal account to organization
POST/users/me/projects/transferdeprecated

This endpoint is deprecated. Scheduled for removal on 2026-07-01.

Transfer projects from personal account to organization

DEPRECATED. Personal accounts have been migrated to organizations, making this operation no longer applicable.

Markdown for AI context

Quick start

REST API - curl
curl "https://console.neon.tech/api/v2/users/me/projects/transfer" \
  -X POST \
  -H "Authorization: Bearer $NEON_API_KEY"
Also available in
import { createApiClient } from '@neondatabase/api-client';

const api = createApiClient({ apiKey: process.env.NEON_API_KEY });
const { data } = await api.transferProjectsFromUserToOrg({});

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 personal account to organization

No example available.

Errors

406

Transfer failed - the target organization has too many projects or its plan is incompatible with the source account. Reduce the number of projects or upgrade the target organization to increase its capacity.

422

One or more of the provided project IDs have GitHub or Vercel integrations installed. Transferring integration projects is currently not supported

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.

Was this page helpful?

On this page

Copy neon init command