I've found a happy balance developing with rails by adding two strategies:
1) Use presenters for display-only logic to keep controllers concerned with managing requests only.
2) Using service object / custom classes in /lib for actions on models as well as abstracting any common related functionality. Creators, Updaters, Processors, Orchestrators, etc. Keep your models only concerned with data and not data transformation, and your controllers from doing it as well.