Move a Chirp to another workspace

When you're done, the Chirp is in the workspace where it belongs.

Who can do this: the account owner, with more than one workspace (Creator, Business and Academy). Team members can't move Chirps between workspaces.

Move it

1. Open the Chirps page in the workspace the Chirp is in.

2. On its card, click More actions (the three dots), then Move to workspace (1).

3. Choose the workspace (2).

   

4. Read what will change and click OK. "Moved to" the workspace.

Only workspaces in your plan are offered. Moving is only on the Chirps page, not in the editor.

What moves with it

Its link, settings and published version, knowledge files, saved versions and history, Actions, who can open it, its lead form, and its analytics.

What changes

• It leaves its folder and the old workspace's Collections.
• Its main address is cleared, and links on the old workspace's own domains stop working. The new workspace's domains show it instead. If it was a domain's home page, that domain shows its list of Chirps. See A main address for a Chirp.
• It may appear on, or leave, your public profile, if one of the two workspaces has full white label.
• It takes the new workspace's look and OpenRouter key. It uses the new workspace's own key if it has one, and otherwise your account's key. Moving a Chirp out of a client's workspace with its own key moves its costs to your key; with no account key, it stops answering until you add one.
• Team access follows the new workspace's members.

Its www.chirpbuilder.com/c/ link stays the same.

What stays behind

• Leads it already collected stay on the old workspace's Leads page, with their counts. A visitor who sends the form again later updates their entry there.
• If its lead form sends leads to an email service, check the lead form after moving: it keeps using the connection from the old workspace.