This is not accurate for this case. When change occurs, we have to ensure that data is retained. When major changes occur (like an entirely new codebase) data migrations have to be done to get things in the right place in the new app. We don’t have a backwards migration built, so there is absolutely a lift here that would have to happen. At this time, that is not a path we are going down.
Now after re-reading 
I realize I responded for the reverting of the app in the same app id channel - if the argument is that you don’t care about the data side of things and want a fresh and clean app (assuming a new app id) then it is much easier and I would agree more on the lower lift comment. However, this creates big future headaches. Again, at this time, that is not a path that we are looking to provide.
