Question: Why aren’t file assets transferred when cloning an app from another organization or migrating it between client accounts?
Answer: This is intentional behavior. File assets are not cloned or moved because the system cannot reliably determine which assets are being used. The assets remain in the original environment and do not break in the cloned app.
Original Slack Thread
User U057L133LV6: We find that when we ‘migrate’ a app between client accounts using the New App > My Apps option that File Assets are not transferred nicely as well… bummer.
It is probably in the documentation but finding out on the day of a large migration is not cool :fearful:
User U057L133LV6: And when migrating a V3 version it shows up as a V2 version at the other end?!?
User UBBJX2EHM: When cloning an app from an app in another org the file assets are not cloned but also do not break.
This is intentional.
Are you finding something else?
User UBBJX2EHM: The version could be copied and we will note that.
User U057L133LV6: We tend to develop within the Loggix account and then move all over. This time there are lots of assets that now stay behind and clutter our environment instead of that of the client :wink:
User U057L133LV6: Found big issue (my opinion!!) Why are we migrating ONLY pages with a slug from one environment to another… that just cost me 3 hours of debugging!! Not cool, sorry
User UBBJX2EHM: Was the friction that assets are not moved?
The challenge there is there is no way of telling what assets are being used.