Project Transfer
A project can be transferred from one tenant to another.
The receiving tenant must explicitly accept the transfer before ownership changes.
Once accepted, the sending tenant immediately loses access to the project and all its forms.
This is commonly used when:
- handing a project over to a client
- moving projects between company accounts
- transferring ownership during organizational changes
- separating staging and production ownership
- moving agency-built projects to customer ownership
What Gets Transferred
Not everything moves during a transfer.
Some data belongs to the project, while other data belongs to the tenant context where it was generated.
| Transferred | Stays with the Source Tenant |
|---|---|
| Project and all project settings | UI load history |
| All forms in the project | Usage analytics |
| Full form revision history | — |
| Translations | Source tenant subscription (cancelled on transfer) |
| API keys and configuration | — |
| Theme settings | — |
Why UI Loads and Analytics Stay
Buildocs UI Engine keeps usage analytics and UI load history with the original tenant.
This data reflects how the system was used under that tenant’s context, including:
- interface usage patterns
- performance and interaction metrics
- operational history tied to the tenant
Because this data is tenant-specific, it does not move with the project.
Translations
Translations are managed at the project level, not the tenant level.
This means:
- translations belong to the project itself
- they move with the project during transfer
- they remain consistent regardless of tenant ownership
This ensures that multilingual content stays aligned with the project structure and UI definitions.
Initiating a Transfer
Only users with the admin role can initiate a transfer.
Step 1
Go to the Projects list
Step 2
Open the row menu for the project you want to transfer
Step 3
Select Transfer Project
Step 4
Enter the Tenant ID of the receiving tenant
Buildocs validates:
- the tenant exists
- the tenant is not your own account
Step 5
Click Next
Step 6
Review the confirmation warning
Step 7
Click Transfer Project
A transfer request is sent to the target tenant.
You remain the owner until the receiving tenant accepts.
Only one pending transfer can exist per project at a time.
Once the receiving tenant accepts the transfer, you immediately lose access to:
- the project
- all forms inside the project
- project configuration
- project management access
Make sure you have exported or recorded anything you need before initiating the transfer.
Accepting or Rejecting a Transfer
When a transfer is pending, the receiving tenant sees an alert banner at the top of the Projects page.
Each incoming transfer shows:
- project name
- Tenant ID of the sender
The receiving tenant can:
- Accept
- Reject
Both actions notify the sending tenant.
On Acceptance
When accepted:
- the project moves immediately
- all forms move with it
- ownership changes instantly
- the sending tenant loses access
- the transfer is finalized
- a confirmation notification is sent to the sender
On Rejection
If rejected:
- the project remains with the original tenant
- nothing is transferred
- the sender is notified of the rejection
A new transfer can be initiated later if needed.
Required Permissions
Project transfer actions require the admin role on both sides:
- initiating a transfer
- accepting a transfer
- rejecting a transfer
This ensures ownership changes are explicitly controlled.
Summary
Project transfer moves:
- project structure
- forms
- configuration
- translations
- revisions
It does not move:
- UI load history
- analytics tied to tenant usage
This separation ensures that project portability does not break tenant-specific operational history.