Move a project to another organization
A project (one website) can change its organization, for example when one company runs two products and wants them in separate organizations. The move is one transaction: everything or nothing. The website keeps counting with the same install code.
Where: Growth Intelligence › the project › Einstellungen › Erweitert › „In andere Organisation verschieben“.
REST GET /v1/projects/{project}/move/targets, POST /v1/projects/{project}/move/preview,
POST /v1/projects/{project}/move; MCP project_move_preview and project_move.
Who may move
A signed-in person (dashboard or an OAuth connection such as Claude) who is owner or admin in both
organizations (org:admin). An admin of only one of them gets 403 insufficient_scope, someone who is no
member of the target 404. Secret keys never move projects. The move asks for the project name typed again
(confirmName, MCP confirm_name).
What moves
| Item | What happens |
|---|---|
| Data | Visits, events, leads, goals, funnels, experiments, recordings, settings and the logo stay with the project; nothing is copied. |
Publishable keys (pk_…) | Go along and stay valid. |
| Secret keys bound to this project alone | Go along and stay valid (for example the website's proxy key and its lead reports). |
| Annotations, open hints, share links, report subscriptions, webhooks | Go along. People without access in the new organization no longer get reports. |
| Sales Engine | The Sales Engine learns the move from Growth Intelligence (project.updated in the new organization) and continues the project's link there; it assigns its contacts and rules in the new organization itself. |
What stays and what ends
- History stays with the old organization: audit log, MCP calls, sent notifications.
- Billing: usage of the running billing period so far stays with the old organization and appears on its invoice; from the move on the project counts for the new one (projects, pageviews, recordings). Invoices and subscriptions of both organizations are not changed.
- Links that end: secret keys for several projects lose this one, org-wide secret keys of the old organization no longer reach it, the project leaves the organization report's selection. A template of the old organization stays there; the project keeps its settings.
- Members of the old organization who are no member of the target lose access; the preview names them.
Blockers
Connections belong to an organization. While the project still uses one of the old organization, the preview
says ready: false and the move answers 409 project_move_blocked:
- ad logins or assigned ad accounts, conversion uploads over an ad login,
- a CRM connection, Search Console, Facebook pages for Instant Forms,
- Instant Forms of another project that report into this one,
- the project's short name is taken in the target (change it under Einstellungen › Erweitert),
- the target's plan has no room for another project.
Disconnect the connection in the project settings (Werbekonten & Budget, Meldungen, CRM, Google Search Console or Instant Forms), move the project, then connect it again in the new organization (or reuse an account you already connected there).
After the move
The dashboard opens the project in the new organization. Check with events_tail that events arrive, and in the
Sales Engine of the new organization adjust the link (Einstellungen › Allgemein › Verknüpfung mit Growth Intelligence).