Good point. It's an app that's got a life left to it. Not much in the way of changes but it's a pretty critical piece of software. Cloned a copy, moving it to 5

Good point. It's an app that's got a life left to it. Not much in the way of changes but it's a pretty critical piece of software. Cloned a copy, moving it to 5.2 and 6.0. Had to update ruby to 2.5.1. Looks like postgresql (which I use heavily) is also making comments about migrating data. This is not seamless. Lots of issues not to mention `rails app:update` basically wipes out the files, you go back in replace with needed info via diff, more errors. I thought that was supposed to alleviate that. If this works I'm hoping at least pushing to Heroku will handle that part. Heroku notes the gem file and makes the required updates.