Most software is bought twice. First one person signs up, does real work on their own, and pays a small amount. Later their company buys a team plan, often for a different tool, because the first one never gave the solo user an easy way to bring colleagues into the work they had already done. The personal-to-team move is a growth play that closes that gap: when a solo user creates or joins a team, you let them carry their existing work across in a click, with its history intact, so the team starts with something useful on day one instead of an empty screen.

The clearest current example is v0, Vercel's AI app builder. v0's Teams documentation (last updated 2 November 2026) says you can transfer chats "between any of your available scopes, either team or personal". One chat moves from its header menu with "Transfer Chat"; many move at once through Settings, Workspace, "Transfer Data". If a chat is linked to a Vercel project, the project travels with it when you own the project's current team. After the move, team owners can see the chat's full history, including messages written before the transfer. The billing follows the same logic: each seat includes $30 of monthly credits that roll over for one month, and a Shared Credit Pool that the whole team draws from once individual credits run out.

The v0 changelog shows the pieces arriving over the year: a "Transfer Chats" option after account upgrade (25 February 2026), team chats visible to the team by default (10 September 2026), and, on 6 October 2026, "Personal v0 accounts are now team workspaces". It says migrated accounts kept their chats, projects and settings.

Why does this work as growth? Two reasons. The person most likely to bring in a team is your heaviest solo user, and the thing stopping them is usually rework: re-creating projects, re-explaining context, re-uploading files. Remove the rework and the invite becomes cheap. Second, the transferred history becomes the team's onboarding. A new colleague opens a chat and sees how the work got where it is, which is far more persuasive than a welcome tour. This is the single-player-to-multiplayer progression: the product is useful alone, then more useful with others, and the bridge between the two costs the user nothing.

This suits any product where one person builds up valuable work over time and that work is naturally shared later: AI builders and writing tools, design and diagram apps, research notebooks, client portals, analytics dashboards, prompt libraries and template tools. It fits solo founders whose buyers are freelancers today and small agencies tomorrow. It matters less if your product holds nothing worth keeping (a one-off converter, say) or if every account is already a company account from the first day.

Here is copy you can adapt. Keep it short and specific about what stays the same.

The success message points straight to the invite, because a moved project with no one else in the room delivers half its value.

Before you ship, ask whether moving their work gives the solo user something real. Three checks matter. Do they avoid rebuilding? Do they keep history, so the context that made the work valuable comes along? Does billing get simpler, with one shared pool instead of personal cards? If the answer to any is no, the prompt feels like a sales tactic.

Notion shows the trade-off clearly. Its guide to moving content between workspaces says content is duplicated into the destination, and that links, relations, permissions and page history may break; it recommends keeping the originals until you are sure the copy is right. That is honest guidance for a hard problem across separate workspaces, and it shows why a move inside one account, keeping the same item, is easier for users to trust. Figma's drafts update took a different route: it moved drafts into teams, each team with its own drafts space, and its move-a-file guide warns that moving a file "may change who has access to it". Spell out permission changes like this on your confirmation screen.

No company has published verified uplift numbers for this play that we could find, so here is a model you can replace with your own figures. Say you have 1,000 paying solo users at $20 a month. Suppose 15% of them regularly share work with someone else, which gives 150 people. If the transfer prompt turns one in five of those into a two-seat team, that is 30 teams, adding 30 extra seats, or $600 a month. Every input here is an assumption. The point is to see which number matters most: the share of solo users who already collaborate. Measure that first.

From today's Daily Briefing →