Transfer Snapshot Ownership

InstaWP lets you move a snapshot to another team you belong to. This is useful when a snapshot was created in the wrong team, or when you want to hand a template over to the team that will maintain and launch sites from it.

Note: Snapshot transfer is team-to-team only. You can transfer a snapshot to one of your own teams (a team you own, or a team you are a member of) — there is no email-invite option like there is for site transfers. The transfer also happens immediately: there is no request for the recipient to approve or reject.

Before you start

A few things are worth knowing before you transfer, because they are easy to miss:

• Both teams must have the same billing type. You can transfer legacy → legacy, or PPU (v3) → PPU (v3) — but never across the two. If the source and destination teams don't match, the transfer is rejected with "Site transfers are only allowed between accounts with the same billing type (PPU to PPU, or legacy to legacy)."
• The transfer is instant and there is no approval step. As soon as you confirm, the snapshot belongs to the destination team. To undo it, you have to transfer it back.
• The parent site is included by default. If the snapshot still has a live parent site, the option to move that site along with the snapshot is pre-checked. Uncheck it if you only want the snapshot itself to move.
• Monetized snapshots can't be transferred. If the snapshot is being sold (listed on the Template Store), the transfer is blocked.

How to transfer a snapshot

Step 1: Go to the Snapshots page, find the snapshot you want to move, and open the three-dot menu (⋯) in the ACTIONS column. Click Transfer Snapshot Ownership.

Step 2: The Transfer Snapshot Ownership modal opens. It shows the Snapshot Name so you can confirm you picked the right one.

Step 3: Open the Destination Team dropdown and pick the team that should receive the snapshot. You can search the list. Teams you own are marked with an "Own team" badge.

Step 4: Optionally add a Message to give the receiving team some context.

Step 5: If the snapshot has a live parent site, you will see "Also transfer the parent site … with this snapshot" — and it is checked by default.

• Leave it checked to move the parent site to the destination team along with the snapshot.
• Uncheck it to move only the snapshot and leave the site where it is.

When the parent site is included and that site has other snapshots, an "Also transfer other snapshots from this site" list appears. Every sibling snapshot is selected by default — uncheck any you want to leave behind, or use Select all / Deselect all.

Step 6: Click Transfer Ownership. The transfer completes immediately, and the snapshot disappears from the current team's Snapshots list. Switch to the destination team using the team switcher in the top-right corner to see it there.

Transferring from the snapshot's Settings page

You can also start the transfer from inside a snapshot. Open the snapshot, go to the Settings tab, and scroll to the Ownership section — then click Transfer Snapshot Ownership.

Note: Use the Snapshots list (⋯ menu) if you want to move the parent site or sibling snapshots too. The modal opened from the Settings page currently does not offer the parent-site option, so it transfers the snapshot on its own.

Why a transfer can fail

The transfer is blocked, with an error message, when:

• The two teams have different billing types. Transfers are only allowed legacy → legacy or PPU (v3) → PPU (v3). A legacy team and a PPU team can't hand snapshots to each other in either direction — you'll see "Site transfers are only allowed between accounts with the same billing type (PPU to PPU, or legacy to legacy)."
• The snapshot is monetized. Snapshots being sold on the Template Store can't be transferred — "Only non-monetized snapshots can be transferred."
• The destination is not one of your teams. You can only transfer a snapshot to a team you own or belong to.
• The snapshot is already in that team. Pick a different destination.
• The destination team's owner has no payment method. When a paid snapshot (or a paid site/sibling snapshot bundled with it) moves into a PPU team, that team's owner must have a card on file first — the team picks up the billing.
• The receiving team's owner account is suspended, or is suspended for non-payment.

Snapshot vs. site transfers

These are two different features — don't mix them up:

	Snapshot transfer	Site transfer
Destination	Only a team you belong to	Another team or a different user, by email
Approval	None — immediate	Email transfers need the recipient to approve
Billing type	Must match — legacy → legacy, or PPU → PPU	Must match — legacy → legacy, or PPU → PPU
Where to start	Snapshots page ⋯ menu, or the snapshot's Settings tab	Sites page ⋯ menu

Need help? If you have questions about transferring a snapshot or run into an issue, reach out to our support team via the ticket widget or email us at support@instawp.com.