If you build websites for other people, this comes up eventually. You put a client's site together under your own Cantrip account, get it looking right, and then it's time to hand over the keys. You move the website to their team. Done, right?
Mostly. But two things change when you do that, not one, and the second one is easy to miss.
The team changes. So does the billing owner. Moving a website to a team doesn't just relabel who it belongs to. It also swaps who's responsible for the bill. Subscription ownership resolves to the team owner, not whoever originally built the site, so the moment you transfer, your client's team is on the hook for their own plan going forward. Obvious once you think about it, but worth saying plainly: don't hand a site to a client's team assuming you're still footing the bill.
The less obvious part: future content gets credited to the new owner too. Every post on a Cantrip site can fall back to an author's name when nothing else is set. That fallback used to just check whoever originally created the website, which sounds fine until you notice what breaks: an agency hands a finished site to a client, the client writes a new post, and the byline still reads like it came from the agency. Cantrip ties that credit to the actual team owner at the moment of the move now, not the original builder. So after a transfer, anything the client writes from that point on carries their name, not yours.
Here's the part worth knowing before you rely on it: that only applies going forward. Posts you wrote and published before the move keep their original byline. Moving a website doesn't rewrite history, it just changes who gets credited from that point on. If you want older posts re-attributed too, that's a separate, manual edit, not something the transfer does for you.
It's a small distinction, but it matters if you hand off client work regularly. The site, the billing, and future content ownership move together the moment you transfer. Whatever you already published under your own name stays yours in the byline, even after someone else owns the site.