a month ago
Before a planned handover of an existing project to a dedicated school account/workspace on Hobby, please confirm the effects of both Transfer Project and Transfer Ownership. Are service/environment IDs, volume data and attachments, variable values/references, deployment history and the .up.railway.app URL preserved without recreation or restart? Are the Bucket, objects, snapshots and S3 credentials also preserved, and must any credentials be rotated? Does GitHub/autodeploy need reauthorization? Is there downtime, and how are usage and pending invoices split at the transfer? Are active Hobby plans on both sides sufficient, and which permissions are required? We need written confirmation from the Railway team to plan the handover. No transfer or configuration change is being requested here.
5 Replies
a month ago
Both Transfer Project (moving it into a workspace where you are an Admin) and Transfer Ownership (handing it to another person) move the existing project as-is. Nothing gets recreated: project, service and environment IDs, volumes and their data, variables and references, deployment history and the .up.railway.app domains all stay the same. Running deployments are not redeployed or restarted as part of the transfer.
The one hard blocker is the Bucket. A project that contains a bucket cannot be transferred with either flow, so the bucket and its objects have to be deleted before the transfer. That means there is no "preserved" path for the bucket, its objects or its credentials. Any bucket created after the move gets new credentials.
GitHub autodeploy is tied to the user who authorized the GitHub app. If the receiving account has not granted that app access to the repo, it needs to do so for auto-deploys to keep working.
For billing, usage before the transfer stays with the source workspace and usage after it goes to the destination. Each workspace keeps its own subscription and invoices, so pending invoices stay where they are.
Here is what each flow needs. Transfer Project requires you to be an Admin on the destination workspace, and that workspace needs an active subscription. Transfer Ownership requires active Hobby or Pro plans on both sides, the recipient to already be a project member, and two-factor auth on the initiating account. The recipient then has 24 hours to accept from the email.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Thank you. This automated response identifies a blocker that changes the handover plan. Could a Railway team member confirm whether both transfer flows currently reject any project with a bucket, and whether there is a supported way to transfer ownership while preserving its encrypted backups and avoiding deletion? The Projects and Storage Buckets docs I checked do not state this transfer restriction. Please provide an official reference and a non-destructive handover procedure, including any waiting period. We will not delete or change resources based solely on an automated reply.
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Yes, that's correct. Transfer Project and Transfer Ownership both currently refuse a project that contains a bucket. The Transfer Project dialog names the bucket and asks for it to be deleted before the move can go ahead. This is a current product limitation, so we can't point you to a separate published reference beyond what the dialog shows.
We don't have a supported way to transfer a project with its bucket, objects, backups or S3 credentials kept in place, and we have no manual override for this. Any bucket created in the project after the transfer will have its own new credentials.
The rest of our earlier answer still holds. IDs, volumes, variables, deployment history and the .up.railway.app domain stay the same through either transfer.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
Yes, that's correct. Transfer Project and Transfer Ownership both currently refuse a project that contains a bucket. The Transfer Project dialog names the bucket and asks for it to be deleted before the move can go ahead. This is a current product limitation, so we can't point you to a separate published reference beyond what the dialog shows. We don't have a supported way to transfer a project with its bucket, objects, backups or S3 credentials kept in place, and we have no manual override for this. Any bucket created in the project after the transfer will have its own new credentials. The rest of our earlier answer still holds. IDs, volumes, variables, deployment history and the .up.railway.app domain stay the same through either transfer.
a month ago
We still need a Railway team member to confirm the non-destructive handover procedure requested above. Please keep this question open and route it to a person. The automated answer does not resolve how to preserve the encrypted backups before a future handover.
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Both Transfer Project and Transfer Ownership currently refuse any project that contains a bucket, and the bucket has to be deleted before either one can go ahead. There is no supported way to move a project between workspaces with its bucket, objects or encrypted backups kept in place, and we have no manual override for it. There is also no waiting period that lifts the restriction.
The one handover that keeps everything in place, the bucket included, is handing over the whole workspace rather than moving the project. The school's account is invited to the current workspace from its People settings and made an Admin, then the new Admin removes the original one. Nothing moves, because the workspace itself stays the same, so IDs, volumes, the bucket, its objects and its credentials are unchanged. Adding a workspace member requires an active Pro subscription, so this route is not available while the workspace is on Hobby. Billing also stays with the workspace: the existing payment method keeps being charged until the new Admin replaces it in the workspace billing settings.
On Hobby, the project transfer flows described earlier are the available routes, and they require the bucket to be removed first.
Status changed to Awaiting User Response Railway • about 1 month ago
24 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 24 days ago