In any case, there is a bit of marketing speak here. We try our best to make it portable. We are at the mercy of apps ultimately...

When we move nextcloud to OIDC, hopefully, we can move all installations into username based.

Basically it seems you can't properly move Nextcloud users from one Cloudron to another.

Although perhaps things have changed and that isn't true anymore? Maybe @staff could test this themselves at some point.

@necrevistonnezr more info about all this from @girish over here which was from the same time.

"We put great effort into app packages to deliver reliable, tested and reproducible updates."

But I think an additional "our" might help too, i.e.

"We put great effort into our app packages to deliver reliable, tested and reproducible updates."

Thanks! Fixed this now.

This was a specific issue where you had imported the app backup before having imported the Cloudron users.

I tried it again the other way around (creating users with the exact same usernames and in the exact same groups etc) and hit exactly the same issue. Basically it seems you can't properly move Nextcloud users from one Cloudron to another.

Also, relatively small issue, but given my experience with Nextcloud (and presumably this is true of other apps too - depending on how they maps users to their db etc), this isn't strictly true:
...
Moving an entire Cloudron server works great. Moving apps from one Cloudron server to another, less so.

Disagree. This was a specific issue where you had imported the app backup before having imported the Cloudron users.
In general, Cloudron apps are portable (and amazingly so if you look at the complexity of LDAB / OIDC) if you adhere to the standards.

"100% Portable

"Cloudron's immutable infrastructure design allows easy migration of apps across servers."

Moving an entire Cloudron server works great. Moving apps from one Cloudron server to another, less so.