Transfer workspaces to a different account
![Georges Duverger](https://us.v-cdn.net/6037124/user_avatars/1709796.jpg)
Comments
-
this is a feature that allows Agency plans to do this so they can develop and transfer client work.
But go ahead and write me a note through support or support@xano.com with further details and we'll see what we can do for you -
Got it. I'll gather all the details and email you shortly. Thanks, Michael.
-
@Georges Duverger where you able to have your workspace moved? We have a similar case where we want to migrate a workspace to another instance or account. Eager to learn if you were able to move the workspace. Thanks!
-
Hi @Ben -5225939 - this is a feature currently available to our Agency plans - https://docs.xano.com/agency-plan/transfer-ownership
-
Does one need to change the endpoint's on the client side after you transfer the workspace? Or do those keep working?
-
@Michael Udinski Has this feature been moved somewhere.. I don't see it anymore?
-
Nevermind - found it.. It's in the agencies you manage instance, not the agency instance (a bit confusing tbh)
-
@Michael Udinski so we have to move all the endpoints client side once we transfer ownership? Seems that way
-
Hey @Paul S the idea is you transfer the entire workspace to the Client so they host it on their instance. Ideally, you shouldn't be hosting client projects but instead use your Agency instance to begin the development of a client project until the hand-off is ready.
-
yeah, that's what I've done, but now that I've transfered it to the client instance, I need to change all the API endpoints on my frontend as they still reference my Agency instance?
-
You are correct. Everything in the workspace, including the API endpoints, are moved to the Client Instance. So yes, you will need to update any endpoints connected in your front-end to point to the client instance now.
-
Thanks Michael.. appreciate your help as always.
I'm not sure this is ideal.. as you know setting up api connections in bubble is a little fiddly and requires seeding the connection with data, then initialising. Doing this at the last moment, when you're ready to launch is a pain and introduces risk. In future, I would rather set up the client instance upfront and do the development there. Or maybe you should consider keeping the api endpoint the same when the transfer happens?
-
Hey Paul - yes I'd definitely recommend development on the client instance - or at least transfer the workspace there once you're ready to start making the connections to a front end. Since each instance is its own dedicated server the endpoint URL has to change because the server is physically changing.
-
@Michael Udinski , sorry, but I've been building the database structure for a client in my particular account, just for a test, and now they want to transfer the whole workspace to their instance.
I've seen that it is possible if I had a Agency account, but I haven't.
Is it possible in any other way?
Next time I'll build everything in my clients side, for sure.
Thanks. -
Is it possible to do a reverse agency transfer? i.e. from a client back into an agency?
-
@Brian Giometti - it's only a one-way transfer for security reasons
Categories
- All Categories
- 53 ? Announcements
- 47 ? Releases
- 37 ? Welcome
- 983 ? Help! I'm a Noob
- 125 ? No-Code Front-Ends
- 633 ? Working with APIs
- 439 ? Transforming data
- 126 ? Connect Xano to ...
- 50 ?? Find an Expert
- 348 ❓Other questions
- 35 ? Security
- 22 ✂️ Snippets
- 19 ? Showcase
- 7 ?️ Xano Chatter
- 62 ? Video Tutorials
- 171 ? Request a feature
- 229 ? Report a Bug
- 19 ? Templates & Extensions
- 7 ? Feedback