Skip to content
Question About Pro Plan Requirements for Transferring Projects Between Railway Accounts
Anonymous
OP

a month ago

Hello Railway Support Team,

I currently have three production projects hosted across three separate Railway accounts, all of which are on the Hobby plan.

I own a software development company called NorthBlue Technology SpA, and I would like to centralize all three projects under my company’s main Railway account to simplify infrastructure management, billing, and maintenance.

I understand that upgrading to the Pro plan may be necessary to transfer projects directly between different Railway accounts or workspaces.

I have no problem upgrading to the Pro plan if required.

However, I would like to clarify one important detail before proceeding:

Do I need to upgrade all four Railway accounts (the three source accounts and the NorthBlue destination account) to the Pro plan to complete these transfers? Or would upgrading only the destination account (NorthBlue Technology SpA) to Pro be sufficient?

My goal is to transfer the existing projects directly, including their PostgreSQL databases, persistent volumes, environment variables, and configurations, without having to manually migrate data or interrupt production services.

I would appreciate your guidance on the most efficient and cost-effective way to accomplish this.

Thank you very much for your time and assistance!

Best regards,

NorthBlue Technology SpA

Software Development & Cloud Infrastructure

Solved

1 Reply

Railway
BOT

a month ago

You don't need Pro on any of the four accounts for this. Handing a project to another person's account (Transfer Ownership) works between Hobby workspaces: the source workspace and the destination workspace each need an active Hobby or Pro plan, so all four accounts can stay on Hobby.

For each project, invite the NorthBlue account as a member from the project's settings under Members. Project invites aren't Pro-gated, and Hobby allows up to 3 project members. Then, from the same Members list, use the three-dot menu next to the NorthBlue account and choose Transfer Ownership. The source account needs two-factor authentication enabled. NorthBlue gets an email it must accept within 24 hours, and it picks which of its workspaces the project lands in. Projects with storage buckets have to have those removed before the transfer goes through.

Once accepted, the project bills against the NorthBlue workspace's subscription. Anyone else who had access only through a project invite will need to be re-added afterward.


Status changed to Awaiting User Response Railway • about 1 month ago


Status changed to Solved Anonymous • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...