You can transfer your projects to another workspace by following our project transfer documentation, and the instructions vary based on the subscription type you are transferring from and to. For your situation specifically: a personal workspace on Hobby cannot add members, so the cleanest path is to upgrade the current workspace to Pro, invite the company account as an Admin via Workspace Settings, then have the new Admin remove the original individual. Nothing moves in this flow - the workspace, its projects, services, domains, variables, GitHub deploy settings, and generated service domains (including the suffixes like portal-agent-production-36c1) all stay exactly where they are. The outgoing admin's payment method stays on file until the new admin replaces it in the workspace billing settings, so that swap should happen right away. Pro is the only plan that supports workspace members, so there is no Hobby path for team ownership.

Heya. The bot covered most of this, but a few gaps worth closing.

To answer Q1 directly: no, there's no way to transfer a personal workspace itself to another account — workspaces aren't transferable, only projects are. So for company ownership you'll need a team workspace.

Re: the Pro-then-remove dance — worth noting the original owner doesn't necessarily have to be removed. If nobody's leaving, they can stay on as a member; ownership just shifts to whoever the workspace admin is. Removing them is only needed if you want the account fully disassociated from the individual.

One thing to watch on the billing swap: Pro is billed per-seat-ish (minimum 5 seats on Pro), so moving from Hobby (~$5/mo usage) to a Pro workspace adds a fixed monthly cost on top. If the goal is just "company owns it, not a person," also worth asking whether an organization workspace on Pro must be the route, or whether Railway supports attaching company billing details to a personal workspace — I don't believe it does, but that would be the cheapest path if it existed.

Me again. Just double checked a few things:

First, a correction to my own comment above: Pro is $20/mo flat with $20 of included usage, and adding members does not incur any seat cost. Sources: docs.railway.com/pricing/plans and docs.railway.com/projects/workspaces. So the upgrade is ~$15/mo over Hobby, not the per-seat hit I implied. There's no 5-seat minimum. I got that wrong.

On Q3 — domains survive. Project transfers move the entire project as-is, and *.up.railway.app domains (including the generated suffixes like portal-agent-production-36c1) persist through the transfer. Source: docs.railway.com/projects#transferring-projects — and Railway staff confirmed exactly that in this thread: station.railway.com/questions/transfer-of-project-63b9f94f. No env-var breakage from domain changes.

On Q4 — env vars and settings survive too. The transfer moves the whole project (services, volumes, variables, deployment history) as-is; same source above. The only things to mind: you must be an Admin of the project to initiate the transfer, and both source and destination workspaces need an active Hobby or Pro subscription.

One wrinkle worth flagging for your exact case: a transfer between workspaces requires being a member of both, and Hobby can't add workspace members (docs.railway.com/projects/workspaces). So the bot's route — upgrade to Pro, invite the company account as Admin, then either transfer the project out or remove the individual — remains the clean path. Since Pro includes $20 of usage and you're at ~$5/mo, the real cost of "company-owned" is about $15/mo.