Other options for entity mapping?

In this sample there are at least three sets of **Entites**: Data layer entities (mapped to REST api or database: ```MoveEntity```), Domain layer entities (```Movie```) and view layer entites (```MovieView```). For each entity to flow from data layer to view layer two mappers are needed. Two other mappers are needed for reverse direction, which are not provided in this sample because only **read** scenarios are implemented. It means that four mappers are involved in moving data through layers back and forth. Adding a new field require all of them to change as well. This can become a maintenance problem. I have two questions regarding this issue:

1. Where is the best place to implement mapping logic?
2. What are other options? (maybe some kind of automatic mapping?)