To update from business legacy to business… is there an update plan button anywhere? or do we cancel plan & then subscribe to a new plan?
Is there any affect on our apps?
I think the only effect would be on your User and Update counts.
I think my advice would be to create a new team with a Business Trial, make a copy of your App and move it into the new team, and then only cancel your original subscription once you are satisfied that the new one is suitable.
Just keep in mind that once you cancel your legacy plan, there is no going back.
3 Likes
I can’t do that. there are 3 apps using the same tables. i don’t want to move to a new team or the link between them would probably break?
ah, yes - that is a problem. I’ve also bumped into that challenge.
I’m not sure there is a good option then, other than to downgrade and then upgrade. You just need to be absolutely sure it’s what you want to do.
Yes its the only option.
Legacy business no longer necessary… or you advice otherwise? I just want to know the right way to do that?
is it
- cancel plan
- subscribe to new plan
so there is no upgrade button or etc.?
I don’t think I can advise either way. It really depends on your specific use case.
I have a Legacy Business plan which I am holding on to for now, because I have one App in the team which has a user base of around 500 users. There is no way I could afford to keep that App in a new Business Team 
Darren i have a separate question if you can advice.
Client is asking if they can downgrade to free when they are not using the app. If they do so and remain so for a few month etc… its an events company and the app is to manage their onsite assets (so they don’t need when there are no events)
Is there any risk of losing any data? files ?
Do they have to rebuild anything or will any components be removed (instead of disabled) before they upgrade back up to business?
To be honest, I’m not really sure.
Certainly, any features that require Business will definitely stop working. But I don’t know what would happen if (for example) you are using Big Tables. Maybe the tables would still be there, but the data not accessible. Or maybe the tables would be removed from the App altogether. Maybe even deleted? I don’t know. I think to get any sort of definitive answer you’d probably have to reach out to Glide Sales.
If you create duplicate apps linked to the same tables instead of duplicating the tables, I would think you could still duplicate and move all three apps without breaking the link between them. (Disclaimer: I’ve never tried this exact scenario.)
I’ve never had issues moving single apps between teams (I also don’t really use any integrations that may break when moving between teams). I know there is a limitation of not being able to share tables across teams, but that’s more of a data security limitation and not a technical limitation. You just can’t select tables to add to an app if those tables being to a different team. If they are already party of an app, I think there really shouldn’t be an issue when moving apps.
I think you can still pull it off without too many issues. Just duplicate all three apps keeping the same tables, and move the duplicates. They should all still remain connected to the same tables. Easy to test if you have a new team on the business trial.
I don’t think that will work, because if it did it would mean you would have a single set of shared tables - shared across two teams. And I’m fairly certain that isn’t supported.
Not technically supported. People have done it though. And really in this case, it’s short term. As far as I understand, what is not supported is the ability to add a table from another team, but I don’t think anything is preventing the ability to use a table from another team if it’s already part of an app.
I can move apps all day long between teams. But like I said, I haven’t technically tried to move complimentary apps.
You got me curious, so I just did a test.
- Created an App in an Enterprise Team.
- Created a second App in the same team.
- Linked a table from the first App to the second App
- Moved the second App to another Enterprise team
- Made same changes to the linked table and observed that the changes did indeed sync across teams.
So yes, you’re correct.
However, if there are any high scale data sources in play (eg. Big Tables), then it isn’t possible.
Also, I don’t think this is what @abdo is really looking for. If I understand correctly, what he would need to be able to do is duplicate the 3 Apps as a group - including duplicating the linked tables as a group. So the end result would be 3 Apps sharing one set of linked tables, and a second group of 3 Apps sharing a separate set of linked tables, where the second set of Apps/tables is a copy of the first. And unfortunately there is no easy way to do that. The only way to do it is to start by duplicating one App and duplicate the tables. Then make two copies of that App, unlink all the tables, link the tables from the first App, and rebuild everything in Apps 2 & 3.
I’ve been down this path with a client. We originally started with two Apps sharing a common set of tables. Then at one point they decided that they needed 3 separate environments: Dev, Staging, Prod. So basically 3 sets of 2 Apps with each set sharing a (separate) common set of tables. I very quickly realised that it is practically impossible to maintain this setup with Glide as it is, so I had to bite the bullet and merge the two Apps into one. It’s still quite challenging to maintain and move Apps around, but possible.
1 Like
I agree. I’m sure there are a couple of gotchas there.
Why would he need to duplicate the tables as well? The goal is to upgrade the apps to a new plan, and to do that by duplicating the apps and moving the duplicates to avoid interruption. Not create an independent set of apps and maintain them separately in two teams.
I get what you’re saying, but I don’t think that’s the case here.
That’s just the way I read the question. But quite possibly I’m wrong and there is some bias creeping in based on my own experience
I’m understanding that there’s are 3 apps in a legacy business team and @abdo wants to upgrade the team to a new business plan. So in the end, all apps would ultimately be in the new team and the original team would be deleted and the old apps removed.
I’m in the office today, so I don’t have my personal computer to test it myself, but I’m pretty sure if you took two apps that shared a table, duplicated both of them without duplicating the data, and then transfer both duplicates to a new team, they would still be connected to each other using the same original tables.
2 Likes
Yes, absolutely.
And when you put it that way it makes perfect sense 
2 Likes