Transfer ownership — hand a site to another person or team

Last updated: 2026-08-10

At a glance

Time needed

About 10 min

Plan required

Free plan

Coding knowledge

None

Where to do it

Account

Step by step

1. 1

   Start the transfer and confirm your code

   From the /sites dashboard, click a card's transfer icon to open the site transfer center at /transfer — there's no separate menu entry for it, only that card. Pick “Transfer to another user,” enter the recipient's email, and click “Start transfer”; a verification code goes to the sender's (the current owner's) email. Say Momo Coffee just got a new owner — enter their email and the process starts. The code is valid for 10 minutes, and getting it wrong more than 5 times means requesting a new one.

   

2. 2

   The recipient confirms their consent code

   Once the sender verifies, the recipient gets notified and sees the request under “Incoming transfer requests.” Clicking “Get verification code” sends a code to the recipient's own email, and entering it records their consent — ownership hasn't actually changed yet at this point. Only after that consent does the final-approval email go out to the sender.

   Ownership transfer › Incoming request · Momo Coffee

   From name@company.com

   Status Awaiting recipient

   Consent code Sent by email · confirming records consent
3. 3

   24 hours after final approval, it can still be undone

   Once the recipient consents, a one-time final-approval link goes to the sender's email. The moment that link is clicked (or approved directly in the app), a 24-hour cooling-off window starts — during it, the sender can cancel in-app with an emailed code, or use the one-click rollback link in the email. Ownership actually changes hands once that window ends, or the instant the recipient clicks “Receive now” to finalize early with both sides confirmed. That 24-hour window only applies to transfers to another person — moving a site between a team and a personal account within the same account is instant, confirmed by nothing more than the team owner's emailed code, with no cooling-off at all.

   Ownership transfer › Final approval · Momo Coffee

   Status Settling (finalizes in 24h)

   Time left 18 hours left

   Cancel In-app with a code · one-click via email link

   Receive now Recipient can finalize instantly
4. 4

   If the recipient's plan can't support it, the transfer is blocked

   Right as ownership is about to change, the recipient's plan gets checked again — not just site, storage, and custom domain limits, but the actual features the site uses: multiple pages, page locks, the number of inquiry forms, and file types beyond images and fonts. If Momo Coffee's site has a page lock turned on and the recipient's plan doesn't support page locks, the transfer is blocked outright. If the recipient's usage changed enough during the 24-hour window to go over a limit, the transfer is cancelled instead of finalized, for the same reason.

   Ownership transfer › Admission check · Momo Coffee

   Multiple pages Rejected if recipient's plan lacks it

   Page lock Rejected if recipient's plan lacks it

   Inquiry form count Rejected if over recipient's plan limit

   File types Non-image/font files rejected by plan

Frequently asked questions

Read next

• Managing your sites — folders, rename, delete & recovery How to organize sites into folders, rename them, and undo a deletion within 7 days from the /sites dashboard (English)
• Create a team and invite members to manage a site together How to create a team, invite members with roles, and understand resource allocation and seat limits (English)
• Account settings: what you can change here, and what you can't What you can actually change on /settings and /profile, and what only lives in the SSO account (English)
• Audit log — see who changed what, and when How to check your account's audit log at /audit and export it as CSV — personal logs are free on every plan, team logs need Team or Ultra (English)